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




W

wrong Web-Response

Checked:
10.06.2019 17:48:41


Older results


1. IP-Addresses

HostTIP-Addressis auth.∑ Queries∑ Timeout
77.239.51.20
A
77.239.51.20
Solothurn/CH
Hostname: 20-51-239-77.dyn.cable.fcom.ch
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://77.239.51.20:80/
77.239.51.20
200

0.070
H
Server: nginx
Date: Mon, 10 Jun 2019 15:48:46 GMT
Content-Type: text/html
Content-Length: 1554
Connection: close
Vary: Accept-Encoding,Accept-Encoding
Last-Modified: Thu, 01 Feb 2018 23:07:27 GMT
ETag: "612-5642ea8d1d833"
Accept-Ranges: bytes

• https://77.239.51.20:80/
77.239.51.20
-4

0.124
W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

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

0.077
A
Not Found
Visible Content:
Server: nginx
Date: Mon, 10 Jun 2019 15:48:46 GMT
Content-Type: text/html
Content-Length: 11939
Connection: close
Vary: Accept-Encoding
ETag: "5cd4a4d8-2ea3"

6. Comments

Aname "77.239.51.20" is ipv4 address, public suffix is not defined
Agood: All ip addresses are public addresses
Agood - only one version with Http-Status 200
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (2 urls)
http://77.239.51.20:80/ 77.239.51.20


Url with incomplete Content-Type - header - missing charset
http://77.239.51.20:80/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 77.239.51.20


Url with incomplete Content-Type - header - missing 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.
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: 3290 milliseconds, 3.290 seconds


7. Connections

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 - CT-Log entries found


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

No CRT - CT-Log entries found


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=57c3b1dd-1b2c-4015-888a-0f5a41a162d6


Last Result: https://check-your-website.server-daten.de/?q=77.239.51.20%3a80 - 2019-06-10 17:48:41


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

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