View on GitHub

DNSViz: A DNS visualization tool

umich.edu

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

RRset statusRRset status

Insecure (7)
  • umich.edu/A
  • umich.edu/AAAA
  • umich.edu/MX
  • umich.edu/NS
  • umich.edu/SOA
  • umich.edu/SOA
  • umich.edu/TXT
Secure (2)
  • edu/SOA
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • umich.edu/DNSKEY (alg 13, id 16501)
  • umich.edu/DNSKEY (alg 13, id 37203)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of umich.edu/DS
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DNSKEY (alg 13, id 7003)
  • edu/DS (alg 13, id 35663)

Delegation statusDelegation status

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

NoticesNotices

Errors (21)
  • umich.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156)
  • umich.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3156)
  • umich.edu/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2400:cb00:2049:1::a29f:3005, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.12.80.214, 192.12.80.222, UDP_-_NOEDNS_)
  • umich.edu/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.12.80.222, UDP_-_EDNS0_512_D_KN)
  • umich.edu/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • umich.edu/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • umich.edu/NS: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (192.12.80.222, UDP_-_EDNS0_4096_)
  • umich.edu/NS: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (192.12.80.222, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (192.12.80.222, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2400:cb00:2049:1::a29f:3005, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, TCP_-_EDNS0_4096_D_N)
  • umich.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • umich.edu/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.48.5, 162.159.49.86, 2400:cb00:2049:1::a29f:3005, 2400:cb00:2049:1::a29f:3156, UDP_-_EDNS0_4096_D_KN)
  • umich.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • umich.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • umich.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • 1juvr4s7li.umich.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • edu to umich.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): umich-edu.dns.umich.com, umich-edu.dns.umich.org, umich-edu.dns.umich.net See RFC 1034, Sec. 4.2.2.
  • edu to umich.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: cffw1.dns.umich.com, dns1.itd.umich.edu, dns2.itd.umich.edu, cffw2.dns.umich.net See RFC 1034, Sec. 4.2.2.
  • umich.edu/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.12.80.214, UDP_-_EDNS0_4096_D_KN)
  • umich.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