mpt.net.mm
Updated:
2025-04-01 04:21:32 UTC (6 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- mpt.net.mm/MX
- mpt.net.mm/NS
- mpt.net.mm/SOA
- mpt.net.mm/TXT
Secure (1)
- net.mm/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- mpt.net.mm/DNSKEY (alg 8, id 10164)
- mpt.net.mm/DNSKEY (alg 8, id 64525)
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26470)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 53148)
- NSEC3 proving non-existence of mpt.net.mm/DS
- mm/DNSKEY (alg 8, id 18589)
- mm/DNSKEY (alg 8, id 32298)
- mm/DS (alg 8, id 18589)
- net.mm/DNSKEY (alg 8, id 45414)
- net.mm/DNSKEY (alg 8, id 56149)
- net.mm/DS (alg 8, id 56149)
Delegation status
Insecure (1)
- net.mm to mpt.net.mm
Secure (2)
- . to mm
- mm to net.mm
Notices
Errors (23)
- NSEC3 proving non-existence of mpt.net.mm/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of mpt.net.mm/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- RRSIG mm/DNSKEY alg 8, id 18589: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 13 hours, 31 minutes after it expires at 2025-04-01 12:46:11+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG mm/DNSKEY alg 8, id 18589: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 13 hours, 31 minutes after it expires at 2025-04-01 12:46:11+00:00. See RFC 4035, Sec. 5.3.3.
- mm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.103.173.9)
- mpt.net.mm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (203.81.92.8)
- mpt.net.mm/DNSKEY (alg 8, id 10164): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (203.81.64.22, 203.81.64.23, UDP_-_EDNS0_4096_D_KN)
- mpt.net.mm/DNSKEY (alg 8, id 64525): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (203.81.64.22, 203.81.64.23, UDP_-_EDNS0_4096_D_KN)
- mpt.net.mm/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (203.81.64.22, 203.81.64.23, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- mpt.net.mm/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (203.81.64.22, 203.81.64.23, UDP_-_EDNS0_4096_D_KN)
- mpt.net.mm/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (203.81.92.8, UDP_-_NOEDNS_)
- mpt.net.mm/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (203.81.64.22, 203.81.64.23, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- mpt.net.mm/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (203.81.64.22, 203.81.64.23, UDP_-_EDNS0_4096_D_KN)
- net.mm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (103.103.173.9)
- mpt.net.mm/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- bp9tw.u6xd0.mpt.net.mm/A has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/A has errors; select the "Denial of existence" DNSSEC option to see them.
- mpt.net.mm/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of mpt.net.mm/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of mpt.net.mm/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- mpt.net.mm/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
