1. General Results, most used to calculate the result A name "foxhill67.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: 6491 (complete: 199710) A Good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: foxhill67.duckdns.org has 2 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.foxhill67.duckdns.org has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: foxhill67.duckdns.org has 1 ipv4, 1 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.foxhill67.duckdns.org has 1 ipv4, 1 ipv6 addresses A Good: No asked Authoritative Name Server had a timeout 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 (4 urls) http://foxhill67.duckdns.org/ 82.75.177.212 Url with incomplete Content-Type - header - missing charset http://www.foxhill67.duckdns.org/ 82.75.177.212 Url with incomplete Content-Type - header - missing charset http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212 Url with incomplete Content-Type - header - missing charset http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212 Url with incomplete Content-Type - header - missing charset H Fatal error: No https - result with http-status 200, no encryption 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://foxhill67.duckdns.org/ 82.75.177.212, Status 200 http://foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14 Configuration problem - different ip addresses with different status K http://www.foxhill67.duckdns.org/ 82.75.177.212, Status 200 http://www.foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14 Configuration problem - different ip addresses with different status K http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200 http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14 Configuration problem - different ip addresses with different status K http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200 http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14 Configuration problem - different ip addresses with different status V https://foxhill67.duckdns.org/ 82.75.177.212 Connect failure - perhaps firewall V https://foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab Connect failure - perhaps firewall V https://www.foxhill67.duckdns.org/ 82.75.177.212 Connect failure - perhaps firewall V https://www.foxhill67.duckdns.org/ 2001:1c06:2d00:0:c497:7653:8e74:54ab Connect failure - perhaps firewall V https://82.75.177.212/ 82.75.177.212 Connect failure - perhaps firewall V https://[2001:1c06:2d00:0000:c497:7653:8e74:54ab]/ 2001:1c06:2d00:0:c497:7653:8e74:54ab Connect failure - perhaps firewall 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 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 foxhill67.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 www.foxhill67.duckdns.org, 2 ip addresses. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain foxhill67.duckdns.org, 2 ip addresses. Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain www.foxhill67.duckdns.org, 2 ip addresses. 2. Header-Checks 3. DNS- and NameServer - Checks A Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 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) A Good (1 - 3.0):: An average of 0.3 queries per domain name server required to find all ip addresses of all name servers. A Info:: 6 different Name Servers found: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, 6 Name Servers included in Delegation: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.duckdns.org, 6 Name Servers included in 1 Zone definitions: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.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: 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: ns1.duckdns.org, ns2.duckdns.org, ns3.duckdns.org, ns4.duckdns.org, ns5.duckdns.org, ns6.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. A Good: All Name Server ip addresses are public. A Good: Minimal 2 different name servers (public suffix and public ip address) found: 6 different Name Servers found Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 6 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.: 6 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.: 6 Name Servers, 1 Countries: CA A Info: Ipv4-Subnet-list: 6 Name Servers, 3 different subnets (first Byte): 3., 35., 99., 4 different subnets (first two Bytes): 3.97., 35.182., 35.183., 99.79., 6 different subnets (first three Bytes): 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: 6 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver 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://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab 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.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab 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://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14 http://foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200 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://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2001:1c06:2d00:0:c497:7653:8e74:54ab, Status -14 http://www.foxhill67.duckdns.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 82.75.177.212, Status 200 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 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 Duration: 1418330 milliseconds, 1418.330 seconds