gov.cm
Updated:
2021-11-13 17:01:20 UTC (1152 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- cm/SOA
- cm/SOA
- cm/SOA
- gov.cm/NS
- gov.cm/SOA
Secure (1)
- ./SOA
DNSKEY/DS/NSEC status
Secure (3)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- 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)
- gov.cm/DS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (195.24.208.2, UDP_-_NOEDNS_)
- gov.cm/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (195.24.192.35, 195.24.208.2, UDP_-_NOEDNS_)
- gov.cm/DS 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, benoue.camnet.cm, ns-cm.afrinic.net, ns2.nic.cm, mbam.camnet.cm 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: sanaga.camnet.cm See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
