1. General Results, most used to calculate the result A name "server-daten.de" is domain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 6338 (complete: 131120) A good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: server-daten.de has 2 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.server-daten.de has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: server-daten.de has 1 ipv4, 1 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.server-daten.de has 1 ipv4, 1 ipv6 addresses A good: No asked Authoritative Name Server had a timeout A good: destination is https A good - only one version with Http-Status 200 A good: one preferred version: www is preferred A Good: No cookie sent via http. A good: every cookie sent via https is marked as secure A Good: Every cookie has a SameSite Attribute with a correct value Strict/Lax/None A Excellent: All cookies (except Cloudflare __cfduid) are Prefix-Cookies:4 Cookies complete, 4 __Host-Cookies, 0 __Secure-Cookies, 0 __cfduid-Cookies (Cloudflare) A good: every https has a Strict Transport Security Header A good: HSTS max-age is long enough, 63072000 seconds = 730 days A good: HSTS has includeSubdomains - directive A good: HSTS has preload directive A Excellent: Domain is in the Google-Preload-List A Excellent: Domain is in the Mozilla/Firefox-Preload-List A HSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List. A Good: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) A http://server-daten.de/ 85.215.2.226 https://server-daten.de/ correct redirect http - https with the same domain name A http://server-daten.de/ 2a01:238:301b::1226 https://server-daten.de/ correct redirect http - https with the same domain name A http://www.server-daten.de/ 85.215.2.226 https://www.server-daten.de/ correct redirect http - https with the same domain name A http://www.server-daten.de/ 2a01:238:301b::1226 https://www.server-daten.de/ correct redirect http - https with the same domain name N https://85.215.2.226/ 85.215.2.226 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://[2a01:0238:301b:0000:0000:0000:0000:1226]/ 2a01:238:301b::1226 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 server-daten.de, 2 ip addresses. 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 www.server-daten.de, 2 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 server-daten.de, 2 ip addresses, 1 different http results. 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 www.server-daten.de, 2 ip addresses, 1 different http results. 2. DNS- and NameServer - Checks A Info:: 17 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 5 Name Servers. A Info:: 17 Queries complete, 17 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. A Good: Some ip addresses of name servers found with the minimum of two DNS Queries. One to find the TLD-Zone, one to ask the TLD-Zone.ns3.inwx.eu (213.239.206.103, 2a01:4f8:222:b03::2) Ok (4 - 8):: An average of 3.4 queries per domain name server required to find all ip addresses of all name servers. A Info:: 5 different Name Servers found: ns.inwx.de, ns2.inwx.de, ns3.inwx.eu, ns4.inwx.com, ns5.inwx.net, 5 Name Servers included in Delegation: ns.inwx.de, ns2.inwx.de, ns3.inwx.eu, ns4.inwx.com, ns5.inwx.net, 5 Name Servers included in 1 Zone definitions: ns.inwx.de, ns2.inwx.de, ns3.inwx.eu, ns4.inwx.com, ns5.inwx.net, 1 Name Servers listed in SOA.Primary: ns.inwx.de. A Good: Only one SOA.Primary Name Server found.: ns.inwx.de. A Good: SOA.Primary Name Server included in the delegation set.: ns.inwx.de. 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.inwx.de, ns2.inwx.de, ns3.inwx.eu, ns4.inwx.com, ns5.inwx.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: 5 different Name Servers found A Good: All name servers have ipv4- and ipv6-addresses.: 5 different Name Servers found A Good: Name servers with different Top Level Domains / Public Suffix List entries found: 5 Name Servers, 4 Top Level Domains: eu, de, net, com A Good: Name Servers with different domain names found.: 4 different Domains found A Good: Name servers with different Country locations found: 5 Name Servers, 5 Countries: AT, CH, DE, NL, US A Info: Ipv4-Subnet-list: 5 Name Servers, 5 different subnets (first Byte): 108., 176., 192., 213., 95., 5 different subnets (first two Bytes): 108.59., 176.97., 192.174., 213.239., 95.211., 5 different subnets (first three Bytes): 108.59.8., 176.97.158., 192.174.68., 213.239.206., 95.211.1. A Excellent: Every Name Server IPv4-address starts with an unique Byte. A Info: IPv6-Subnet-list: 5 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2604:, 2a01:, 4 different subnets (first two blocks): 2001:067c:, 2001:1af8:, 2604:9a00:, 2a01:04f8:, 5 different subnets (first three blocks): 2001:067c:01bc:, 2001:067c:10b8:, 2001:1af8:4400:, 2604:9a00:2010:, 2a01:04f8:0222:, 5 different subnets (first four blocks): 2001:067c:01bc:0000:, 2001:067c:10b8:0000:, 2001:1af8:4400:a048:, 2604:9a00:2010:a013:, 2a01:04f8:0222:0b03: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 10 good Nameserver A Good: Nameserver supports Echo Capitalization: 10 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 10 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns3.inwx.eu / 213.239.206.103: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (maude.inwx.net). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns3.inwx.eu / 2a01:4f8:222:b03::2: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (maude.inwx.net). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns4.inwx.com / 95.211.1.145: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (hoover). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns4.inwx.com / 2001:1af8:4400:a048:1::1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (hoover). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns5.inwx.net / 108.59.8.65: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (chalmers.inwx.net). COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns5.inwx.net / 2604:9a00:2010:a013:1::1: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (chalmers.inwx.net). COOKIE: ok. CLIENTSUBNET: ok. A Good: All SOA have the same Serial Number A good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates 3. 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: Every https result with status 200 supports GZip. A Good: Every https result with status 200 has a minified Html-Content with a quota lower then 110 %. A Good: Every https connection via port 443 supports the http/2 protocol via ALPN. A Good: All script Elements (type text/javascript) and src-Attribute have a defer / async - Attribute. So loading and executing these JavaScripts doesn't block parsing and rendering the Html-Output. A Good: All CSS / JavaScript files are sent with GZip. That reduces the content of the files. 4 external CSS / JavaScript files found A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 2 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed A Good: All CSS / JavaScript files are sent with a long Cache-Control header (minimum 7 days). So the browser can re-use these files, no download is required. 4 external CSS / JavaScript files with long Cache-Control max-age found A Good: All images are sent with a long Cache-Control header (minimum 7 days). So the browser can reuse these files, no download is required. 2 image files with long Cache-Control max-age found A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: All img-elements have a valid alt-attribute.: 2 img-elements found. 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 Duration: 103924 milliseconds, 103.924 seconds