1. General Results, most used to calculate the result A name "d2s24bcvfqs8se.cloudfront.net" is domain, public suffix is ".cloudfront.net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 8549 (complete: 221801) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: d2s24bcvfqs8se.cloudfront.net has 12 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: d2s24bcvfqs8se.cloudfront.net has 4 ipv4, 8 ipv6 addresses A Good: No asked Authoritative Name Server had a timeout A DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem A Good: No cookie sent via http. HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (64 urls) http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.28 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.91 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.143 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.227 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.110 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.121 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.158 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.205 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:2200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3a00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3e00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:5000:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8600:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8c00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:d200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.28 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.91 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.143 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.227 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.110 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.121 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.158 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.205 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:2200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3a00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3e00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:5000:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8600:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8c00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:d200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.28 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.91 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.143 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.227 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.110 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.121 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.158 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.205 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:2200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:3a00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:3e00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:5000:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:8200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:8600:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:8c00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:d200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://18.64.100.28/ 18.64.100.28 Url with incomplete Content-Type - header - missing charset https://18.64.100.91/ 18.64.100.91 Url with incomplete Content-Type - header - missing charset https://18.64.100.143/ 18.64.100.143 Url with incomplete Content-Type - header - missing charset https://18.64.100.227/ 18.64.100.227 Url with incomplete Content-Type - header - missing charset https://18.238.169.110/ 18.238.169.110 Url with incomplete Content-Type - header - missing charset https://18.238.169.121/ 18.238.169.121 Url with incomplete Content-Type - header - missing charset https://18.238.169.158/ 18.238.169.158 Url with incomplete Content-Type - header - missing charset https://18.238.169.205/ 18.238.169.205 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:2200:0006:31c0:5f80:0021]/ 2600:9000:250d:2200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:3a00:0006:31c0:5f80:0021]/ 2600:9000:250d:3a00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:3e00:0006:31c0:5f80:0021]/ 2600:9000:250d:3e00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:5000:0006:31c0:5f80:0021]/ 2600:9000:250d:5000:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:8200:0006:31c0:5f80:0021]/ 2600:9000:250d:8200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:8600:0006:31c0:5f80:0021]/ 2600:9000:250d:8600:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:8c00:0006:31c0:5f80:0021]/ 2600:9000:250d:8c00:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset https://[2600:9000:250d:d200:0006:31c0:5f80:0021]/ 2600:9000:250d:d200:6:31c0:5f80:21 Url with incomplete Content-Type - header - missing charset B https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.28 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.91 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.143 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.227 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.110 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.121 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.158 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.205 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:2200:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3a00:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3e00:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:5000:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8200:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8600:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8c00:6:31c0:5f80:21 Missing HSTS-Header B https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:d200:6:31c0:5f80:21 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://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.28 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.91 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.143 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.227 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.110 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.121 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.158 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.205 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:2200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3a00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3e00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:5000:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8600:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8c00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M http://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:d200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.28 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.91 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.143 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.64.100.227 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.110 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.121 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.158 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 18.238.169.205 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:2200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3a00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:3e00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:5000:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8600:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:8c00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://d2s24bcvfqs8se.cloudfront.net/ 2600:9000:250d:d200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://18.64.100.28/ 18.64.100.28 Misconfiguration - main pages should never send http status 400 - 499 M https://18.64.100.91/ 18.64.100.91 Misconfiguration - main pages should never send http status 400 - 499 M https://18.64.100.143/ 18.64.100.143 Misconfiguration - main pages should never send http status 400 - 499 M https://18.64.100.227/ 18.64.100.227 Misconfiguration - main pages should never send http status 400 - 499 M https://18.238.169.110/ 18.238.169.110 Misconfiguration - main pages should never send http status 400 - 499 M https://18.238.169.121/ 18.238.169.121 Misconfiguration - main pages should never send http status 400 - 499 M https://18.238.169.158/ 18.238.169.158 Misconfiguration - main pages should never send http status 400 - 499 M https://18.238.169.205/ 18.238.169.205 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:2200:0006:31c0:5f80:0021]/ 2600:9000:250d:2200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:3a00:0006:31c0:5f80:0021]/ 2600:9000:250d:3a00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:3e00:0006:31c0:5f80:0021]/ 2600:9000:250d:3e00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:5000:0006:31c0:5f80:0021]/ 2600:9000:250d:5000:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:8200:0006:31c0:5f80:0021]/ 2600:9000:250d:8200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:8600:0006:31c0:5f80:0021]/ 2600:9000:250d:8600:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:8c00:0006:31c0:5f80:0021]/ 2600:9000:250d:8c00:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 M https://[2600:9000:250d:d200:0006:31c0:5f80:0021]/ 2600:9000:250d:d200:6:31c0:5f80:21 Misconfiguration - main pages should never send http status 400 - 499 N https://18.64.100.28/ 18.64.100.28 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.64.100.91/ 18.64.100.91 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.64.100.143/ 18.64.100.143 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.64.100.227/ 18.64.100.227 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.238.169.110/ 18.238.169.110 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.238.169.121/ 18.238.169.121 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.238.169.158/ 18.238.169.158 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://18.238.169.205/ 18.238.169.205 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:2200:0006:31c0:5f80:0021]/ 2600:9000:250d:2200:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:3a00:0006:31c0:5f80:0021]/ 2600:9000:250d:3a00:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:3e00:0006:31c0:5f80:0021]/ 2600:9000:250d:3e00:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:5000:0006:31c0:5f80:0021]/ 2600:9000:250d:5000:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:8200:0006:31c0:5f80:0021]/ 2600:9000:250d:8200:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:8600:0006:31c0:5f80:0021]/ 2600:9000:250d:8600:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:8c00:0006:31c0:5f80:0021]/ 2600:9000:250d:8c00:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2600:9000:250d:d200:0006:31c0:5f80:0021]/ 2600:9000:250d:d200:6:31c0:5f80:21 Error - Certificate isn't trusted, RemoteCertificateNameMismatch A Good: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain d2s24bcvfqs8se.cloudfront.net, 12 ip addresses. Info: Checking all ip addresses of that domain without sending the hostname only one certificate found. Checking all ip addresses and sending the hostname only one certificate found. Both certificates are the same. So that domain doesn't require Server Name Indication (SNI), it's the primary certificate of that set of ip addresses.: Domain d2s24bcvfqs8se.cloudfront.net, 12 ip addresses, 1 different http results. 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.d2s24bcvfqs8se.cloudfront.net 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) F d2s24bcvfqs8se.cloudfront.net 18.64.100.28 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.28 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.28 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.28 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.91 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.91 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.91 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.91 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.143 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.143 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.143 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.143 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.227 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.227 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.227 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.64.100.227 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.110 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.110 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.110 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.110 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.121 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.121 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.121 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.121 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.158 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.158 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.158 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.158 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.205 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.205 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.205 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 18.238.169.205 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:2200:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:2200:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:2200:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:2200:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3a00:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3a00:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3a00:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3a00:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3e00:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3e00:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3e00:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:3e00:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:5000:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:5000:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:5000:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:5000:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8200:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8200:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8200:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8200:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8600:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8600:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8600:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8600:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8c00:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8c00:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8c00:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:8c00:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:d200:6:31c0:5f80:21 Content-Security-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:d200:6:31c0:5f80:21 X-Content-Type-Options Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:d200:6:31c0:5f80:21 Referrer-Policy Critical: Missing Header: F d2s24bcvfqs8se.cloudfront.net 2600:9000:250d:d200:6:31c0:5f80:21 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 16 Queries complete, 16 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns-1181.awsdns-19.org, ns-2011.awsdns-59.co.uk, ns-205.awsdns-25.com, ns-670.awsdns-19.net, 4 Name Servers included in Delegation: ns-1181.awsdns-19.org, ns-2011.awsdns-59.co.uk, ns-205.awsdns-25.com, ns-670.awsdns-19.net, 4 Name Servers included in 1 Zone definitions: ns-1181.awsdns-19.org, ns-2011.awsdns-59.co.uk, ns-205.awsdns-25.com, ns-670.awsdns-19.net, 1 Name Servers listed in SOA.Primary: ns-205.awsdns-25.com. A Good: Only one SOA.Primary Name Server found.: ns-205.awsdns-25.com. A Good: SOA.Primary Name Server included in the delegation set.: ns-205.awsdns-25.com. A Good: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ns-1181.awsdns-19.org, ns-2011.awsdns-59.co.uk, ns-205.awsdns-25.com, ns-670.awsdns-19.net A Good: All Name Server Domain Names have a Public Suffix. A Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found A Good: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found A Good: Name servers with different Top Level Domains / Public Suffix List entries found: 4 Name Servers, 4 Top Level Domains: org, net, com, co.uk A Good: Name Servers with different domain names found.: 4 different Domains found A Good: Name servers with different Country locations found: 4 Name Servers, 3 Countries: GB, IE, US A Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.192., 205.251.194., 205.251.196., 205.251.199. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5300:, 2600:9000:5302:, 2600:9000:5304:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5300:cd00:, 2600:9000:5302:9e00:, 2600:9000:5304:9d00:, 2600:9000:5307:db00: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 8 good Nameserver A Good: Nameserver supports Echo Capitalization: 8 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns-205.awsdns-25.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. A Good: All SOA have the same Serial Number A Good: CAA entries found, creating certificate is limited: amazonaws.com is allowed to create wildcard-certificates A Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates 4. Content- and Performance-critical Checks http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.28 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.91 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.143 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.64.100.227 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.110 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.121 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.158 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 18.238.169.205 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:2200:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:3a00:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:3e00:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:5000:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:8200:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:8600:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:8c00:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://d2s24bcvfqs8se.cloudfront.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2600:9000:250d:d200:6:31c0:5f80:21 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 401 / 403 Not Allowed / Forbidden. A http status 404 - Not Found - is expected. Creating a Letsencrypt certificate via http-01 challenge may not work. 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 A Good: 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 A Info: Different Server-Headers found A Duration: 287794 milliseconds, 287.794 seconds