tm
Updated:
2024-03-04 17:39:55 UTC (264 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- tm/NS
- tm/NSEC3PARAM
- tm/SOA
DNSKEY/DS/NSEC status
Secure (5)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- tm/DNSKEY (alg 8, id 36787)
- tm/DNSKEY (alg 8, id 55352)
- tm/DS (alg 8, id 36787)
Delegation status
Secure (1)
- . to tm
Notices
Errors (4)
- tm zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:feb8::5:8)
- tm/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:feb8::5:8, UDP_-_NOEDNS_)
- tm/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- j7w64mv1gh.tm/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- tm/NS: 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. (80.249.100.44, UDP_-_EDNS0_4096_D_KN)
- tm/NSEC3PARAM: 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. (80.249.100.44, UDP_-_EDNS0_4096_D_KN)
- tm/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. (80.249.100.44, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- tm/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- j7w64mv1gh.tm/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
