Check DNS, Urls + Redirects, Certificates and Content of your Website




V

Connect failure - perhaps firewall

Checked:
04.03.2019 20:29:36


Older results

No older results found


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
207.180.196.157
A
207.180.196.157
Hostname: -
yes



2. DNSSEC


No DNSSEC - Informations found


3. Name Servers


No Nameserver entries found


4. SOA-Entries


No SOA entries found

5. Url-Checks


:

:
Domainname Http-StatusredirectSec.G
• http://207.180.196.157/
207.180.196.157
200

0.060
H
Date: Mon, 04 Mar 2019 19:29:41 GMT
Server: Apache/2.4.29 (Ubuntu)
Vary: Accept-Encoding
Content-Length: 753
Connection: close
Content-Type: text/html;charset=UTF-8

• https://207.180.196.157/
207.180.196.157
-2

1.063
V
ConnectFailure - Unable to connect to the remote server No connection could be made because the target machine actively refused it 207.180.196.157:443

• http://207.180.196.157/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
207.180.196.157
404

0.077
A
Not Found
Visible Content:
Date: Mon, 04 Mar 2019 19:29:42 GMT
Server: Apache/2.4.29 (Ubuntu)
Content-Length: 348
Connection: close
Content-Type: text/html; charset=iso-8859-1

6. Comments (GZip / Html minfied / Cache-Control is beta)

Aname "207.180.196.157" is ipv4 address, public suffix is not defined
Agood: All ip addresses are public addresses
Agood - only one version with Http-Status 200
AGood: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
Hfatal error: No https - result with http-status 200, no encryption
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
Vhttps://207.180.196.157/ 207.180.196.157
-2

connect failure - perhaps firewall
AGood: All checks /.well-known/acme-challenge/random-filename without redirects answer with the expected http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 challenge should work. If it doesn't work: Check your vHost configuration (apachectl -S, httpd -S, nginx -T). Every combination of port and ServerName / ServerAlias (Apache) or Server (Nginx) must be unique. Merge duplicated entries in one vHost. If you use an IIS, extensionless files must be allowed in the /.well-known/acme-challenge subdirectory. Create a web.config in that directory. Content: <configuration><system.webServer><staticContent><mimeMap fileExtension="." mimeType="text/plain" /></staticContent></system.webServer></configuration>. If you have a redirect http ⇒ https, that's ok, Letsencrypt follows such redirects to port 80 / 443 (same or other server). There must be a certificate. But the certificate may be expired, self signed or with a not matching domain name. Checking the validation file Letsencrypt ignores such certificate errors. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 2960 milliseconds, 2.960 seconds


7. Connections (http/2- and additional Tls.1.0/1.1/1.2 checks are BETA)

No connection informations found. Perhaps only http - connections.


8. Certificates

No certificate informations found. Perhaps only http - connections.


9. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates

No CertSpotter - Certificate-Transparency-Log informations found. The feature is new (startet 2019-05-07), so recheck this domain.


2. Source crt.sh - old and new certificates, sometimes very slow.

No Certificate-Transparency-Log informations found. The feature is new (startet 2019-03-21), so recheck this domain.


10. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


11. CAA - Entries

No CAA entries found


12. TXT - Entries

No TXT entries found


13. Portchecks (BETA)

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=ba64bc6b-a972-432b-a369-12fced519e09


Last Result: https://check-your-website.server-daten.de/?q=207.180.196.157 - 2019-03-04 20:29:36


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=207.180.196.157" target="_blank">Check this Site: 207.180.196.157</a>