kenic.or.ke
Updated:
2022-03-15 07:11:46 UTC (975 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- kenic.or.ke/A
- kenic.or.ke/AAAA
- kenic.or.ke/MX
- kenic.or.ke/NS
- kenic.or.ke/SOA
- kenic.or.ke/TXT
Secure (1)
- or.ke/SOA
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of kenic.or.ke/DS
- ke/DNSKEY (alg 8, id 10600)
- ke/DNSKEY (alg 8, id 3198)
- ke/DNSKEY (alg 8, id 41201)
- ke/DS (alg 8, id 41201)
- ke/DS (alg 8, id 41201)
- or.ke/DNSKEY (alg 8, id 11298)
- or.ke/DNSKEY (alg 8, id 15787)
- or.ke/DNSKEY (alg 8, id 39427)
- or.ke/DS (alg 8, id 15787)
- or.ke/DS (alg 8, id 39427)
Delegation status
Insecure (1)
- or.ke to kenic.or.ke
Secure (2)
- . to ke
- ke to or.ke
Notices
Errors (4)
- 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.
- or.ke zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:43f8:e0:1::70)
- kenic.or.ke/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 9799): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- 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.
JavaScript is required to make the graph below interactive.
