View on GitHub

DNSViz: A DNS visualization tool

sandia.gov

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

RRset statusRRset status

Secure (8)
  • sandia.gov/A
  • sandia.gov/AAAA
  • sandia.gov/MX
  • sandia.gov/NS
  • sandia.gov/NSEC3PARAM
  • sandia.gov/SOA
  • sandia.gov/SOA
  • sandia.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • ./DNSKEY (alg 8, id 5613)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DS (alg 8, id 64280)
  • sandia.gov/DNSKEY (alg 7, id 20739)
  • sandia.gov/DNSKEY (alg 7, id 36033)
  • sandia.gov/DNSKEY (alg 7, id 42518)
  • sandia.gov/DS (alg 7, id 20739)
  • sandia.gov/DS (alg 7, id 20739)
  • sandia.gov/DS (alg 7, id 36033)
  • sandia.gov/DS (alg 7, id 36033)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to sandia.gov

NoticesNotices

Errors (2)
  • sandia.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 0eqxgz8y7c.sandia.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (27)
  • RRSIG sandia.gov/A alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/AAAA alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/DNSKEY alg 7, id 20739: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/DNSKEY alg 7, id 20739: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/DNSKEY alg 7, id 20739: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/DNSKEY alg 7, id 36033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/DNSKEY alg 7, id 36033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/DNSKEY alg 7, id 36033: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/MX alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/NS alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/NSEC3PARAM alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/SOA alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/SOA alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sandia.gov/TXT alg 7, id 42518: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to sandia.gov: The glue address(es) for ns2.ca.sandia.gov (198.206.219.66) differed from its authoritative address(es) (198.206.219.122). See RFC 1034, Sec. 4.2.2.
  • gov to sandia.gov: The glue address(es) for ns2.ca.sandia.gov (2620:106:6000:40::66) differed from its authoritative address(es) (2620:106:6000:41:f0::122). See RFC 1034, Sec. 4.2.2.
  • sandia.gov/DS (alg 7, id 20739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandia.gov/DS (alg 7, id 20739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandia.gov/DS (alg 7, id 20739): 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.
  • sandia.gov/DS (alg 7, id 20739): 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.
  • sandia.gov/DS (alg 7, id 36033): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandia.gov/DS (alg 7, id 36033): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sandia.gov/DS (alg 7, id 36033): 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.
  • sandia.gov/DS (alg 7, id 36033): 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.
  • sandia.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 0eqxgz8y7c.sandia.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sandia.gov/DNSKEY 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