View on GitHub

DNSViz: A DNS visualization tool

miami.edu

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of miami.edu/DS
  • edu/DNSKEY (alg 13, id 30299)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DS (alg 13, id 35663)

Delegation statusDelegation status

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

NoticesNotices

Errors (16)
  • miami.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (129.171.64.3)
  • miami.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (129.171.64.3)
  • miami.edu/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, UDP_-_EDNS0_4096_D_KN)
  • miami.edu/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • miami.edu/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • miami.edu/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, UDP_-_EDNS0_4096_D_KN)
  • miami.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, TCP_-_EDNS0_4096_D_N)
  • miami.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • miami.edu/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.171.64.3, UDP_-_EDNS0_4096_D_KN)
  • mb1re.wrsx5.miami.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • miami.edu/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • miami.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • miami.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • miami.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • miami.edu/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • miami.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • edu to miami.edu: The glue address(es) for e1.miami.edu (64.56.84.250) differed from its authoritative address(es) (64.56.84.250, 129.171.64.3). 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