View on GitHub

DNSViz: A DNS visualization tool

com.ng

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

RRset statusRRset status

Insecure (7)
  • com.ng/NS
  • com.ng/SOA
  • com.ng/SOA
  • com.ng/TXT
  • com.ng/TXT
  • ng/SOA
  • ng/SOA
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC proving non-existence of ng/DS

Delegation statusDelegation status

Insecure (2)
  • . to ng
  • ng to com.ng

NoticesNotices

Errors (2)
  • ng to com.ng: An SOA RR with owner name (com.ng) not matching the zone name (ng) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (194.0.1.29, 2001:678:4::1d, UDP_-_EDNS0_4096_D_K)
  • com.ng/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • . to ng: 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