View on GitHub

DNSViz: A DNS visualization tool

uncg.edu

Updated: 2023-01-26 18:20:00 UTC (664 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)
  • uncg.edu/A
  • uncg.edu/MX
  • uncg.edu/NS
  • uncg.edu/SOA
  • uncg.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 951)
  • NSEC3 proving non-existence of uncg.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 34085)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • uncg.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::)
  • uncg.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::)
  • uncg.edu/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, UDP_-_EDNS0_4096_D_KN)
  • uncg.edu/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • uncg.edu/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • uncg.edu/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, UDP_-_EDNS0_4096_D_KN)
  • uncg.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, TCP_-_EDNS0_4096_D_N)
  • uncg.edu/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • uncg.edu/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (192.101.21.33, 2600:2700:f00:11::, UDP_-_EDNS0_4096_D_KN)
  • uncg.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • mf3hneusvk.uncg.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • uncg.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • uncg.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • uncg.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • edu to uncg.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): ns-resolver-02.mcnc.org See RFC 1034, Sec. 4.2.2.
  • edu to uncg.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: ncnoc.ncren.net 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