View on GitHub

DNSViz: A DNS visualization tool

co.ke

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (7)
  • co.ke/A (NODATA)
  • co.ke/AAAA (NODATA)
  • co.ke/SOA
  • ke/SOA
  • ke/SOA
  • ke/SOA
  • ke/SOA
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (1)
  • NSEC3 proving non-existence of co.ke/AAAA
Secure (3)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC proving non-existence of ke/DS
Non_existent (1)
  • co.ke/DNSKEY (alg 8, id 64164)

Delegation statusDelegation status

Insecure (1)
  • . to ke

NoticesNotices

Errors (9)
  • NSEC3 proving non-existence of co.ke/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of co.ke/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of co.ke/AAAA alg 8, id 64164: The Signature Expiration field of the RRSIG RR (2022-09-11 06:58:04+00:00) is 86 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of co.ke/AAAA alg 8, id 64164: The Signer's Name field of the RRSIG RR (co.ke) does not match the name of the zone containing the RRset (ke). See RFC 4035, Sec. 5.3.1.
  • RRSIG co.ke/SOA alg 8, id 64164: The Signature Expiration field of the RRSIG RR (2022-09-14 21:16:20+00:00) is 83 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG co.ke/SOA alg 8, id 64164: The Signer's Name field of the RRSIG RR (co.ke) does not match the name of the zone containing the RRset (ke). See RFC 4035, Sec. 5.3.1.
  • co.ke/AAAA (NODATA): An SOA RR with owner name (co.ke) not matching the zone name (ke) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (2001:43f8:120::22, UDP_-_EDNS0_4096_D_KN)
  • ke zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.168.22)
  • ke/DNSKEY: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (196.216.168.22, TCP_-_EDNS0_4096_D_KN)
Warnings (2)
  • NSEC3 proving non-existence of co.ke/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of co.ke/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.

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