View on GitHub

DNSViz: A DNS visualization tool

usm.edu

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

RRset statusRRset status

Insecure (4)
  • usm.edu/A
  • usm.edu/NS
  • usm.edu/SOA
  • usm.edu/TXT
Secure (2)
  • edu/SOA
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of usm.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 34085)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • usm.edu zone: The following NS name(s) did not resolve to address(es): darbanazure, dns_azure_internal
  • usm.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (131.95.186.31)
  • usm.edu zone: There was an error resolving the following NS name(s) to address(es): darban3.cc.usm.edu, darban4.cc.usm.edu, ns2.usm.edu
  • usm.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.95.186.31, UDP_-_NOEDNS_)
  • usm.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (23.98.146.63, UDP_-_EDNS0_512_D_KN)
  • usm.edu/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (23.98.146.63, UDP_-_EDNS0_512_D_KN)
  • usm.edu/MX: No response was received from the server over UDP (tried 9 times). See RFC 1035, Sec. 4.2. (23.98.146.63, UDP_-_EDNS0_4096_D_N)
  • usm.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.95.186.31, UDP_-_NOEDNS_)
  • usm.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • edu to usm.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): darban3.cc.usm.edu, darban4.cc.usm.edu, darbanazure, dns_azure_internal See RFC 1034, Sec. 4.2.2.
  • edu to usm.edu: The following NS name(s) were found in the delegation NS RRset (i.e., in the edu zone), but not in the authoritative NS RRset: darban5.usm.edu, ns2.usm.edu See RFC 1034, Sec. 4.2.2.
  • usm.edu/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (23.98.146.63, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • usm.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. (23.98.146.63, UDP_-_EDNS0_4096_D_KN)
  • usm.edu/TXT: 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. (23.98.146.63, UDP_-_EDNS0_4096_D_KN)
  • usm.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usm.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