View on GitHub

DNSViz: A DNS visualization tool

datamtn.com

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (5)
  • datamtn.com/A
  • datamtn.com/MX
  • datamtn.com/NS
  • datamtn.com/SOA
  • datamtn.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (5)
  • 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)
Secure (7)
  • ./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/DS (alg 8, id 5238)
  • datamtn.com/DS (alg 8, id 5238)

Delegation statusDelegation status

Bogus (1)
  • com to datamtn.com
Secure (1)
  • . to com

NoticesNotices

Errors (23)
  • RRSIG datamtn.com/A alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 5238: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 5238: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 5238: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 5238: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/DNSKEY alg 8, id 5238: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/MX alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/NS alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/SOA alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • RRSIG datamtn.com/TXT alg 8, id 49325: The Signature Inception field of the RRSIG RR (2020-03-13 22:16:59+00:00) is 3 hours, 34 minutes in the future. See RFC 4035, Sec. 5.3.1.
  • com to datamtn.com: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (64.62.200.147, 65.49.37.203, 108.166.170.104, 108.166.170.105, 192.198.87.242, 198.255.114.190, 2001:470:1:7a::147, 2001:470:1:7a:2000::203, 2607:5600:143:0:1000::101, 2607:f348:100c:1::105, 2607:f348:100c:1::171, UDP_-_EDNS0_4096_D_K)
  • 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/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_)
  • zvbemp5dx6.datamtn.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • datamtn.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • datamtn.com/CNAME 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 (13)
  • 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): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • datamtn.com/DS (alg 8, id 5238): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.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.
  • zvbemp5dx6.datamtn.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • datamtn.com/CNAME 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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph