1. General Results, most used to calculate the result A name "belladonnadubai.com" is domain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services" 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: ns-107.awsdns-13.com / 205.251.192.107: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-107.awsdns-13.com / 2600:9000:5300:6b00::1: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-1287.awsdns-32.org / 205.251.197.7: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-1287.awsdns-32.org / 2600:9000:5305:700::1: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-1696.awsdns-20.co.uk / 205.251.198.160: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-1696.awsdns-20.co.uk / 2600:9000:5306:a000::1: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-857.awsdns-43.net / 205.251.195.89: Refused X Fatal error: Nameserver doesn't support TCP connection: ns-857.awsdns-43.net / 2600:9000:5303:5900::1: Refused 2. Header-Checks 3. DNS- and NameServer - Checks A Good: Nameserver supports Echo Capitalization: 8 good Nameserver X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-107.awsdns-13.com X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-1287.awsdns-32.org X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-1696.awsdns-20.co.uk X Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-857.awsdns-43.net A Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 13 good Nameserver Nameserver doesn't pass all EDNS-Checks: ns-107.awsdns-13.com / 205.251.192.107: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-107.awsdns-13.com / 2600:9000:5300:6b00::1: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-1287.awsdns-32.org / 205.251.197.7: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-1287.awsdns-32.org / 2600:9000:5305:700::1: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-1696.awsdns-20.co.uk / 205.251.198.160: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-1696.awsdns-20.co.uk / 2600:9000:5306:a000::1: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-857.awsdns-43.net / 205.251.195.89: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result. Nameserver doesn't pass all EDNS-Checks: ns-857.awsdns-43.net / 2600:9000:5303:5900::1: OP100: no result. FLAGS: no result. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: no result. V1DNSSEC: ok. 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 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: 36557 milliseconds, 36.557 seconds