View on GitHub

DNSViz: A DNS visualization tool

ucdavis.edu

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • edu/DNSKEY (alg 8, id 24314)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DS (alg 8, id 28065)
  • ucdavis.edu/DNSKEY (alg 8, id 17655)
  • ucdavis.edu/DNSKEY (alg 8, id 31642)
  • ucdavis.edu/DS (alg 8, id 31642)
  • ucdavis.edu/DS (alg 8, id 31642)
  • ucdavis.edu/DS (alg 8, id 39682)
  • ucdavis.edu/DS (alg 8, id 42136)
Non_existent (2)
  • ucdavis.edu/DNSKEY (alg 8, id 39682)
  • ucdavis.edu/DNSKEY (alg 8, id 42136)

Delegation statusDelegation status

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

NoticesNotices

Warnings (11)
  • ucdavis.edu/A: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f810:ce0:10::2, UDP_-_EDNS0_4096_D_KN)
  • ucdavis.edu/DS (alg 8, id 31642): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucdavis.edu/DS (alg 8, id 31642): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucdavis.edu/DS (alg 8, id 31642): 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.
  • ucdavis.edu/DS (alg 8, id 31642): 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.
  • ucdavis.edu/DS (alg 8, id 42136): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucdavis.edu/DS (alg 8, id 42136): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ucdavis.edu/DS (alg 8, id 42136): 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.
  • ucdavis.edu/DS (alg 8, id 42136): 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.
  • ucdavis.edu/MX: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f810:ce0:10::2, UDP_-_EDNS0_4096_D_KN)
  • ucdavis.edu/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f810:ce0:10::2, UDP_-_EDNS0_4096_D_KN)

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