View on GitHub

DNSViz: A DNS visualization tool

gov.cm

« 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 (6)
  • cm/SOA
  • cm/SOA
  • gov.cm/NS
  • gov.cm/NS (NODATA)
  • gov.cm/SOA
  • gov.cm/SOA (NODATA)
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

Insecure (2)
  • . to cm
  • cm to gov.cm

NoticesNotices

Errors (22)
  • cm zone: The following NS name(s) did not resolve to address(es): benoue.camnet.cm
  • cm zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (198.6.1.82)
  • 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.35)
  • cm/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.82, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • gov.cm zone: The following NS name(s) did not resolve to address(es): benoue.camnet.cm
  • gov.cm zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (41.205.23.134, 41.205.23.136, 195.24.192.33, 195.24.192.34)
  • gov.cm zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (41.205.23.134, 41.205.23.136, 195.24.192.33, 195.24.192.34)
  • gov.cm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (195.24.192.35)
  • gov.cm/DNSKEY: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (195.24.203.4, UDP_-_EDNS0_512_D_K)
  • gov.cm/DS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.82, UDP_-_NOEDNS_)
  • gov.cm/NS (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (41.205.23.134, 41.205.23.136, UDP_-_EDNS0_4096_D_K)
  • gov.cm/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (195.24.192.35, UDP_-_EDNS0_4096_D_K)
  • gov.cm/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (198.6.1.82, UDP_-_NOEDNS_)
  • gov.cm/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (41.205.23.134, 41.205.23.136, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • gov.cm/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (41.205.23.134, 41.205.23.136, 195.24.192.33, 195.24.192.34, TCP_-_EDNS0_4096_D)
  • gov.cm/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • . 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.
  • cm to gov.cm: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the cm zone): ns1.mtnbusiness.cm, benoue.camnet.cm, mbam.camnet.cm, ns2.mtnbusiness.cm, lom.camnet.cm See RFC 1034, Sec. 4.2.2.
  • cm to gov.cm: The server(s) for the parent zone (cm) responded with a referral instead of answering authoritatively for the DS RR type. See RFC 4034, Sec. 5. (195.24.192.34, UDP_-_EDNS0_4096_D_K)
  • gov.cm/NS: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (195.24.203.4, UDP_-_EDNS0_4096_D_K)
  • gov.cm/SOA: The response had an invalid RCODE (FORMERR) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (195.24.203.4, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • gov.cm/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • tagkv0nz6m.gov.cm/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.cm/A has warnings; select the "Denial of existence" DNSSEC option to see them.

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