View on GitHub

DNSViz: A DNS visualization tool

berkeley.edu

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

RRset statusRRset status

Bogus (4)
  • berkeley.edu/A
  • berkeley.edu/MX
  • berkeley.edu/NS
  • berkeley.edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • berkeley.edu/DS (alg 10, id 38028)
  • berkeley.edu/DS (alg 10, id 59277)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DNSKEY (alg 13, id 7003)
  • edu/DS (alg 13, id 35663)
Non_existent (4)
  • berkeley.edu/DNSKEY (alg 10, id 21896)
  • berkeley.edu/DNSKEY (alg 10, id 25055)
  • berkeley.edu/DNSKEY (alg 10, id 38028)
  • berkeley.edu/DNSKEY (alg 10, id 59277)

Delegation statusDelegation status

Bogus (1)
  • edu to berkeley.edu
Secure (1)
  • . to edu

NoticesNotices

Errors (10)
  • berkeley.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (128.32.136.3, 128.32.136.14, 192.107.102.142, 2607:f140:a000:d::abc, 2607:f140:ffff:fffe::3)
  • berkeley.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f140:ffff:fffe::e)
  • berkeley.edu/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (2607:f140:ffff:fffe::e, UDP_-_EDNS0_4096_D_KN)
  • berkeley.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (128.32.136.3, 128.32.136.14, 192.107.102.142, 2607:f140:a000:d::abc, 2607:f140:ffff:fffe::3, UDP_-_EDNS0_4096_D_KN)
  • berkeley.edu/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (2607:f140:ffff:fffe::e, UDP_-_EDNS0_4096_D_KN)
  • berkeley.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (128.32.136.3, 128.32.136.14, 192.107.102.142, 2607:f140:a000:d::abc, 2607:f140:ffff:fffe::3, TCP_-_EDNS0_4096_D_N)
  • berkeley.edu/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (128.32.136.3, 128.32.136.14, 192.107.102.142, 2607:f140:a000:d::abc, 2607:f140:ffff:fffe::3, TCP_-_EDNS0_4096_D_KN)
  • edu to berkeley.edu: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
  • ht6uvjq7z3.berkeley.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • berkeley.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • RRSIG berkeley.edu/A alg 10, id 21896: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/A alg 10, id 25055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/MX alg 10, id 21896: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/MX alg 10, id 25055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/NS alg 10, id 21896: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/NS alg 10, id 25055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/SOA alg 10, id 21896: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG berkeley.edu/SOA alg 10, id 25055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • edu to berkeley.edu: Authoritative AAAA records exist for adns1.berkeley.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • edu to berkeley.edu: Authoritative AAAA records exist for adns2.berkeley.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • berkeley.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • berkeley.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • berkeley.edu/AAAA 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