go.ke
Updated:
2022-11-29 23:16:55 UTC (767 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (12)
- go.ke/NS
- go.ke/NS (NODATA)
- go.ke/SOA
- go.ke/SOA (NODATA)
- go.ke/TXT
- go.ke/TXT
- go.ke/TXT
- ke/SOA
- ke/SOA
- ke/SOA
- ke/SOA
- ke/SOA
Secure (1)
- ./SOA
DNSKEY/DS/NSEC status
Secure (3)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC proving non-existence of ke/DS
Non_existent (1)
- go.ke/DNSKEY (alg 8, id 4905)
Delegation status
Insecure (2)
- . to ke
- ke to go.ke
Notices
Errors (28)
- RRSIG go.ke/NS alg 8, id 4905: The Signature Expiration field of the RRSIG RR (2022-09-10 19:39:16+00:00) is 80 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG go.ke/SOA alg 8, id 4905: The Signature Expiration field of the RRSIG RR (2022-09-14 07:38:01+00:00) is 76 days in the past. See RFC 4035, Sec. 5.3.1.
- RRSIG go.ke/TXT alg 8, id 4905: The Signature Expiration field of the RRSIG RR (2022-09-14 02:04:42+00:00) is 76 days in the past. See RFC 4035, Sec. 5.3.1.
- go.ke zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.162.70, 196.216.168.22)
- go.ke zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.216.162.70)
- go.ke zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:43f8:e0:1::70)
- go.ke/DNSKEY: No response was received from the server over TCP (tried 1 times). See RFC 1035, Sec. 4.2. (196.216.168.22, TCP_-_EDNS0_4096_D_KN)
- go.ke/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (196.216.168.22, UDP_-_EDNS0_512_D_KN)
- go.ke/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- go.ke/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.216.168.22, UDP_-_NOEDNS_)
- go.ke/NS (NODATA): An SOA RR with owner name (ke) not matching the zone name (go.ke) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (147.135.106.237, 185.28.194.194, 185.38.108.108, 196.1.4.3, 196.1.4.130, 196.216.168.22, 198.32.67.9, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:50c0:a8ff:feee:30, 2604:2dc0:200:2eb::237, UDP_-_EDNS0_4096_D_KN)
- go.ke/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:43f8:e0:1::70, UDP_-_NOEDNS_)
- go.ke/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, UDP_-_NOEDNS_)
- go.ke/SOA (NODATA): An SOA RR with owner name (ke) not matching the zone name (go.ke) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (147.135.106.237, 185.28.194.194, 185.38.108.108, 196.1.4.3, 196.1.4.130, 196.216.168.22, 198.32.67.9, 204.61.216.7, 2001:500:14:6007:ad::1, 2001:43f8:10:0:50c0:a8ff:feee:30, 2001:43f8:120::22, 2604:2dc0:200:2eb::237, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_0x20, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- go.ke/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (196.216.168.22, TCP_-_EDNS0_4096_D_N)
- go.ke/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, TCP_-_NOEDNS_)
- go.ke/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- go.ke/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.162.70, UDP_-_NOEDNS_)
- ke zone: The following NS name(s) did not resolve to address(es): ns.anycast.kenic.or.ke
- ke zone: There was an error resolving the following NS name(s) to address(es): mzizi.kenic.or.ke
- k7zvjyoi9a.go.ke/A has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- go.ke/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- go.ke/SOA (NODATA): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (196.216.168.22, UDP_-_EDNS0_4096_D_KN_0x20)
- go.ke/SOA (NODATA): 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. (196.216.168.22, UDP_-_EDNS0_4096_D_KN)
- go.ke/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- go.ke/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- go.ke/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- go.ke/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
