View on GitHub

DNSViz: A DNS visualization tool

unh.edu

Updated: 2023-06-02 11:55:14 UTC (493 days ago) Update now
« 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)
  • unh.edu/A
  • unh.edu/MX
  • unh.edu/NS
  • unh.edu/SOA
  • unh.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 60955)
  • NSEC3 proving non-existence of unh.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 30503)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • unh.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30)
  • unh.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30)
  • unh.edu/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, UDP_-_EDNS0_4096_D_KN)
  • unh.edu/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • unh.edu/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • unh.edu/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, UDP_-_EDNS0_4096_D_KN)
  • unh.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, TCP_-_EDNS0_4096_D_N)
  • unh.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • unh.edu/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (132.177.102.30, 2606:4100:3fff:102::102:30, UDP_-_EDNS0_4096_D_KN)
  • unh.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • unh.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • unh.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • unh.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 95zbqc41j7.unh.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • edu to unh.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): psu-ns2.plymouth.edu, psu-ns1.plymouth.edu 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