| 1. General Results, most used to calculate the result |
| A | name "server.germancoding.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: server.germancoding.com has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: server.germancoding.com 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: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 63072000 seconds = 730 days
|
| 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)
|
| A | http://server.germancoding.com/ 176.9.103.107
| https://server.germancoding.com/
| Correct redirect http - https with the same domain name
|
| A | http://server.germancoding.com/ 2a01:4f8:151:506c::2
| https://server.germancoding.com/
| Correct redirect http - https with the same domain name
|
| M | https://176.9.103.107/ 176.9.103.107
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| M | https://[2a01:04f8:0151:506c:0000:0000:0000:0002]/ 2a01:4f8:151:506c::2
|
| Misconfiguration - main pages should never send http status 400 - 499
|
| N | https://176.9.103.107/ 176.9.103.107
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| N | https://[2a01:04f8:0151:506c:0000:0000:0000:0002]/ 2a01:4f8:151:506c::2
|
| 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.germancoding.com, 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.germancoding.com, 2 ip addresses, 1 different http results.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 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.hosting.de (134.0.30.178, 2a03:2900:3:1::2), ns2.hosting.de (194.50.113.2, 2001:4d8f:2::2), ns3.hosting.de (194.126.196.2, 2a03:2902:3:1::2)
|
| A | Good (1 - 3.0):: An average of 0.7 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 3 different Name Servers found: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de, 3 Name Servers included in Delegation: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de, 3 Name Servers included in 1 Zone definitions: ns1.hosting.de, ns2.hosting.de, ns3.hosting.de, 1 Name Servers listed in SOA.Primary: ns1.hosting.de.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.hosting.de.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.hosting.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: ns1.hosting.de, ns2.hosting.de, ns3.hosting.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 | Good: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
|
| A | Good: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 Name Servers, 1 Top Level Domain: de
|
| 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: hosting.de
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: DE
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 134., 194., 3 different subnets (first two Bytes): 134.0., 194.126., 194.50., 3 different subnets (first three Bytes): 134.0.30., 194.126.196., 194.50.113.
|
| 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:, 2a03:, 3 different subnets (first two blocks): 2001:4d8f:, 2a03:2900:, 2a03:2902:, 3 different subnets (first three blocks): 2001:4d8f:0002:, 2a03:2900:0003:, 2a03:2902:0003:, 3 different subnets (first four blocks): 2001:4d8f:0002:0000:, 2a03:2900:0003:0001:, 2a03:2902:0003:0001:
|
| A | Good: Name Server IPv6 addresses from different subnets found.
|
| A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| A | Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
|
| A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
|
| Nameserver doesn't pass all EDNS-Checks: ns1.hosting.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
|
| A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
| 4. 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 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 | 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
|
| https://server.germancoding.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| 3.237 seconds
| Warning: 404 needs more then one second
|
| https://176.9.103.107/ 176.9.103.107
| 3.300 seconds
| Warning: 404 needs more then one second
|
| https://[2a01:04f8:0151:506c:0000:0000:0000:0002]/ 2a01:4f8:151:506c::2
| 3.337 seconds
| Warning: 404 needs more then one second
|
| A | Duration: 73086 milliseconds, 73.086 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)