View on GitHub

DNSViz: A DNS visualization tool

tulane.edu

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

RRset statusRRset status

Insecure (5)
  • tulane.edu/A
  • tulane.edu/MX
  • tulane.edu/NS
  • tulane.edu/SOA
  • tulane.edu/TXT
Secure (1)
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of tulane.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 47450)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

Insecure (1)
  • edu to tulane.edu
Secure (1)
  • . to edu

NoticesNotices

Errors (3)
  • tulane.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:10a:3000:3016::37, 2620:10a:30f0:100::2)
  • tulane.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:10a:3000:3016::37, 2620:10a:30f0:100::2, UDP_-_NOEDNS_)
  • tulane.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:10a:3000:3016::37, 2620:10a:30f0:100::2, UDP_-_NOEDNS_)
Warnings (1)
  • edu to tulane.edu: AAAA glue records exist for ns2.tulane.edu, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.

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