| 1. General Results, most used to calculate the result |
| A | name "athome.dickeys.com" is subdomain, 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: 57967 (complete: 151507)
|
| A | Good: All ip addresses are public addresses
|
| Warning: Only one ip address found: athome.dickeys.com has only one ip address.
|
| Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: athome.dickeys.com has no ipv6 address.
|
| 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.
|
| A | Good: every https has a Strict Transport Security Header
|
| A | Good: HSTS max-age is long enough, 31536000 seconds = 365 days
|
| A | Good: HSTS has includeSubdomains - 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 (3 urls)
|
| https://athome.dickeys.com/ 34.236.80.172
|
| Url with incomplete Content-Type - header - missing charset
|
| https://athome.dickeys.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Url with incomplete Content-Type - header - missing charset
|
| https://34.236.80.172/ 34.236.80.172
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://athome.dickeys.com/ 34.236.80.172
| https://athome.dickeys.com/
| Correct redirect http - https with the same domain name
|
| N | https://34.236.80.172/ 34.236.80.172
|
| Error - Certificate isn't trusted, RemoteCertificateNameMismatch
|
| 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 athome.dickeys.com, 1 ip addresses, 1 different http results.
|
| 2. Header-Checks |
| 3. DNS- and NameServer - Checks |
| A | Info:: 7 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
|
| A | Info:: 7 Queries complete, 7 with IPv6, 0 with IPv4.
|
| A | Good: All DNS Queries done via IPv6.
|
| Ok (4 - 8):: An average of 3.5 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns3.worldnic.com, ns4.worldnic.com, 2 Name Servers included in Delegation: ns3.worldnic.com, ns4.worldnic.com, 2 Name Servers included in 1 Zone definitions: ns3.worldnic.com, ns4.worldnic.com, 1 Name Servers listed in SOA.Primary: ns3.worldnic.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns3.worldnic.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns3.worldnic.com.
|
| 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: 2 Name Servers, 1 different subnets (first Byte): 207., 1 different subnets (first two Bytes): 207.204., 2 different subnets (first three Bytes): 207.204.21., 207.204.40.
|
| A | Good: Name Server IPv4-addresses from different subnet 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
|
| Nameserver doesn't pass all EDNS-Checks: dns-external-master.amazon.com: 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.
|
| Nameserver doesn't pass all EDNS-Checks: dns-external-master.amazon.com: 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.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.p31.dynect.net / 208.78.70.31: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (proxy-121-defra.hivecast-121-defra.as15135.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns1.p31.dynect.net / 2001:500:90:1::31: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (proxy-114-defra.hivecast-114-defra.as15135.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns2.p31.dynect.net / 204.13.250.31: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (proxy-74-defra.hivecast-74-defra.as15135.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.p31.dynect.net / 208.78.71.31: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (proxy-73-defra.hivecast-73-defra.as15135.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.p31.dynect.net / 2001:500:94:1::31: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (proxy-74-defra.hivecast-74-defra.as15135.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.worldnic.com: 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.
|
| Nameserver doesn't pass all EDNS-Checks: ns3.worldnic.com / 207.204.40.102: 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 (worldnic). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns4.p31.dynect.net / 204.13.251.31: OP100: ok. FLAGS: ok. V1: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. V1OP100: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found, no OPT100 expected, no OPT100 found. V1FLAGS: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. DNSSEC: ok. V1DNSSEC: SOA NOT expected and NOT found, BADVER expected, NOERR found, Version 0 expectend and found. NSID: ok (proxy-329-nlams2.hivecast-329-nlams2.as15135.net). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: ns4.worldnic.com / 207.204.21.102: 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 (worldnic). COOKIE: ok. CLIENTSUBNET: ok.
|
| Nameserver doesn't pass all EDNS-Checks: pdns1.ultradns.net: 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 |
| https://athome.dickeys.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
|
| A | Good: No https + http status 200 with inline CSS / JavaScript found
|
| 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
|
| A | Duration: 345746 milliseconds, 345.746 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)