tn
Updated:
2021-10-06 08:55:50 UTC (994 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- tn/NS
- tn/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- tn/DNSKEY (alg 8, id 36171)
- tn/DNSKEY (alg 8, id 8629)
- tn/DS (alg 8, id 8629)
Delegation status
Secure (1)
- . to tn
Notices
Errors (2)
- tn/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_512_D_KN)
- tn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- ./DNSKEY (alg 8, id 14748): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 26838): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (193.0.14.129, UDP_-_EDNS0_4096_D_KN)
- tn/SOA: 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. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
