1. General Results, most used to calculate the result A name "zimmies.duckdns.org" is domain, public suffix is ".duckdns.org", top-level-domain is ".org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)", num .org-domains preloaded: 7468 (complete: 220007) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: www.zimmies.duckdns.org has 2 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: zimmies.duckdns.org has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: www.zimmies.duckdns.org has 1 ipv4, 1 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: zimmies.duckdns.org has 1 ipv4, 1 ipv6 addresses 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 (5 urls) http://www.zimmies.duckdns.org/ 88.130.0.73 Url with incomplete Content-Type - header - missing charset https://zimmies.duckdns.org/ 88.130.0.73 Url with incomplete Content-Type - header - missing charset https://www.zimmies.duckdns.org/ 88.130.0.73 Url with incomplete Content-Type - header - missing charset http://www.zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.130.0.73 Url with incomplete Content-Type - header - missing charset https://88.130.0.73/ 88.130.0.73 Url with incomplete Content-Type - header - missing charset A http://zimmies.duckdns.org/ 88.130.0.73 https://zimmies.duckdns.org/ Correct redirect http - https with the same domain name B https://zimmies.duckdns.org/ 88.130.0.73 Missing HSTS-Header B https://www.zimmies.duckdns.org/ 88.130.0.73 Missing HSTS-Header C Error - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version. C Error - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200. H Fatal 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. K http://www.zimmies.duckdns.org/ 88.130.0.73, Status 200 http://www.zimmies.duckdns.org/ 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 Configuration problem - different ip addresses with different status K http://zimmies.duckdns.org/ 88.130.0.73, Status 301 http://zimmies.duckdns.org/ 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 Configuration problem - different ip addresses with different status K https://www.zimmies.duckdns.org/ 88.130.0.73, Status 200 https://www.zimmies.duckdns.org/ 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 Configuration problem - different ip addresses with different status K https://zimmies.duckdns.org/ 88.130.0.73, Status 200 https://zimmies.duckdns.org/ 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 Configuration problem - different ip addresses with different status K http://www.zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.130.0.73, Status 404 http://www.zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 Configuration problem - different ip addresses with different status K http://zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.130.0.73, Status 301 http://zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 Configuration problem - different ip addresses with different status N https://www.zimmies.duckdns.org/ 88.130.0.73 Error - Certificate isn't trusted, RemoteCertificateNameMismatch N https://88.130.0.73/ 88.130.0.73 Error - Certificate isn't trusted, RemoteCertificateNameMismatch O www.zimmies.duckdns.org / 88.130.0.73 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found O zimmies.duckdns.org / 88.130.0.73 / 443 Old connection: Cipher Suites without Forward Secrecy (FS) found. Remove all of these Cipher Suites, use only Cipher Suites with Forward Secrecy: Starting with ECDHE- or DHE - the last "E" says: "ephemeral". Or use Tls.1.3, then all Cipher Suites use FS. 16 Cipher Suites without Forward Secrecy found X Fatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns1.duckdns.org / 99.79.143.35: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns2.duckdns.org / 35.182.183.211: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns3.duckdns.org / 35.183.157.249: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns4.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns4.duckdns.org / 3.97.51.116: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns5.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns5.duckdns.org / 99.79.16.64: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns6.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns6.duckdns.org / 3.97.58.28: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns7.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns7.duckdns.org / 15.223.21.81: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns8.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns8.duckdns.org / 15.223.106.16: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns9.duckdns.org: Timeout X Fatal error: Nameserver doesn't support TCP connection: ns9.duckdns.org / 15.222.19.97: Timeout 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.zimmies.duckdns.org, 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 zimmies.duckdns.org, 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.zimmies.duckdns.org 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) F zimmies.duckdns.org 88.130.0.73 Content-Security-Policy Critical: Missing Header: F zimmies.duckdns.org 88.130.0.73 X-Content-Type-Options Critical: Missing Header: F zimmies.duckdns.org 88.130.0.73 Referrer-Policy Critical: Missing Header: F zimmies.duckdns.org 88.130.0.73 Permissions-Policy Critical: Missing Header: F www.zimmies.duckdns.org 88.130.0.73 Content-Security-Policy Critical: Missing Header: F www.zimmies.duckdns.org 88.130.0.73 X-Content-Type-Options Critical: Missing Header: F www.zimmies.duckdns.org 88.130.0.73 Referrer-Policy Critical: Missing Header: F www.zimmies.duckdns.org 88.130.0.73 Permissions-Policy Critical: Missing Header: 3. DNS- and NameServer - Checks A Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 9 Name Servers. A Info:: 2 Queries complete, 2 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.ns1.duckdns.org (99.79.143.35), ns2.duckdns.org (35.182.183.211), ns3.duckdns.org (35.183.157.249), ns4.duckdns.org (3.97.51.116), ns5.duckdns.org (99.79.16.64), ns6.duckdns.org (3.97.58.28), ns7.duckdns.org (15.223.21.81), ns8.duckdns.org (15.223.106.16), ns9.duckdns.org (15.222.19.97) A Good (1 - 3.0):: An average of 0.2 queries per domain name server required to find all ip addresses of all name servers. A Info:: 9 different Name Servers found: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, ns7.duckdns.org, ns8.duckdns.org, ns9.duckdns.org, 9 Name Servers included in Delegation: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, ns7.duckdns.org, ns8.duckdns.org, ns9.duckdns.org, 9 Name Servers included in 2 Zone definitions: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, ns7.duckdns.org, ns8.duckdns.org, ns9.duckdns.org, 1 Name Servers listed in SOA.Primary: ns1.duckdns.org. A Good: Only one SOA.Primary Name Server found.: ns1.duckdns.org. A Good: SOA.Primary Name Server included in the delegation set.: ns1.duckdns.org. 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. Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1 A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 9 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 9 different Name Servers found Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 9 Name Servers, 1 Top Level Domain: duckdns.org Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: Warning: All Name Servers from the same Country / IP location.: 9 Name Servers, 1 Countries: CA A Info: Ipv4-Subnet-list: 9 Name Servers, 4 different subnets (first Byte): 15., 3., 35., 99., 6 different subnets (first two Bytes): 15.222., 15.223., 3.97., 35.182., 35.183., 99.79., 9 different subnets (first three Bytes): 15.222.19., 15.223.106., 15.223.21., 3.97.51., 3.97.58., 35.182.183., 35.183.157., 99.79.143., 99.79.16. A Good: Name Server IPv4-addresses from different subnet found: A Good: Nameserver supports Echo Capitalization: 9 good Nameserver X Nameserver Timeout checking Echo Capitalization: ns1.duckdns.org / 99.79.143.35 X Nameserver Timeout checking Echo Capitalization: ns2.duckdns.org X Nameserver Timeout checking Echo Capitalization: ns2.duckdns.org / 35.182.183.211 X Nameserver Timeout checking Echo Capitalization: ns3.duckdns.org / 35.183.157.249 X Nameserver Timeout checking Echo Capitalization: ns4.duckdns.org / 3.97.51.116 X Nameserver Timeout checking Echo Capitalization: ns5.duckdns.org X Nameserver Timeout checking Echo Capitalization: ns6.duckdns.org X Nameserver Timeout checking Echo Capitalization: ns7.duckdns.org X Nameserver Timeout checking Echo Capitalization: ns8.duckdns.org A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 9 good Nameserver X Nameserver Timeout checking EDNS512: ns1.duckdns.org X Nameserver Timeout checking EDNS512: ns1.duckdns.org / 99.79.143.35 X Nameserver Timeout checking EDNS512: ns2.duckdns.org X Nameserver Timeout checking EDNS512: ns2.duckdns.org / 35.182.183.211 X Nameserver Timeout checking EDNS512: ns3.duckdns.org / 35.183.157.249 X Nameserver Timeout checking EDNS512: ns4.duckdns.org / 3.97.51.116 X Nameserver Timeout checking EDNS512: ns5.duckdns.org X Nameserver Timeout checking EDNS512: ns6.duckdns.org X Nameserver Timeout checking EDNS512: ns6.duckdns.org / 3.97.58.28 X Nameserver Timeout checking EDNS512: ns7.duckdns.org X Nameserver Timeout checking EDNS512: ns9.duckdns.org X Nameserver Timeout checking EDNS512: ns9.duckdns.org / 15.222.19.97 Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 99.79.143.35: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns1.duckdns.org / 99.79.143.35: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org: OP100: ok. FLAGS: fatal timeout. 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 35.182.183.211: OP100: ok. FLAGS: ok. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns2.duckdns.org / 35.182.183.211: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 35.183.157.249: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns3.duckdns.org / 35.183.157.249: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns4.duckdns.org: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns4.duckdns.org / 3.97.51.116: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns4.duckdns.org / 3.97.51.116: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns5.duckdns.org: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns5.duckdns.org / 99.79.16.64: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns5.duckdns.org / 99.79.16.64: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns6.duckdns.org: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. 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: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: fatal timeout. COOKIE: ok. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns6.duckdns.org / 3.97.58.28: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns6.duckdns.org / 3.97.58.28: OP100: ok. FLAGS: fatal timeout. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns7.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns7.duckdns.org: OP100: fatal timeout. FLAGS: fatal timeout. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns7.duckdns.org / 15.223.21.81: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns7.duckdns.org / 15.223.21.81: OP100: fatal timeout. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. 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: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns8.duckdns.org: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns8.duckdns.org / 15.223.106.16: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns8.duckdns.org / 15.223.106.16: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns9.duckdns.org: OP100: ok. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout. Nameserver doesn't pass all EDNS-Checks: ns9.duckdns.org / 15.222.19.97: 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. COOKIE: ok. CLIENTSUBNET: ok. Nameserver doesn't pass all EDNS-Checks: ns9.duckdns.org / 15.222.19.97: OP100: fatal timeout. FLAGS: fatal timeout. V1: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: fatal timeout. V1FLAGS: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: fatal timeout. V1DNSSEC: SOA NOT expected, but found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: ok. 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://zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:9e8:200c:7634:3631:c4ff:fec6:63a8 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://www.zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:9e8:200c:7634:3631:c4ff:fec6:63a8 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://zimmies.duckdns.org/.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://www.zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 http://www.zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.130.0.73, Status 404 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. http://zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:9e8:200c:7634:3631:c4ff:fec6:63a8, Status -14 http://zimmies.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 88.130.0.73, 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: No https + http status 200 with inline CSS / JavaScript found https://zimmies.duckdns.org/ 88.130.0.73 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://www.zimmies.duckdns.org/ 88.130.0.73 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://88.130.0.73/ 88.130.0.73 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://zimmies.duckdns.org/ 88.130.0.73 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://www.zimmies.duckdns.org/ 88.130.0.73 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://88.130.0.73/ 88.130.0.73 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. Warning: CSS / JavaScript found without GZip support. Send these ressources with GZip. 2 external CSS / JavaScript files without GZip found - 0 with GZip, 2 complete Warning: CSS / JavaScript files with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 3 external CSS / JavaScript 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, 3 complete. Warning: Images with a missing or too short Cache-Control header found. Browsers should cache and re-use these files. 3 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, 3 complete. A Good: All checked attribute values are enclosed in quotation marks (" or '). A Good: All img-elements have a valid alt-attribute.: 3 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: 3055136 milliseconds, 3055.136 seconds