com.ng

Updated: 2023-01-17 02:50:24 UTC (710 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset 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 status

Secure (3)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 951)
NSEC proving non-existence of ng/DS

Delegation status

Insecure (2)

. to ng
ng to com.ng

Notices

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.
b7ydhcigx5.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.