View on GitHub

DNSViz: A DNS visualization tool

ornl.gov

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

RRset statusRRset status

Secure (7)
  • ornl.gov/A
  • ornl.gov/MX
  • ornl.gov/NS
  • ornl.gov/SOA
  • ornl.gov/SOA
  • ornl.gov/SOA
  • ornl.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • ornl.gov/DNSKEY (alg 7, id 26234)
  • ornl.gov/DNSKEY (alg 7, id 41165)
  • ornl.gov/DNSKEY (alg 7, id 5660)
  • ornl.gov/DS (alg 7, id 5660)
  • ornl.gov/DS (alg 7, id 5660)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • ornl.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:0:2b30:304::32, 2620:0:2b30:304::96)
  • ornl.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:2b30:304::32, 2620:0:2b30:304::96, UDP_-_NOEDNS_)
  • ornl.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:2b30:304::32, 2620:0:2b30:304::96, UDP_-_NOEDNS_)
  • ornl.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • ornl.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • tf61ev94jg.ornl.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (26)
  • RRSIG ornl.gov/A alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/DNSKEY alg 7, id 5660: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/DNSKEY alg 7, id 5660: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/DNSKEY alg 7, id 5660: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/MX alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/NS alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/SOA alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/SOA alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/SOA alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ornl.gov/TXT alg 7, id 41165: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to ornl.gov: Authoritative AAAA records exist for ns0-alt.ornl.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to ornl.gov: Authoritative AAAA records exist for ns0.ornl.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to ornl.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-aoa.es.net, ns1.es.net, ns-lvk.es.net See RFC 1034, Sec. 4.2.2.
  • gov to ornl.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: ns0-alt.ornl.gov See RFC 1034, Sec. 4.2.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): 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.
  • ornl.gov/DS (alg 7, id 5660): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ornl.gov/DS (alg 7, id 5660): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ornl.gov/DS (alg 7, id 5660): 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.
  • ornl.gov/DS (alg 7, id 5660): 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.
  • ornl.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ornl.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ornl.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tf61ev94jg.ornl.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