cnn.com
Updated:
2024-11-11 07:36:16 UTC (10 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- cnn.com/A
- cnn.com/AAAA
- cnn.com/MX
- cnn.com/NS
- cnn.com/SOA
- cnn.com/TXT
Secure (1)
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of cnn.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 cnn.com
Secure (1)
- . to com
Notices
Errors (1)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.33.4.12, UDP_-_EDNS0_512_D_KN)
Warnings (2)
- cnn.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:2f00::1, 2600:9000:5302:4000::1, 2600:9000:5306:5e00::1, UDP_-_EDNS0_4096_D_KN)
- com to cnn.com: Authoritative AAAA records exist for ns-47.awsdns-05.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
