nytimes.com
Updated:
2024-11-05 08:10:27 UTC (18 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- nytimes.com/A
- nytimes.com/MX
- nytimes.com/NS
- nytimes.com/SOA
- nytimes.com/SOA
- nytimes.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of nytimes.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 29942)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to nytimes.com
Secure (1)
- . to com
Notices
Warnings (4)
- ./DNSKEY (alg 8, id 20326): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 61050): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- com to nytimes.com: Authoritative AAAA records exist for ns-244.awsdns-30.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- nytimes.com/TXT: 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. (2600:9000:5300:f400::1, 2600:9000:5302:7b00::1, 2600:9000:5305:3000::1, 2600:9000:5306:7400::1, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
