hanover.com
Updated:
2022-08-26 14:12:46 UTC (818 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- hanover.com/A
- hanover.com/MX
- hanover.com/NS
- hanover.com/SOA
- hanover.com/SOA
- hanover.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC3 proving non-existence of hanover.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 32298)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to hanover.com
Secure (1)
- . to com
Notices
Warnings (3)
- ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20826): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
- hanover.com/SOA: The case of the query name (hanover.com) was not preserved in the Question section of the response. (13.107.24.2, 40.90.4.2, 2620:1ec:8ec::2, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
