| 1. General Results, most used to calculate the result |
A | name "mangobrave.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: 103088 (complete: 263653)
|
A | Good: No asked Authoritative Name Server had a timeout
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-1220.awsdns-24.org / 205.251.196.196: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-1220.awsdns-24.org / 2600:9000:5304:c400::1: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-1877.awsdns-42.co.uk / 205.251.199.85: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-1877.awsdns-42.co.uk / 2600:9000:5307:5500::1: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-22.awsdns-02.com / 205.251.192.22: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-22.awsdns-02.com / 2600:9000:5300:1600::1: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-680.awsdns-21.net / 205.251.194.168: Refused
|
X | Fatal error: Nameserver doesn't support TCP connection: ns-680.awsdns-21.net / 2600:9000:5302:a800::1: Refused
|
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.mangobrave.com
|
| 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 |
|
A |
|
A | Info:: 13 different Name Servers found: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, 13 Name Servers included in Delegation: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, 13 Name Servers included in 1 Zone definitions: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net, 1 Name Servers listed in SOA.Primary: a.gtld-servers.net.
|
A | Good: Only one SOA.Primary Name Server found.: a.gtld-servers.net.
|
A | Good: SOA.Primary Name Server included in the delegation set.: a.gtld-servers.net.
|
A | Good: All Name Server Domain Names have a Public Suffix.
|
A |
|
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-1220.awsdns-24.org
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-1877.awsdns-42.co.uk
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-22.awsdns-02.com
|
X | Fatal error: Nameserver doesn't support EDNS with max. 512 Byte Udp payload or sends more then 512 Bytes: ns-680.awsdns-21.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-1220.awsdns-24.org / 205.251.196.196: 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-1220.awsdns-24.org / 2600:9000:5304:c400::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-1877.awsdns-42.co.uk / 205.251.199.85: 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-1877.awsdns-42.co.uk / 2600:9000:5307:5500::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-22.awsdns-02.com / 205.251.192.22: 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-22.awsdns-02.com / 2600:9000:5300:1600::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-680.awsdns-21.net / 205.251.194.168: 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-680.awsdns-21.net / 2600:9000:5302:a800::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 |
| 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: 55513 milliseconds, 55.513 seconds
|