View on GitHub

DNSViz: A DNS visualization tool

com.ng

Updated: 2023-01-31 05:58:17 UTC (695 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 (10)
  • com.ng/NS
  • com.ng/SOA
  • com.ng/SOA
  • com.ng/SOA
  • com.ng/TXT
  • com.ng/TXT
  • com.ng/TXT
  • ng/SOA
  • 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 951)
  • NSEC proving non-existence of ng/DS

Delegation statusDelegation status

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

NoticesNotices

Errors (19)
  • com.ng zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.222.79.26)
  • com.ng zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.222.79.26)
  • com.ng/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • com.ng/DS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, UDP_-_EDNS0_4096_D_KN)
  • com.ng/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, UDP_-_EDNS0_4096_D_KN)
  • com.ng/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, TCP_-_EDNS0_4096_D_N)
  • com.ng/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • com.ng/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, UDP_-_EDNS0_4096_D_KN)
  • 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_KN)
  • ng zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.222.79.26)
  • ng/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (41.222.79.26, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • com.ng/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ltydr49qco.com.ng/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • com.ng/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • com.ng/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • com.ng/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • com.ng/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • com.ng/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • com.ng/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • . to ng: The glue address(es) for ns2.nic.net.ng (204.61.216.40) differed from its authoritative address(es) (41.222.79.26, 204.61.216.40). 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