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 (18)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 61809)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DNSKEY (alg 13, id 35999)
  • edu/DS (alg 13, id 35663)
  • usfca.edu/DNSKEY (alg 5, id 35613)
  • usfca.edu/DNSKEY (alg 5, id 40521)
  • usfca.edu/DNSKEY (alg 5, id 43212)
  • usfca.edu/DNSKEY (alg 5, id 46738)
  • usfca.edu/DNSKEY (alg 5, id 49837)
  • usfca.edu/DNSKEY (alg 8, id 11926)
  • usfca.edu/DNSKEY (alg 8, id 19215)
  • usfca.edu/DNSKEY (alg 8, id 2095)
  • usfca.edu/DNSKEY (alg 8, id 25299)
  • usfca.edu/DNSKEY (alg 8, id 64953)
  • usfca.edu/DS (alg 8, id 11926)
  • usfca.edu/DS (alg 8, id 2095)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • usfca.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (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)
  • usfca.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (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/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (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, TCP_-_EDNS0_4096_D_N)
  • usfca.edu/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (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, TCP_-_EDNS0_4096_D_KN)
  • c2l9t.vaw0y.usfca.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • usfca.edu/DNSKEY 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 (42)
  • RRSIG usfca.edu/A alg 5, id 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 43212: 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 46738: 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 46738: 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 46738: 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 46738: 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 46738: 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 46738: 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 46738: 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 46738: 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 46738: 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 46738: 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 49837: 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 49837: 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 49837: 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 49837: 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 49837: 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 49837: 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 49837: 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 49837: 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 49837: 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 49837: 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 43212: 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 43212: 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 43212: 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 43212: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • 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.
  • 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.
  • c2l9t.vaw0y.usfca.edu/A 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