View on GitHub

DNSViz: A DNS visualization tool

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

Delegation statusDelegation status

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

NoticesNotices

Errors (13)
  • seattleu.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1)
  • seattleu.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1)
  • seattleu.edu/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, UDP_-_EDNS0_4096_D_K)
  • seattleu.edu/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • seattleu.edu/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • seattleu.edu/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, UDP_-_EDNS0_4096_D_K)
  • seattleu.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, TCP_-_EDNS0_4096_D)
  • seattleu.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • seattleu.edu/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (205.251.192.191, 2600:9000:5300:bf00::1, UDP_-_EDNS0_4096_D_K)
  • seattleu.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • seattleu.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • seattleu.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • r2x9yag3jh.seattleu.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • edu to seattleu.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: ns-191.awsdns-23.com See RFC 1034, Sec. 4.2.2.
  • 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
  • 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)

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