1. General Results, most used to calculate the result A name "penascoth.com" is domain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 55723 (complete: 142558) A good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: penascoth.com has 2 different ip addresses (authoritative). A Good: Minimal 2 ip addresses per domain name found: www.penascoth.com has 2 different ip addresses (authoritative). A Good: Ipv4 and Ipv6 addresses per domain name found: penascoth.com has 1 ipv4, 1 ipv6 addresses A Good: Ipv4 and Ipv6 addresses per domain name found: www.penascoth.com has 1 ipv4, 1 ipv6 addresses A good: No asked Authoritative Name Server had a timeout 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: All urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset) http://penascoth.com/ 74.208.236.113 174f7b5baced73b551d27a0b04412104=89a313d7ae015faabccf0d1655907915; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://penascoth.com/ 2607:f1c0:100f:f000::224 174f7b5baced73b551d27a0b04412104=2f99d4bee729943e49a2334b47de8582; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.penascoth.com/ 74.208.236.113 174f7b5baced73b551d27a0b04412104=786ad295b6eec4ffae9bfa5bc8b38d27; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. http://www.penascoth.com/ 2607:f1c0:100f:f000::224 174f7b5baced73b551d27a0b04412104=3c7f3a8dccb23447facc9a296c7d9bc2; path=/; HttpOnly Fatal: Cookie sent via http. Never send Cookies / Session-Cookies via http. If a user uses an insecure WLan and if the same cookie is used to managed the authenticated session, it's possible to hack that user. Same with HttpOnly - without https that's only decorative. B http://penascoth.com/ 74.208.236.113 174f7b5baced73b551d27a0b04412104=89a313d7ae015faabccf0d1655907915; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://penascoth.com/ 2607:f1c0:100f:f000::224 174f7b5baced73b551d27a0b04412104=2f99d4bee729943e49a2334b47de8582; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.penascoth.com/ 74.208.236.113 174f7b5baced73b551d27a0b04412104=786ad295b6eec4ffae9bfa5bc8b38d27; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. B http://www.penascoth.com/ 2607:f1c0:100f:f000::224 174f7b5baced73b551d27a0b04412104=3c7f3a8dccb23447facc9a296c7d9bc2; path=/; HttpOnly Cookie without a SameSite-Attribute. Possible values are: Strict/Lax/None. Cookie may not work as expected, if "None" is wanted, but browsers use "Lax" as default value. 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: 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. P https://penascoth.com/ 74.208.236.113 Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome) P https://penascoth.com/ 2607:f1c0:100f:f000::224 Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome) P https://www.penascoth.com/ 74.208.236.113 Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome) P https://www.penascoth.com/ 2607:f1c0:100f:f000::224 Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome) P https://74.208.236.113/ 74.208.236.113 Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome) P https://[2607:f1c0:100f:f000:0000:0000:0000:0224]/ 2607:f1c0:100f:f000::224 Error creating a TLS-Connection: IANA TLS Alert No. 80, internal_error. An internal error unrelated to the peer or the correctness of the protocol (such as a memory allocation failure) makes it impossible to continue. SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla) / ERR_SSL_PROTOCOL_ERROR (Chrome) 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 penascoth.com, 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.penascoth.com, 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 penascoth.com, 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.penascoth.com, 2 ip addresses. 2. DNS- and NameServer - Checks A Info:: 52 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 52 Queries complete, 52 with IPv6, 0 with IPv4. A Good: All DNS Queries done via IPv6. Bad (greater 8):: An average of 13.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns1045.ui-dns.biz, ns1045.ui-dns.com, ns1045.ui-dns.de, ns1045.ui-dns.org, 4 Name Servers included in Delegation: ns1045.ui-dns.biz, ns1045.ui-dns.com, ns1045.ui-dns.de, ns1045.ui-dns.org, 4 Name Servers included in 1 Zone definitions: ns1045.ui-dns.biz, ns1045.ui-dns.com, ns1045.ui-dns.de, ns1045.ui-dns.org, 1 Name Servers listed in SOA.Primary: ns1045.ui-dns.com. A Good: Only one SOA.Primary Name Server found.: ns1045.ui-dns.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1045.ui-dns.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: ns1045.ui-dns.biz, ns1045.ui-dns.com, ns1045.ui-dns.de, ns1045.ui-dns.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: 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: de, org, com, biz A Good: Name Servers with different domain names found.: 4 different Domains found Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: DE A Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 217., 1 different subnets (first two Bytes): 217.160., 4 different subnets (first three Bytes): 217.160.80., 217.160.81., 217.160.82., 217.160.83. 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): 2001:, 1 different subnets (first two blocks): 2001:08d8:, 1 different subnets (first three blocks): 2001:08d8:00fe:, 1 different subnets (first four blocks): 2001:08d8:00fe:0053: Fatal: All Name Server IPv6 addresses from the same subnet. 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 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. 3. Content- and Performance-critical Checks http://penascoth.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 74.208.236.113 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://penascoth.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::224 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.penascoth.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 74.208.236.113 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://www.penascoth.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 2607:f1c0:100f:f000::224 Fatal: Check of /.well-known/acme-challenge/random-filename has a http status 201, 202, 203 or 204. Creating a Letsencrypt certificate via http-01 challenge can't work. A http status 301-309 (Redirect to another domain or port 80 / 443) or a http status 404 - Not Found is expected, if the test file doesn't exist. Looks like the webserver isn't configured, perhaps it's an answer of your hoster. 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 Info: Different Server-Headers found A Duration: 86737 milliseconds, 86.737 seconds