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



X

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

Checked:
14.09.2021 18:14:43


Older results

No older results found


1. IP-Addresses

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

yes
1
0

AAAA

yes


www.com.mm

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

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



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



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 26838, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 30.09.2021, 00:00:00 +, Signature-Inception: 09.09.2021, 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: mm
mm
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 18589, DigestType 2 and Digest CmZAPaLOtMOWB1BzkHTVynmTNLRcheP+3Xg44BokNdg=



1 RRSIG RR to validate DS RR found



RRSIG-Owner mm., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.09.2021, 05:00:00 +, Signature-Inception: 14.09.2021, 04:00:00 +, KeyTag 26838, Signer-Name: (root)



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 32298, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner mm., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 21.09.2021, 03:47:08 +, Signature-Inception: 14.09.2021, 01:13:02 +, KeyTag 18589, Signer-Name: mm



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



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

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



DS with Algorithm 8, KeyTag 22462, DigestType 2 and Digest VV5RdRmEhyI5ieA6LrgueLJ8dKty2PU8u+8fT1JILF8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com.mm., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.09.2021, 06:19:42 +, Signature-Inception: 11.09.2021, 08:25:01 +, KeyTag 32298, Signer-Name: mm



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



2 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 65160, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com.mm., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 18.09.2021, 00:55:57 +, Signature-Inception: 11.09.2021, 09:53:02 +, KeyTag 22462, Signer-Name: com.mm



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



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



A-Query sends a valid NSEC3 RR as result with the hashed query name "snr4p7vqet4l723h388kh8s47dvt8t6j" equal the hashed NSEC3-owner "snr4p7vqet4l723h388kh8s47dvt8t6j" and the hashed NextOwner "sntthgnpa2s87876ql4prtp267j34892". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NoData-Proof required and found.



CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "snr4p7vqet4l723h388kh8s47dvt8t6j" equal the hashed NSEC3-owner "snr4p7vqet4l723h388kh8s47dvt8t6j" and the hashed NextOwner "sntthgnpa2s87876ql4prtp267j34892". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed query name "snr4p7vqet4l723h388kh8s47dvt8t6j" equal the hashed NSEC3-owner "snr4p7vqet4l723h388kh8s47dvt8t6j" and the hashed NextOwner "sntthgnpa2s87876ql4prtp267j34892". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "snr4p7vqet4l723h388kh8s47dvt8t6j" equal the hashed NSEC3-owner "snr4p7vqet4l723h388kh8s47dvt8t6j" and the hashed NextOwner "sntthgnpa2s87876ql4prtp267j34892". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.com.mm) sends a valid NSEC3 RR as result with the hashed owner name "snr4p7vqet4l723h388kh8s47dvt8t6j" (unhashed: com.mm). So that's the Closest Encloser of the query name.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "6rjb905s2sht8t46ucmul1b24mh9rr8k" (unhashed: _tcp.com.mm) with the owner "6rc6gtupp695se4mhjlttenkknr7n095" and the NextOwner "6rl3njsrsljoiatfjas98vqr21ktaoa4". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: No Bitmap? Validated: RRSIG-Owner 6rc6gtupp695se4mhjlttenkknr7n095.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 18.09.2021, 16:49:28 +, Signature-Inception: 11.09.2021, 05:06:02 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "hrn8ah1gusncit04l31nu2c97i71a3h0" (unhashed: *.com.mm) with the owner "hrmb94bfq1nhglve1297595jooujpth0" and the NextOwner "hrno1q6at1b73estvj0mi96sqnjvdpm2". So that NSEC3 confirms the not-existence of the Wildcard expansion.
Bitmap: No Bitmap? Validated: RRSIG-Owner hrmb94bfq1nhglve1297595jooujpth0.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.09.2021, 06:49:27 +, Signature-Inception: 14.09.2021, 03:06:03 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed query name "snr4p7vqet4l723h388kh8s47dvt8t6j" equal the hashed NSEC3-owner "snr4p7vqet4l723h388kh8s47dvt8t6j" and the hashed NextOwner "sntthgnpa2s87876ql4prtp267j34892". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



Status: Good. NoData-Proof required and found.

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



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "1v9cc75ee73i1908hfa9ejhakmnf7r6o" between the hashed NSEC3-owner "1v54q7ms8ujjlelmc3j2n37b8g3j91t2" and the hashed NextOwner "1vbsmjkl9qg6nm9tks4ah2ru5vvsbqvj". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: No Bitmap? Validated: RRSIG-Owner 1v54q7ms8ujjlelmc3j2n37b8g3j91t2.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 05:27:13 +, Signature-Inception: 10.09.2021, 11:12:02 +, KeyTag 65160, Signer-Name: com.mm



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "snr4p7vqet4l723h388kh8s47dvt8t6j" as Owner. That's the Hash of "com.mm" with the NextHashedOwnerName "sntthgnpa2s87876ql4prtp267j34892". So that domain name is the Closest Encloser of "www.com.mm". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner snr4p7vqet4l723h388kh8s47dvt8t6j.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 17.09.2021, 02:49:21 +, Signature-Inception: 10.09.2021, 07:27:01 +, KeyTag 65160, Signer-Name: com.mm



The ClosestEncloser says, that "*.com.mm" with the Hash "hrn8ah1gusncit04l31nu2c97i71a3h0" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "hrmb94bfq1nhglve1297595jooujpth0" and the Next Owner "hrno1q6at1b73estvj0mi96sqnjvdpm2", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: No Bitmap? Validated: RRSIG-Owner hrmb94bfq1nhglve1297595jooujpth0.com.mm., Algorithm: 8, 3 Labels, original TTL: 3600 sec, Signature-expiration: 21.09.2021, 06:49:27 +, Signature-Inception: 14.09.2021, 03:06:03 +, KeyTag 65160, Signer-Name: com.mm


3. Name Servers

DomainNameserverNS-IP
www.com.mm
  a.nic.net.mm

com.mm
  a.nic.net.mm / dns1.frpar1
37.209.192.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


  b.nic.net.mm / dns3.defra1
37.209.194.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


  c.nic.net.mm / dns4.defra1
37.209.196.4
Sterling/Virginia/United States (US) - NeuStar, Inc.


  d.nic.net.mm / dns1.frpar1
37.209.198.4
Sterling/Virginia/United States (US) - NeuStar, Inc.

mm
  a.nic.net.mm / dns2.frpar1


  b.nic.net.mm / dns2.defra1


  c.nic.net.mm / dns2.defra1


  d.nic.net.mm / dns3.frpar1


4. SOA-Entries


Domain:mm
Zone-Name:mm
Primary:a.nic.net.mm
Mail:admin.registry.gov.mm
Serial:1631632501
Refresh:1800
Retry:900
Expire:604800
TTL:3600
num Entries:4


Domain:com.mm
Zone-Name:com.mm
Primary:a.nic.net.mm
Mail:admin.registry.gov.mm
Serial:1631635142
Refresh:1800
Retry:900
Expire:604800
TTL:3600
num Entries:4


Domain:www.com.mm
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
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 "com.mm" is public suffix, public suffix is ".*.mm", top-level-domain is ".mm", top-level-domain-type is "country-code", Country is Myanmar, tld-manager is "Ministry of Transport and Communications", num .mm-domains preloaded: 0 (complete: 168171)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem

2. DNS- and NameServer - Checks

AGood: Only one SOA.Primary Name Server found.: a.nic.net.mm.
AGood: SOA.Primary Name Server included in the delegation set.: a.nic.net.mm.
AGood: Consistency 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. Ordered list of name servers: a.nic.net.mm, b.nic.net.mm, c.nic.net.mm, d.nic.net.mm
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 4 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: *.mm
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: net.mm
Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
AGood: Name Server IPv4-addresses from different subnet found:
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: a.nic.net.mm: 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.
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

ADuration: 30810 milliseconds, 30.810 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

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


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
com.mm
0

no CAA entry found
1
0
mm
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
_acme-challenge.com.mm

Name Error - The domain name does not exist
1
0
_acme-challenge.com.mm.com.mm

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=83f2305f-f3e5-4664-94a6-bffb4d36c366


Last Result: https://check-your-website.server-daten.de/?q=com.mm - 2021-09-14 18:14:43


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

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