View on GitHub

DNSViz: A DNS visualization tool

temple.edu

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 43304)
  • edu/DS (alg 8, id 28065)
  • temple.edu/DNSKEY (alg 8, id 16818)
  • temple.edu/DNSKEY (alg 8, id 8746)
  • temple.edu/DS (alg 8, id 8746)

Delegation statusDelegation status

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

NoticesNotices

Errors (1)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
Warnings (2)
  • ./DNSKEY (alg 8, id 20326): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 47671): 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. (2001:500:12::d0d, 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