View on GitHub

DNSViz: A DNS visualization tool

gov.cm

Updated: 2023-12-11 17:13:19 UTC (146 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (4)
  • cm/SOA
  • cm/SOA
  • gov.cm/NS
  • gov.cm/SOA
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • cm zone: The server(s) were not responsive to queries over UDP. (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. (195.24.203.8)
  • gov.cm/NS: No response was received from the server over UDP (tried 12 times). (195.24.203.8, UDP_-_NOEDNS_)
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
  • . 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

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