| 1. General Results, most used to calculate the result |
| A | name "secure.comodo.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: 108094 (complete: 276475)
|
| A | Good: All ip addresses are public addresses
|
| A | Good: Minimal 2 ip addresses per domain name found: secure.comodo.com has 2 different ip addresses (authoritative).
|
| A | Good: Ipv4 and Ipv6 addresses per domain name found: secure.comodo.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 | https://secure.comodo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| https://secure.comodo.com/.well-known/acme-challenge/purchase.php?
| Correct redirect https to https
|
| 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.
|
| 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 (1 urls)
|
| https://secure.comodo.com/ 2610:1c8:1b::1
|
| Url with incomplete Content-Type - header - missing charset
|
| A | http://secure.comodo.com/ 2610:1c8:1b::1
| https://secure.comodo.com/
| Correct redirect http - https with the same domain name
|
| B | https://secure.comodo.com/ 2610:1c8:1b::1
|
| Missing HSTS-Header
|
| B | https://secure.comodo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
|
| Missing HSTS-Header
|
| B | https://secure.comodo.com/.well-known/acme-challenge/purchase.php?
|
| Missing HSTS-Header
|
| B | https://secure.comodo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| PHPSESSID=um369lpmdn0rht5659bbq3ias3; path=/
| Cookie sent via https, but not marked as secure
|
| B | https://secure.comodo.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
| PHPSESSID=um369lpmdn0rht5659bbq3ias3; path=/
| 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.
|
| K | https://secure.comodo.com/ 104.37.183.1, Status -103
| https://secure.comodo.com/ 2610:1c8:1b::1, Status 200
| Configuration problem - different ip addresses with different status
|
| L | https://secure.comodo.com/.well-known/acme-challenge/purchase.php?
| https://secure.comodo.com/.well-known/acme-challenge/purchase.php?
| Error direct loop
|
| O | secure.comodo.com / 2610:1c8:1b::1 / 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. 5 Cipher Suites without Forward Secrecy found
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns1.belugacdn.com / 199.167.64.1: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns1.nurd.com / 199.167.64.4: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns2.belugacdn.com / 104.37.177.1: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
|
| X | Fatal error: Nameserver doesn't support TCP connection: ns2.nurd.com / 104.37.177.4: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
|
| 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 secure.comodo.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 secure.comodo.com, 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.secure.comodo.com
|
| 2. Header-Checks |
| F | secure.comodo.com 2610:1c8:1b::1
| Content-Security-Policy
| Critical: Missing Header:
|
| F | secure.comodo.com 2610:1c8:1b::1
| X-Content-Type-Options
| Critical: Missing Header:
|
| F | secure.comodo.com 2610:1c8:1b::1
| Referrer-Policy
| Critical: Missing Header:
|
| F | secure.comodo.com 2610:1c8:1b::1
| Permissions-Policy
| Critical: Missing Header:
|
| B | secure.comodo.com 2610:1c8:1b::1
| Cross-Origin-Embedder-Policy
| Info: Missing Header
|
| B | secure.comodo.com 2610:1c8:1b::1
| Cross-Origin-Opener-Policy
| Info: Missing Header
|
| B | secure.comodo.com 2610:1c8:1b::1
| Cross-Origin-Resource-Policy
| Info: Missing Header
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 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.nurd.com (199.167.64.4), ns2.nurd.com (104.37.177.4)
|
| A | Good (1 - 3.0):: An average of 1.0 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 2 different Name Servers found: ns1.nurd.com, ns2.nurd.com, 2 Name Servers included in Delegation: ns1.nurd.com, ns2.nurd.com, 2 Name Servers included in 1 Zone definitions: ns1.nurd.com, ns2.nurd.com, 1 Name Servers listed in SOA.Primary: ns1.nurd.com.
|
| A | Good: Only one SOA.Primary Name Server found.: ns1.nurd.com.
|
| A | Good: SOA.Primary Name Server included in the delegation set.: ns1.nurd.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, 2 different subnets (first Byte): 104., 199., 2 different subnets (first two Bytes): 104.37., 199.167., 2 different subnets (first three Bytes): 104.37.177., 199.167.64.
|
| A | Excellent: Every Name Server IPv4-address starts with an unique Byte.
|
| A | Good: Nameserver supports Echo Capitalization: 2 good Nameserver
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns1.nurd.com
|
| X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns2.nurd.com
|
| Nameserver doesn't pass all EDNS-Checks: ns1.belugacdn.com / 199.167.64.1: 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.belugacdn.com / 199.167.64.1: 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.belugacdn.com / 199.167.64.1: 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.belugacdn.com / 199.167.64.1: 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.belugacdn.com / 199.167.64.1: 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.nurd.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.nurd.com / 199.167.64.4: 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: ns2.belugacdn.com / 104.37.177.1: 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: ns2.nurd.com / 104.37.177.4: 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 |
| 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 | Good: All checked attribute values are enclosed in quotation marks (" or ').
|
| 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: 324133 milliseconds, 324.133 seconds
|