Check DNS, Urls + Redirects, Certificates and Content of your Website


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.




X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
08.11.2019 07:22:18


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mytel.mm.com
A

yes
1
0

AAAA

yes


www.mytel.mm.com
A

yes
1
0

AAAA

yes



2. DNSSEC

Info: The Xml-split has triggered some hidden bugs. Now it looks ok.
If root or the top level zone isn't validated, it's buggy.
Both green and your domain is red -> it's your domain.

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.11.2019, 00:00:00 +, Signature-Inception: 31.10.2019, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com
1 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.11.2019, 05:00:00 +, Signature-Inception: 08.11.2019, 04:00:00 +, KeyTag 22545, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 22545 used to validate the DS RRSet in the parent zone



3 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 12163, Flags 256



Public Key with Algorithm 8, KeyTag 17708, Flags 256



Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 22.11.2019, 19:24:21 +, Signature-Inception: 07.11.2019, 19:19:21 +, KeyTag 30909, Signer-Name: com



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: mm.com
mm.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: mytel.mm.com
mytel.mm.com
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.mytel.mm.com
www.mytel.mm.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.mytel.mm.com
  ns3.dns.com

mytel.mm.com
  ns3.dns.com
121.12.104.109
Dongguan/Guangdong/China (CN) - Guangdong Network of ChinaTelecom


 
183.2.194.173
Guangzhou/Guangdong/China (CN) - CHINANET Guangdong province network


 
218.98.111.109
Frankfurt am Main/Hesse/Germany (DE) - Zenlayer Inc


T 
218.98.111.173
Frankfurt am Main/Hesse/Germany (DE) - Zenlayer Inc


 
2607:a400:1:19::6c
Los Angeles/California/United States (US) - Zenlayer Inc

mm.com
  ns3.dns.com


  ns4.dns.com

com
  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


4. SOA-Entries


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1573194110
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:com
Zone-Name:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1573194125
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:12


Domain:mm.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:mm.com
Zone-Name:
Primary:ns3.dns.com
Mail:admin.dns.com
Serial:1546952909
Refresh:7200
Retry:3600
Expire:1209600
TTL:1800
num Entries:1


Domain:mytel.mm.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:mytel.mm.com
Zone-Name:
Primary:ns3.dns.com
Mail:admin.dns.com
Serial:1546952909
Refresh:7200
Retry:3600
Expire:1209600
TTL:1800
num Entries:4


Domain:www.mytel.mm.com
Zone-Name:
Primary:ns3.dns.com
Mail:admin.dns.com
Serial:1546952909
Refresh:7200
Retry:3600
Expire:1209600
TTL:1800
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "mytel.mm.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns3.dns.com
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns3.dns.com / 121.12.104.109
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns3.dns.com / 183.2.194.173
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns3.dns.com / 218.98.111.109
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns3.dns.com / 218.98.111.173
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns3.dns.com / 2607:a400:1:19::6c
XFatal error: Nameserver doesn't support echo capitalization. That's critical if you want to create Letsencrypt certificates. Read https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00 (2008). If a dns client asks "ExAmPlE.cOm", the name server must answer with the same name, not with "example.com". Creating Letsencrypt certificates isn't possible. Your name server provider must update the software.: ns4.dns.com

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 5 good Nameserver
XNameserver Timeout checking EDNS512: ns3.dns.com / 218.98.111.173
Nameserver doesn't pass all EDNS-Checks: ns3.dns.com: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns3.dns.com / 218.98.111.109: OP100: ok. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: fatal timeout.
Nameserver doesn't pass all EDNS-Checks: ns3.dns.com / 218.98.111.173: OP100: ok. FLAGS: ok. V1: fatal timeout. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: ok. NSID: ok. COOKIE: fatal timeout. CLIENTSUBNET: fatal timeout.
AGood: 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.

3. Content- and Performance-critical Checks

AGood: 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
ADuration: 274796 milliseconds, 274.796 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses (alpha)

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.mytel.mm.com
0

no CAA entry found
1
0
mytel.mm.com
0

no CAA entry found
1
0
mm.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
mm.com


2
2
mytel.mm.com

ok
1
0
www.mytel.mm.com

ok
1
0
_acme-challenge.mytel.mm.com


2
2
_acme-challenge.www.mytel.mm.com

missing entry or wrong length
1
0
_acme-challenge.mytel.mm.com.mm.com

perhaps wrong
1
0
_acme-challenge.mytel.mm.com.mytel.mm.com

perhaps wrong
1
0
_acme-challenge.www.mytel.mm.com.mytel.mm.com

perhaps wrong
1
0
_acme-challenge.www.mytel.mm.com.www.mytel.mm.com

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=68289063-0066-4e35-bfbe-a27f5b890d17


Last Result: https://check-your-website.server-daten.de/?q=mytel.mm.com - 2019-11-08 07:22:18


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=mytel.mm.com" target="_blank">Check this Site: mytel.mm.com</a>