nkn.in
Updated:
2023-11-21 16:14:42 UTC (369 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- nkn.in/A
- nkn.in/MX
- nkn.in/NS
- nkn.in/SOA
- nkn.in/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- in/DNSKEY (alg 8, id 25291)
- in/DNSKEY (alg 8, id 27000)
- in/DS (alg 8, id 25291)
- nkn.in/DNSKEY (alg 8, id 13711)
- nkn.in/DNSKEY (alg 8, id 20586)
- nkn.in/DS (alg 8, id 13711)
Delegation status
Secure (2)
- . to in
- in to nkn.in
Notices
Warnings (6)
- in/DS (alg 8, id 25291): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
- in/DS (alg 8, id 25291): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, UDP_-_EDNS0_4096_D_KN)
- nkn.in/DNSKEY (alg 8, id 13711): 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. (2405:8a00:4::4, UDP_-_EDNS0_4096_D_KN)
- nkn.in/DNSKEY (alg 8, id 20586): 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. (2405:8a00:4::4, UDP_-_EDNS0_4096_D_KN)
- nkn.in/TXT: 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. (2405:8a00:bb::bb, UDP_-_EDNS0_4096_D_KN)
- nkn.in/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
