View on GitHub

DNSViz: A DNS visualization tool

gov.gh

« 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 (4)
  • gh/SOA
  • gov.gh/NS
  • gov.gh/SOA
  • gov.gh/TXT
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

Incomplete (1)
  • gh to gov.gh
Insecure (1)
  • . to gh

NoticesNotices

Errors (2)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_K)
  • gh to gov.gh: No delegation NS records were detected in the parent zone (gh). This results in an NXDOMAIN response to a DS query (for DNSSEC), even if the parent servers are authoritative for the child. See RFC 1034, Sec. 4.2.2. (197.253.95.251, 197.253.127.251, 200.160.0.5, 2001:12ff:0:a20::5, UDP_-_EDNS0_4096_D_K)

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