View on GitHub

DNSViz: A DNS visualization tool

umes.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 (8)
  • umes.edu/A
  • umes.edu/MX
  • umes.edu/NS
  • umes.edu/NS
  • umes.edu/SOA
  • umes.edu/SOA
  • umes.edu/TXT
  • umes.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 20826)
  • NSEC3 proving non-existence of umes.edu/DS
  • edu/DNSKEY (alg 8, id 18290)
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • umes.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (131.118.96.7, 131.118.96.15)
  • umes.edu/DNSKEY: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_512_D_KN)
  • umes.edu/MX: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_512_D_KN)
  • umes.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (131.118.96.7, 131.118.96.15, TCP_-_EDNS0_4096_D_N)
  • umes.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • edu/DS (alg 8, id 28065): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • edu/DS (alg 8, id 28065): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • umes.edu/A: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_4096_D_KN)
  • umes.edu/MX: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_4096_D_KN)
  • umes.edu/NS: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_4096_D_KN)
  • umes.edu/SOA: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • umes.edu/TXT: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (131.118.96.7, 131.118.96.15, UDP_-_EDNS0_4096_D_KN)
  • umes.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • umes.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • umes.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ugx38s9vk0.umes.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • umes.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