View on GitHub

DNSViz: A DNS visualization tool

loc.gov

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

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 36558)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • loc.gov/DS (alg 8, id 41152)
  • loc.gov/DS (alg 8, id 6991)
Non_existent (2)
  • loc.gov/DNSKEY (alg 8, id 41152)
  • loc.gov/DNSKEY (alg 8, id 6991)

Delegation statusDelegation status

Bogus (1)
  • gov to loc.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (5)
  • gov to loc.gov: 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.
  • loc.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.147.32.166, 140.147.239.150)
  • loc.gov zone: There was an error resolving the following NS name(s) to address(es): ns21.loc.gov, ns23.loc.gov
  • loc.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.147.32.166, 140.147.239.150, UDP_-_NOEDNS_)
  • loc.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.147.32.166, 140.147.239.150, UDP_-_NOEDNS_)
Warnings (12)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • loc.gov/DS (alg 8, id 41152): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • loc.gov/DS (alg 8, id 41152): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • loc.gov/DS (alg 8, id 41152): 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.
  • loc.gov/DS (alg 8, id 41152): 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.
  • loc.gov/DS (alg 8, id 6991): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • loc.gov/DS (alg 8, id 6991): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • loc.gov/DS (alg 8, id 6991): 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.
  • loc.gov/DS (alg 8, id 6991): 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.

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