| 1. General Results, most used to calculate the result |
A | name "srv-itrz-000192.static.itebo.de" is subdomain, public suffix is ".de", top-level-domain is ".de", top-level-domain-type is "country-code", Country is Germany, tld-manager is "DENIC eG", num .de-domains preloaded: 9732 (complete: 245733)
|
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.
|
X | Fatal error: Nameserver doesn't support TCP connection: f.nic.de: 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: l.de.net: 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: _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Domainname: _mta-sts.srv-itrz-000192.static.itebo.de
|
B | Bad: _mta-sts TXT found, but invalid
|
| 2. Header-Checks |
U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
A | Info:: 2 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 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.a.ns14.net (62.116.131.31, 62.116.159.231), b.ns14.net (2001:8d8:580:401:217:160:113:32, 217.160.113.231, 217.160.113.32), c.ns14.net (195.34.161.195, 2a01:130:2000:118:89:146:248:231, 89.146.248.231), d.ns14.net (2607:f1c0:1800:8091:74:208:254:254, 74.208.254.231, 74.208.254.254)
|
A | Good (1 - 3.0):: An average of 0.5 queries per domain name server required to find all ip addresses of all name servers.
|
A | Info:: 4 different Name Servers found: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net, 4 Name Servers included in Delegation: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net, 4 Name Servers included in 1 Zone definitions: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net, 1 Name Servers listed in SOA.Primary: a.ns14.net.
|
A | Good: Only one SOA.Primary Name Server found.: a.ns14.net.
|
A | Good: SOA.Primary Name Server included in the delegation set.: a.ns14.net.
|
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: a.ns14.net, b.ns14.net, c.ns14.net, d.ns14.net
|
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: Some Name Servers have IPv6 addresses: 3 Name Servers with IPv6 found (1 Name Servers without IPv6)
|
| 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.: 4 Name Servers, 1 Top Level Domain: net
|
| 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: ns14.net
|
A | Good: Name servers with different Country locations found: 4 Name Servers, 2 Countries: DE, US
|
A | Info: Ipv4-Subnet-list: 8 Name Servers, 5 different subnets (first Byte): 195., 217., 62., 74., 89., 5 different subnets (first two Bytes): 195.34., 217.160., 62.116., 74.208., 89.146., 6 different subnets (first three Bytes): 195.34.161., 217.160.113., 62.116.131., 62.116.159., 74.208.254., 89.146.248.
|
A | Good: Name Server IPv4-addresses from different subnet found:
|
A | Info: IPv6-Subnet-list: 3 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2607:, 2a01:, 3 different subnets (first two blocks): 2001:08d8:, 2607:f1c0:, 2a01:0130:, 3 different subnets (first three blocks): 2001:08d8:0580:, 2607:f1c0:1800:, 2a01:0130:2000:, 3 different subnets (first four blocks): 2001:08d8:0580:0401:, 2607:f1c0:1800:8091:, 2a01:0130:2000:0118:
|
A | Excellent: Every Name Server IPv6-address starts with an unique Hex-block
|
A | Good: Nameserver supports TCP connections: 2 good Nameserver
|
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: a.ns14.net
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: b.ns14.net
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: c.ns14.net
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: d.ns14.net
|
A | Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
|
A | Good: All SOA have the same Serial Number
|
A | Good: CAA entries found, creating certificate is limited: buypass.no is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: mail is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: sectigo.com is allowed to create certificates
|
A | Good: CAA entries found, creating certificate is limited: digicert.com is allowed to create wildcard-certificates
|
A | Good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create wildcard-certificates
|
| Warning: Unknown CAA found: mail isn't defined. Unknown entry. May be wrong written, may be not longer valid. May be a missing entry in this tool.
|
| 4. Content- and Performance-critical Checks |
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: 90566 milliseconds, 90.566 seconds
|