www.google.co.ke

Updated: 2020-07-31 09:49:08 UTC (1575 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46594)
NSEC3 proving non-existence of google.co.ke/DS
co.ke/DNSKEY (alg 8, id 14028)
co.ke/DNSKEY (alg 8, id 50050)
co.ke/DS (alg 8, id 50050)
ke/DNSKEY (alg 8, id 41201)
ke/DNSKEY (alg 8, id 63355)
ke/DS (alg 8, id 41201)
ke/DS (alg 8, id 41201)

NSEC3 proving non-existence of google.co.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 google.co.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 google.co.ke/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of google.co.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.