datamtn.com
Updated:
2020-03-13 19:02:45 UTC (1596 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- datamtn.com/A
- datamtn.com/MX
- datamtn.com/NS
- datamtn.com/SOA
- datamtn.com/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 56311)
- com/DS (alg 8, id 30909)
- datamtn.com/DNSKEY (alg 8, id 15362)
- datamtn.com/DNSKEY (alg 8, id 20216)
- datamtn.com/DNSKEY (alg 8, id 29928)
- datamtn.com/DNSKEY (alg 8, id 49325)
- datamtn.com/DNSKEY (alg 8, id 5238)
- datamtn.com/DS (alg 8, id 5238)
- datamtn.com/DS (alg 8, id 5238)
Delegation status
Secure (2)
- . to com
- com to datamtn.com
Notices
Errors (8)
- datamtn.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238)
- datamtn.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238, UDP_-_NOEDNS_)
- datamtn.com/DS (alg 8, id 5238): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- datamtn.com/DS (alg 8, id 5238): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- datamtn.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:49f0:d064:6:1000::238, UDP_-_NOEDNS_)
- datamtn.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 7opmgjw5c4.datamtn.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- datamtn.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- com to datamtn.com: Authoritative AAAA records exist for dnssec10.datamtn.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to datamtn.com: Authoritative AAAA records exist for dnssec11.datamtn.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to datamtn.com: Authoritative AAAA records exist for dnssec12.datamtn.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to datamtn.com: Authoritative AAAA records exist for dnssec14.datamtn.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to datamtn.com: Authoritative AAAA records exist for dnssec7.datamtn.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to datamtn.com: Authoritative AAAA records exist for dnssec9.datamtn.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- datamtn.com/DS (alg 8, id 5238): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- datamtn.com/DS (alg 8, id 5238): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- datamtn.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 7opmgjw5c4.datamtn.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- datamtn.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
