View on GitHub

DNSViz: A DNS visualization tool

ironmountain.com

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (3)
  • ironmountain.com/DNSKEY (alg 5, id 12127)
  • ironmountain.com/DNSKEY (alg 5, id 43131)
  • ironmountain.com/DNSKEY (alg 5, id 8403)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 956)
  • com/DS (alg 13, id 19718)
  • ironmountain.com/DS (alg 5, id 12349)
Non_existent (1)
  • ironmountain.com/DNSKEY (alg 5, id 12349)

Delegation statusDelegation status

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

NoticesNotices

Errors (2)
  • com to ironmountain.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. (216.229.145.31, 216.229.153.20, TCP_-_EDNS0_4096_D_KN)
  • com to ironmountain.com: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.229.145.31, 216.229.153.20, TCP_-_EDNS0_4096_D_KN)
Warnings (28)
  • RRSIG ironmountain.com/A alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/A alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 12127: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 12127: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 12127: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/DNSKEY alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/MX alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/MX alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/NS alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/NS alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/SOA alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/SOA alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/TXT alg 5, id 43131: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ironmountain.com/TXT alg 5, id 8403: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • ironmountain.com/DS (alg 5, id 12349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ironmountain.com/DS (alg 5, id 12349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ironmountain.com/DS (alg 5, id 12349): 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.
  • ironmountain.com/DS (alg 5, id 12349): 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.
  • ironmountain.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ironmountain.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ironmountain.com/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ironmountain.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bd0mq.na8wr.ironmountain.com/A 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