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 20326)
  • ./DNSKEY (alg 8, id 26838)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 37868)
  • edu/DS (alg 8, id 28065)
  • usfca.edu/DNSKEY (alg 5, id 13857)
  • usfca.edu/DNSKEY (alg 5, id 27901)
  • usfca.edu/DNSKEY (alg 5, id 3901)
  • usfca.edu/DNSKEY (alg 5, id 62280)
  • usfca.edu/DNSKEY (alg 8, id 33022)
  • usfca.edu/DS (alg 5, id 27901)
  • usfca.edu/DS (alg 5, id 3901)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • usfca.edu/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.62.180.53, 194.62.181.53, 204.16.254.53, 204.16.255.53, 2620:0:2e64::53, 2a07:dc00:180::53, 2a07:dc00:1810::53, 2a07:dc00:2550::53, UDP_-_EDNS0_4096_D_KN)
  • usfca.edu/AAAA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.62.180.53, 194.62.181.53, 204.16.254.53, 204.16.255.53, 2620:0:2e64::53, 2a07:dc00:180::53, 2a07:dc00:1810::53, 2a07:dc00:2550::53, UDP_-_EDNS0_4096_D_KN)
  • usfca.edu/MX: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.62.180.53, 194.62.181.53, 204.16.254.53, 204.16.255.53, 2620:0:2e64::53, 2a07:dc00:180::53, 2a07:dc00:1810::53, 2a07:dc00:2550::53, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • usfca.edu/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.62.180.53, 194.62.181.53, 204.16.254.53, 204.16.255.53, 2620:0:2e64::53, 2a07:dc00:180::53, 2a07:dc00:1810::53, 2a07:dc00:2550::53, UDP_-_EDNS0_4096_D_KN)
  • usfca.edu/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (194.62.180.53, 194.62.181.53, 204.16.254.53, 204.16.255.53, 2620:0:2e64::53, 2a07:dc00:180::53, 2a07:dc00:1810::53, 2a07:dc00:2550::53, UDP_-_EDNS0_4096_D_KN)
  • usfca.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • jykpz468r7.usfca.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • RRSIG usfca.edu/A alg 5, id 13857: 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 13857: 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 13857: 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 13857: 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 13857: 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 13857: 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 13857: 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 27901: 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 27901: 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 27901: 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 27901: 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 27901: 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 3901: 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 3901: 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 3901: 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 3901: 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 3901: 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 13857: 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 13857: 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 13857: 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 13857: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • usfca.edu/DS (alg 5, id 27901): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usfca.edu/DS (alg 5, id 27901): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usfca.edu/DS (alg 5, id 3901): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usfca.edu/DS (alg 5, id 3901): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usfca.edu/DNSKEY 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.
  • jykpz468r7.usfca.edu/A 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.

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