go.ke
Updated:
2022-11-29 23:16:55 UTC (523 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 (20)
- 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.
- 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.
- 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.
- go.ke zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. (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. (196.216.162.70)
- go.ke zone: The server(s) were not responsive to queries over UDP. (2001:43f8:e0:1::70)
- go.ke/DNSKEY: No response was received from the server over TCP (tried 1 times). (196.216.168.22, TCP_-_EDNS0_4096_D_KN)
- go.ke/DNSKEY: No response was received from the server over UDP (tried 4 times). (196.216.168.22, UDP_-_EDNS0_512_D_KN)
- go.ke/DNSKEY: The response had an invalid RCODE (SERVFAIL). (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). (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. (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). (2001:43f8:e0:1::70, UDP_-_NOEDNS_)
- go.ke/NS: The response had an invalid RCODE (SERVFAIL). (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. (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). (196.216.168.22, TCP_-_EDNS0_4096_D_N)
- go.ke/SOA: The response had an invalid RCODE (SERVFAIL). (196.216.162.70, TCP_-_NOEDNS_)
- go.ke/SOA: The response had an invalid RCODE (SERVFAIL). (196.216.162.70, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- go.ke/TXT: The response had an invalid RCODE (SERVFAIL). (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
Warnings (2)
- 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). (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. (196.216.168.22, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
