co.ke
Updated:
2023-03-18 11:04:34 UTC (1005 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- co.ke/A (NODATA)
- co.ke/AAAA (NODATA)
- ke/SOA
- ke/SOA
- ke/SOA
- ke/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of co.ke/A
- NSEC3 proving non-existence of co.ke/AAAA
- ke/DNSKEY (alg 8, id 10155)
- ke/DNSKEY (alg 8, id 28886)
- ke/DS (alg 8, id 28886)
Delegation status
Secure (1)
- . to ke
Notices
Errors (5)
- NSEC3 proving non-existence of co.ke/A: 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/A: 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.
- 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.
- ke/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of co.ke/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of co.ke/A: 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.
- NSEC3 proving non-existence of co.ke/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- ke/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
