View on GitHub

DNSViz: A DNS visualization tool

usfca.edu

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

RRset statusRRset status

Secure (6)
  • usfca.edu/A
  • usfca.edu/AAAA
  • usfca.edu/MX
  • usfca.edu/NS
  • usfca.edu/SOA
  • usfca.edu/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • edu/DNSKEY (alg 13, id 30299)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DS (alg 13, id 35663)
  • usfca.edu/DNSKEY (alg 5, id 12855)
  • usfca.edu/DNSKEY (alg 5, id 26293)
  • usfca.edu/DNSKEY (alg 5, id 52320)
  • usfca.edu/DNSKEY (alg 8, id 19735)
  • usfca.edu/DNSKEY (alg 8, id 396)
  • usfca.edu/DNSKEY (alg 8, id 49668)
  • usfca.edu/DS (alg 8, id 19735)

Delegation statusDelegation status

Secure (2)
  • . to edu
  • edu to usfca.edu

NoticesNotices

Errors (2)
  • usfca.edu/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (28)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • RRSIG usfca.edu/A alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/AAAA alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 26293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 26293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 26293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 26293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 26293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 26293: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/DNSKEY alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/MX alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/NS alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/SOA alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG usfca.edu/TXT alg 5, id 52320: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • edu/DS (alg 13, id 35663): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • edu/DS (alg 13, id 35663): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • usfca.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ckwg2.kvm5a.usfca.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/NSEC3PARAM 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