| 1. General Results, most used to calculate the result |
| A | name "mcp.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: 83852 (complete: 216710)
|
| A | DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
|
| 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: mcp.com: Timeout
|
| X | Fatal error: Nameserver isn't defined or has timeout
|
| 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.mcp.com
|
| 2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05) |
| U |
|
| No https result with http status 2** or 4** (standard-check) found, no header checked.
|
| 3. DNS- and NameServer - Checks |
| A | Info:: 4 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
|
| A | Info:: 4 Queries complete, 2 with IPv6, 2 with IPv4.
|
| Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
|
| 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.mcp.com (62.92.114.179), ns2.mcp.com (212.4.59.46)
|
| A | Good (1 - 3.0):: An average of 1.3 queries per domain name server required to find all ip addresses of all name servers.
|
| A | Info:: 4 different Name Servers found: mcp.com, ns.mcp.com, ns1.mcp.com, ns2.mcp.com, 2 Name Servers included in Delegation: ns1.mcp.com, ns2.mcp.com, 3 Name Servers included in 2 Zone definitions: ns.mcp.com, ns1.mcp.com, ns2.mcp.com, 1 Name Servers listed in SOA.Primary: mcp.com.
|
| A | Good: Only one SOA.Primary Name Server found.: mcp.com.
|
| Error: SOA.Primary Name Server not included in the delegation set.: mcp.com.
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns.mcp.com (62.92.114.179): Delegation: ns1.mcp.com, ns2.mcp.com, Zone: ns.mcp.com, ns1.mcp.com, ns2.mcp.com. Name Servers defined in Zone, missing in Delegation: ns.mcp.com.
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.mcp.com (62.92.114.179): Delegation: ns1.mcp.com, ns2.mcp.com, Zone: ns.mcp.com, ns1.mcp.com, ns2.mcp.com. Name Servers defined in Zone, missing in Delegation: ns.mcp.com.
|
| X | Fatal: Inconsistency 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. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.mcp.com (212.4.59.46): Delegation: ns1.mcp.com, ns2.mcp.com, Zone: ns.mcp.com, ns1.mcp.com, ns2.mcp.com. Name Servers defined in Zone, missing in Delegation: ns.mcp.com.
|
| A | Good: All Name Server Domain Names have a Public Suffix.
|
| Error: Name Server Domain Names with Public Suffix and without ip address found.: 1 Name Servers without ipv4 and ipv6: 1
|
|
|
| A | Good: Minimal 2 different name servers (public suffix and public ip address) found: 3 different Name Servers found
|
| Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 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: com
|
| A | Good: Name Servers with different domain names found.: 2 different Domains found
|
| Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: NO
|
| A | Info: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 212., 62., 2 different subnets (first two Bytes): 212.4., 62.92., 2 different subnets (first three Bytes): 212.4.59., 62.92.114.
|
| A | Good: Name Server IPv4-addresses from different subnet found:
|
| Nameserver doesn't pass all EDNS-Checks: mcp.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: mcp.com: OP100: fatal timeout. FLAGS: fatal timeout. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: fatal timeout. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: fatal timeout. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
|
| 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: 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: 39997 milliseconds, 39.997 seconds
|
%22%20style=%22background-color:rgb(255,255,255)%22%3e%3c/svg%3e)