tn
Updated:
2022-02-16 19:30:55 UTC (1060 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- tn/NS
- tn/SOA
- tn/SOA
DNSKEY/DS/NSEC status
Secure (5)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- 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 (5)
- tn zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (147.28.0.39, 2001:418:1::39)
- tn/DNSKEY: No response was received from the server over UDP (tried 9 times). See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_)
- tn/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (147.28.0.39, TCP_-_EDNS0_4096_D_N)
- tn/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (2001:418:1::39, TCP_-_EDNS0_4096_D_N)
- tn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- 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)
- tn/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
