gov.cm
Updated:
2023-12-11 17:13:19 UTC (390 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- cm/SOA
- cm/SOA
- gov.cm/NS
- gov.cm/SOA
Secure (1)
- ./SOA
DNSKEY/DS/NSEC status
Secure (3)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC proving non-existence of cm/DS
Delegation status
Insecure (2)
- . to cm
- cm to gov.cm
Notices
Errors (4)
- cm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (195.24.192.17, 195.24.192.34, 195.24.192.35)
- gov.cm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (195.24.203.8)
- gov.cm/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (195.24.203.8, UDP_-_NOEDNS_)
- gov.cm/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- . to cm: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): ns1.nic.cm, ns-cm.nic.fr, phloem.uoregon.edu, ns2.nic.cm, ns-cm.afrinic.net See RFC 1034, Sec. 4.2.2.
- . to cm: The following NS name(s) were found in the delegation NS RRset (i.e., in the . zone), but not in the authoritative NS RRset: kim.camnet.cm, lom.camnet.cm, sanaga.camnet.cm See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
