kenic.or.ke
Updated:
2022-01-26 09:58:17 UTC (1024 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (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 (2)
- or.ke/SOA
- or.ke/SOA
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of kenic.or.ke/DS
- 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)
- kenic.or.ke/DS (alg 13, id 52798)
- 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)
Non_existent (1)
- kenic.or.ke/DNSKEY (alg 13, id 52798)
Delegation status
Bogus (1)
- or.ke to kenic.or.ke
Secure (2)
- . to ke
- ke to or.ke
Notices
Errors (20)
- 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.
- 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.
- NSEC3 proving non-existence of kenic.or.ke/DS: No NSEC3 RR matches the SNAME (kenic.or.ke). See RFC 5155, Sec. 8.6.
- NSEC3 proving non-existence of kenic.or.ke/DS: No NSEC3 RR matches the SNAME (kenic.or.ke). See RFC 5155, Sec. 8.6.
- kenic.or.ke/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN)
- kenic.or.ke/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN)
- kenic.or.ke/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- kenic.or.ke/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN)
- kenic.or.ke/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- kenic.or.ke/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN)
- or.ke to kenic.or.ke: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- or.ke to kenic.or.ke: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (196.1.4.148, 196.13.202.39, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:6818:d6ff:fe71:353e, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- 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/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- kenic.or.ke/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- kenic.or.ke/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- tkposhjrg9.kenic.or.ke/A has errors; select the "Denial of existence" DNSSEC option to see them.
- kenic.or.ke/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- 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.
- 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.
