1. General Results, most used to calculate the result A name "mta9-2.directcrm.ru" is subdomain, public suffix is ".ru", top-level-domain is ".ru", top-level-domain-type is "country-code", Country is Russian Federation (the), tld-manager is "Coordination Center for TLD RU", num .ru-domains preloaded: 1928 (complete: 175327) A good: All ip addresses are public addresses A Good: Minimal 2 ip addresses per domain name found: mta9-2.directcrm.ru has 9 different ip addresses (authoritative). 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: mta9-2.directcrm.ru 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 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: More then one ip address per domain name found, checking all ip addresses the same http status and the same certificate found: Domain mta9-2.directcrm.ru, 9 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 mta9-2.directcrm.ru, 9 ip addresses. 2. DNS- and NameServer - Checks A Info:: 22 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 6 Name Servers. A Info:: 22 Queries complete, 21 with IPv6, 1 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-02.azure-dns.com (2603:1061::2, 40.90.4.2), ns2-02.azure-dns.net (2620:1ec:8ec::2, 64.4.48.2), ns3-02.azure-dns.org (13.107.24.2, 2a01:111:4000::2), ns4-02.azure-dns.info (13.107.160.2, 2620:1ec:bda::2) Ok (4 - 8):: An average of 3.7 queries per domain name server required to find all ip addresses of all name servers. A Info:: 6 different Name Servers found: ns1.yandexcloud.net, ns1-02.azure-dns.com, ns2.yandexcloud.net, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 6 Name Servers included in Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 6 Name Servers included in 2 Zone definitions: ns1.yandexcloud.net, ns2.yandexcloud.net, ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 2 Name Servers listed in SOA.Primary: ns1.yandexcloud.net, ns1-02.azure-dns.com. Error: Different SOA.Primary Name Servers found, different SOA Definitions.: ns1.yandexcloud.net,ns1-02.azure-dns.com. Error: SOA.Primary Name Server not included in the delegation set.: ns1.yandexcloud.net,ns1-02.azure-dns.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.: ns1.yandexcloud.net (2a0d:d6c1:0:1a::1b4): Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info. 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.: ns1-02.azure-dns.com (2603:1061::2): Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, Zone: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. 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.: ns2.yandexcloud.net (2a0d:d6c1:0:1a::2c9): Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. Name Servers defined in Delegation, missing in Zone: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info. 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.: ns2-02.azure-dns.net (2620:1ec:8ec::2): Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, Zone: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. 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.: ns3-02.azure-dns.org (2a01:111:4000::2): Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, Zone: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.net. 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.: ns4-02.azure-dns.info (2620:1ec:bda::2): Delegation: ns1-02.azure-dns.com, ns1.yandexcloud.net, ns2-02.azure-dns.net, ns2.yandexcloud.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, Zone: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info. Name Servers defined in Delegation, missing in Zone: ns1.yandexcloud.net, ns2.yandexcloud.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: 6 different Name Servers found A Good: Name servers with different Top Level Domains / Public Suffix List entries found: 6 Name Servers, 5 Top Level Domains: com, org, net, info, yandexcloud.net A Good: Name Servers with different domain names found.: 5 different Domains found A Good: Name servers with different Country locations found: 6 Name Servers, 4 Countries: CA, IE, RU, US A A Info: IPv6-Subnet-list: 6 Name Servers with IPv6, 4 different subnets (first block): 2603:, 2620:, 2a01:, 2a0d:, 4 different subnets (first two blocks): 2603:1061:, 2620:01ec:, 2a01:0111:, 2a0d:d6c1:, 5 different subnets (first three blocks): 2603:1061:0000:, 2620:01ec:08ec:, 2620:01ec:0bda:, 2a01:0111:4000:, 2a0d:d6c1:0000:, 5 different subnets (first four blocks): 2603:1061:0000:0000:, 2620:01ec:08ec:0000:, 2620:01ec:0bda:0000:, 2a01:0111:4000:0000:, 2a0d:d6c1:0000:001a: A Good: Name Server IPv6 addresses from different subnets found. A Info: Nameserver mit different domain names found. May be a problem with DNS-Updates 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.yandexcloud.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. X Fatal error: Nameservers with different SOA Serial Numbers A good: CAA entries found, creating certificate is limited: globalsign.com is allowed to create certificates A good: CAA entries found, creating certificate is limited: godaddy.com is allowed to create certificates A good: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates 3. Content- and Performance-critical Checks http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.230 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.231 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.232 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.233 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.234 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.235 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.236 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.237 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. http://mta9-2.directcrm.ru/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 176.107.162.238 Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. 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: 508803 milliseconds, 508.803 seconds