1. General Results, most used to calculate the result A name "test-dev-customer-portal.jibo.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: 85538 (complete: 220007) 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. 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.test-dev-customer-portal.jibo.com 2. Header-Checks (alpha, started 2022-10-23, may be buggy / incomplete) U No https result with http status 2** or 4** (standard-check) found, no header checked. 3. DNS- and NameServer - Checks A Info:: 8 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers. A Info:: 8 Queries complete, 8 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-02.azure-dns.com (2603:1061:0:700::2, 40.90.4.2), ns2-02.azure-dns.net (2620:1ec:8ec:700::2, 64.4.48.2), ns3-02.azure-dns.org (204.14.183.2, 2a01:111:4000:700::2), ns4-02.azure-dns.info (208.84.5.2, 2620:1ec:bda:700::2) A Good (1 - 3.0):: An average of 2.0 queries per domain name server required to find all ip addresses of all name servers. A Info:: 4 different Name Servers found: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 4 Name Servers included in Delegation: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 4 Name Servers included in 1 Zone definitions: ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info, 1 Name Servers listed in SOA.Primary: ns1-02.azure-dns.com. A Good: Only one SOA.Primary Name Server found.: ns1-02.azure-dns.com. A Good: SOA.Primary Name Server included in the delegation set.: ns1-02.azure-dns.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: 4 Name Servers, 4 different subnets (first Byte): 150., 204., 208., 40., 4 different subnets (first two Bytes): 150.171., 204.14., 208.84., 40.90., 4 different subnets (first three Bytes): 150.171.21., 204.14.183., 208.84.5., 40.90.4. A Excellent: Every Name Server IPv4-address starts with an unique Byte. A Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 3 different subnets (first block): 2603:, 2620:, 2a01:, 3 different subnets (first two blocks): 2603:1061:, 2620:01ec:, 2a01:0111:, 4 different subnets (first three blocks): 2603:1061:0000:, 2620:01ec:08ec:, 2620:01ec:0bda:, 2a01:0111:4000:, 4 different subnets (first four blocks): 2603:1061:0000:0700:, 2620:01ec:08ec:0700:, 2620:01ec:0bda:0700:, 2a01:0111:4000:0700: A Good: Name Server IPv6 addresses from different subnets found. A Good: Nameserver supports TCP connections: 8 good Nameserver A Good: Nameserver supports Echo Capitalization: 8 good Nameserver A Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns1-02.azure-dns.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-02.azure-dns.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. 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 Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask. 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: 51177 milliseconds, 51.177 seconds