View on GitHub

DNSViz: A DNS visualization tool

inl.gov

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

RRset statusRRset status

Secure (5)
  • inl.gov/A
  • inl.gov/MX
  • inl.gov/NS
  • inl.gov/SOA
  • inl.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • inl.gov/DNSKEY (alg 5, id 43936)
  • inl.gov/DNSKEY (alg 5, id 5753)
  • inl.gov/DNSKEY (alg 5, id 8669)
  • inl.gov/DS (alg 5, id 5753)
  • inl.gov/DS (alg 5, id 5753)
  • inl.gov/DS (alg 5, id 8669)
  • inl.gov/DS (alg 5, id 8669)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • inl.gov zone: The following NS name(s) did not resolve to address(es): ns.inl.gov, ns2.inl.gov
  • inl.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:0:2b88:9700::40, 2620:0:2b88:b301::10)
  • inl.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:2b88:9700::40, 2620:0:2b88:b301::10, UDP_-_NOEDNS_)
  • inl.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:2b88:9700::40, 2620:0:2b88:b301::10, UDP_-_NOEDNS_)
Warnings (28)
  • RRSIG inl.gov/A alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 5753: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 5753: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 5753: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 8669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 8669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/DNSKEY alg 5, id 8669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/MX alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/NS alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/SOA alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG inl.gov/TXT alg 5, id 43936: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • gov to inl.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns.inl.gov, ns2.inl.gov See RFC 1034, Sec. 4.2.2.
  • inl.gov/DS (alg 5, id 5753): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • inl.gov/DS (alg 5, id 5753): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • inl.gov/DS (alg 5, id 5753): 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.
  • inl.gov/DS (alg 5, id 5753): 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.
  • inl.gov/DS (alg 5, id 8669): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • inl.gov/DS (alg 5, id 8669): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • inl.gov/DS (alg 5, id 8669): 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.
  • inl.gov/DS (alg 5, id 8669): 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.
  • inl.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • inl.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • inl.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • inl.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2z0hxpg671.inl.gov/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