kenic.or.ke

Updated: 2022-06-17 14:58:30 UTC (879 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
NSEC3 proving non-existence of kenic.or.ke/DS
ke/DNSKEY (alg 8, id 10600)
ke/DNSKEY (alg 8, id 31896)
ke/DNSKEY (alg 8, id 41201)
ke/DS (alg 8, id 41201)
ke/DS (alg 8, id 41201)
or.ke/DNSKEY (alg 8, id 15787)
or.ke/DNSKEY (alg 8, id 18963)
or.ke/DNSKEY (alg 8, id 39427)
or.ke/DS (alg 8, id 15787)
or.ke/DS (alg 8, id 39427)

NSEC3 proving non-existence of kenic.or.ke/DS: 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 kenic.or.ke/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
kenic.or.ke/DS has errors; select the "Denial of existence" DNSSEC option to see them.

NSEC3 proving non-existence of kenic.or.ke/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of kenic.or.ke/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
ke/DS (alg 8, id 41201): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ke/DS (alg 8, id 41201): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ke/DS (alg 8, id 41201): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
ke/DS (alg 8, id 41201): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
or.ke to kenic.or.ke: Authoritative AAAA records exist for ns.anycast.kenic.or.ke, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
kenic.or.ke/DS has warnings; select the "Denial of existence" DNSSEC option to see them.