1. General Results, most used to calculate the result A name "priv.its-zeller.de" is subdomain, 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: 8783 (complete: 220007) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: priv.its-zeller.de has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: priv.its-zeller.de has 1 ipv4, 1 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: destination is https A Good - only one version with Http-Status 200 A Good: one preferred version: non-www is preferred A Good: No cookie sent via http. Warning: HSTS preload sent, but not in Preload-List. Never send a preload directive if you don't know what preload means. Check https://hstspreload.org/ to learn the basics about the Google-Preload list. If you send a preload directive, you should **immediately** add your domain to the HSTS preload list via https://hstspreload.org/ . If Google accepts the domain, so the status is "pending": Note that new entries are hardcoded into the Chrome source code and can take several months before they reach the stable version. So you will see this message some months. If you don't want that or if you don't understand "preload", but if you send a preload directive and if you have correct A-redirects, everybody can add your domain to that list. Then you may have problems, it's not easy to undo that. So if you don't want your domain preloaded, remove the preload directive. 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 (2 urls) https://priv.its-zeller.de/ 91.46.24.222 Url with incomplete Content-Type - header - missing charset https://91.46.24.222/ 91.46.24.222 Url with incomplete Content-Type - header - missing charset B Warning: HSTS max-age is too short - minimum 31536000 = 365 days required, 15768000 seconds = 182 days found K http://priv.its-zeller.de/ 91.46.24.222, Status 301 http://priv.its-zeller.de/ 2003:d8:77ff:3aa7:464e:6dff:fed1:9525, Status -14 Configuration problem - different ip addresses with different status K https://priv.its-zeller.de/ 91.46.24.222, Status 200 https://priv.its-zeller.de/ 2003:d8:77ff:3aa7:464e:6dff:fed1:9525, Status -14 Configuration problem - different ip addresses with different status K http://priv.its-zeller.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.46.24.222, Status 301 http://priv.its-zeller.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:d8:77ff:3aa7:464e:6dff:fed1:9525, Status -14 Configuration problem - different ip addresses with different status N https://91.46.24.222/ 91.46.24.222 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 priv.its-zeller.de, 2 ip addresses. 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.priv.its-zeller.de 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) F priv.its-zeller.de 91.46.24.222 Content-Security-Policy Critical: Missing Header: F priv.its-zeller.de 91.46.24.222 X-Content-Type-Options Critical: Missing Header: F priv.its-zeller.de 91.46.24.222 Referrer-Policy Critical: Missing Header: F priv.its-zeller.de 91.46.24.222 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 4 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers. A Info:: 4 Queries complete, 4 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.ns.second-ns.com (213.239.204.242, 2a01:4f8:0:a101::b:1), ns1.your-server.de (213.133.106.251, 2a01:4f8:d0a:2006::2), ns3.second-ns.de (193.47.99.4, 2001:67c:192c::add:b3) A Good (1 - 3.0):: An average of 1.3 queries per domain name server required to find all ip addresses of all name servers. A Info:: 3 different Name Servers found: ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de, 3 Name Servers included in Delegation: ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de, 3 Name Servers included in 1 Zone definitions: ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de, 1 Name Servers listed in SOA.Primary: ns1.your-server.de. A Good: Only one SOA.Primary Name Server found.: ns1.your-server.de. A Good: SOA.Primary Name Server included in the delegation set.: ns1.your-server.de. 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 Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 193., 213., 3 different subnets (first two Bytes): 193.47., 213.133., 213.239., 3 different subnets (first three Bytes): 193.47.99., 213.133.106., 213.239.204. A Good: Name Server IPv4-addresses from different subnet found: A Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 2 different subnets (first block): 2001:, 2a01:, 2 different subnets (first two blocks): 2001:067c:, 2a01:04f8:, 3 different subnets (first three blocks): 2001:067c:192c:, 2a01:04f8:0000:, 2a01:04f8:0d0a:, 3 different subnets (first four blocks): 2001:067c:192c:0000:, 2a01:04f8:0000:a101:, 2a01:04f8:0d0a:2006: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 6 good Nameserver A Good: Nameserver supports Echo Capitalization: 6 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1.your-server.de: 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 Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries. 4. Content- and Performance-critical Checks http://priv.its-zeller.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:d8:77ff:3aa7:464e:6dff:fed1:9525 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. https://priv.its-zeller.de:443/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://priv.its-zeller.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2003:d8:77ff:3aa7:464e:6dff:fed1:9525, Status -14 http://priv.its-zeller.de/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 91.46.24.222, Status 301 Fatal: Check of /.well-known/acme-challenge/random-filename has different answers checking ipv6 / ipv4. Ipv6 doesn't have the expected result http status 404 - Not Found. Creating a Letsencrypt certificate via http-01 validation may not work. Checking the validation file in /.well-known/acme-challenge Letsencrypt prefers ipv6. Two options: Remove your ipv6 / AAAA DNS entry or (better) fix your ipv6, so your webserver handles ipv6 correct. Perhaps add "Listen [::]:80". Don't use <VirtualHost ip-address:80>, switch to <VirtualHost *:80>. If you use IIS, check your bindings. Don't select a single ip address. Use this tool to check your raw ipv6 address. Add your domain name in the "Hostname" - field. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. A Good: Every https result with status 200 supports GZip. https://priv.its-zeller.de/ 91.46.24.222 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://91.46.24.222/ 91.46.24.222 Warning: Https + http status 200 + Inline CSS / JavaScript found. Don't use inline CSS / JavaScript. These are compiled and re-used ressources, save these with a long Cache-Control max-age - header. https://priv.its-zeller.de/ 91.46.24.222 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://91.46.24.222/ 91.46.24.222 Warning: Https result with status 200 found, Html-Content is too big. Should be max. 110 %. May contain inline CSS / JavaScript, too much comments or white space. Re-used ressources - create files with a long Cache-Control max-age header. Remove comments and white space. https://priv.its-zeller.de/ 91.46.24.222 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. https://91.46.24.222/ 91.46.24.222 Warning: Https connections (Standard Port 443) found without support of the http/2 protocol via ALPN. Http/2 is the new Http-Version (old: http 1.1) with some important new features. Update your server software so http/2 is available. Only one TCP-connection per Server (that's a performance boost), Header-Compression and Server Pushs are available. Domain Sharding and Inline-CSS/Javascript shouldn't used with http/2. A Good: All images with internal compression not sent via GZip. Images (.png, .jpg) are already compressed, so an additional GZip isn't helpful. 1 images (type image/png, image/jpg) found without additional GZip. Not required because these images are already compressed Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 2 image files without Cache-Control-Header, 0 with Cache-Control, but no max-age, 0 with Cache-Control max-age too short (minimum 7 days), 0 with Cache-Control long enough, 2 complete. 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 http://priv.its-zeller.de/ 91.46.24.222 Warning: HSTS header sent via http has no effect A Duration: 225427 milliseconds, 225.427 seconds