| 1. General Results, most used to calculate the result |
| A | name "5.196.26.210" is ipv4 address, public suffix is not defined
|
| A | Good: All ip addresses are public addresses
|
| A | Good: No cookie sent via http.
|
| A | Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset)
|
| B | https://5.196.26.210/ 5.196.26.210
|
| Missing HSTS-Header
|
| C | Error - no version with Http-Status 200
|
| H | Fatal error: No https - result with http-status 200, no encryption
|
| M | http://5.196.26.210/ 5.196.26.210
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://5.196.26.210/ 5.196.26.210
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://5.196.26.210/ 5.196.26.210
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://5.196.26.210/ 5.196.26.210
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| B | No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.5.196.26.210
|
| 2. Header-Checks |
| F | 5.196.26.210 5.196.26.210
| Content-Security-Policy
| Critical: Missing Header:
|
| F | 5.196.26.210 5.196.26.210
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | 5.196.26.210 5.196.26.210
| Referrer-Policy
| Critical: Missing Header:
|
| F | 5.196.26.210 5.196.26.210
| Permissions-Policy
| Critical: Missing Header:
|
| B | 5.196.26.210 5.196.26.210
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | 5.196.26.210 5.196.26.210
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | 5.196.26.210 5.196.26.210
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| 4. Content- and Performance-critical Checks |
| A | Good: 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.
|
| A | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| A | Info: No img element found, no alt attribute checked
|
| https://5.196.26.210/ 5.196.26.210
| 2.574 seconds
| Warning: 404 needs more then one second
|
| https://5.196.26.210/ 5.196.26.210
| 2.134 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 27950 milliseconds, 27.950 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)