hey.com
Updated:
2024-03-02 06:21:22 UTC (about a year ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- hey.com/A
- hey.com/MX
- hey.com/NS
- hey.com/SOA
- hey.com/SOA
- hey.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- NSEC3 proving non-existence of hey.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 4534)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to hey.com
Secure (1)
- . to com
Notices
Warnings (4)
- com to hey.com: Authoritative AAAA records exist for ns-201.awsdns-25.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- hey.com/A: 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. (2a00:edc0:6259:7:5::4, UDP_-_EDNS0_4096_D_KN)
- hey.com/SOA: 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. (2a00:edc0:6259:7:5::2, UDP_-_EDNS0_4096_D_KN)
- hey.com/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
