yahoo.com
Updated:
2020-12-26 07:47:54 UTC (1379 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- yahoo.com/A
- yahoo.com/AAAA
- yahoo.com/MX
- yahoo.com/NS
- yahoo.com/SOA
- yahoo.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ./DNSKEY (alg 8, id 42351)
- NSEC3 proving non-existence of yahoo.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 31510)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to yahoo.com
Secure (1)
- . to com
Notices
Errors (15)
- . to com: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (192.35.51.30, TCP_-_EDNS0_4096_)
- . to com: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (192.35.51.30, TCP_-_EDNS0_4096_)
- com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (192.42.93.30, 192.43.172.30, 192.54.112.30)
- com/DNSKEY (alg 8, id 30909): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (192.35.51.30, TCP_-_EDNS0_4096_)
- com/DNSKEY (alg 8, id 30909): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (192.35.51.30, UDP_-_EDNS0_4096_D_KN)
- com/DNSKEY (alg 8, id 31510): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (192.35.51.30, TCP_-_EDNS0_4096_)
- com/DNSKEY (alg 8, id 31510): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (192.35.51.30, UDP_-_EDNS0_4096_D_KN)
- com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.35.51.30, UDP_-_EDNS0_512_D_KN)
- yahoo.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (27.123.42.42, 68.142.255.16, 68.180.131.16, 98.138.11.157, 202.165.97.53, 2001:4998:130::1001, 2001:4998:140::1002, 2406:2000:ff60::53, 2406:8600:f03f:1f8::1003)
- yahoo.com/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (27.123.42.42, 2406:8600:f03f:1f8::1003, TCP_-_EDNS0_4096_D_KN)
- yahoo.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (27.123.42.42, 2406:8600:f03f:1f8::1003, UDP_-_EDNS0_512_D_KN)
- yahoo.com/MX: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (27.123.42.42, TCP_-_EDNS0_4096_D_N)
- yahoo.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (27.123.42.42, UDP_-_EDNS0_512_D_KN)
- yahoo.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (27.123.42.42, 68.142.255.16, 68.180.131.16, 98.138.11.157, 202.165.97.53, 2001:4998:130::1001, 2001:4998:140::1002, 2406:2000:ff60::53, 2406:8600:f03f:1f8::1003, TCP_-_EDNS0_4096_D_N)
- yahoo.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- yahoo.com/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. (27.123.42.42, UDP_-_EDNS0_4096_D_KN)
- yahoo.com/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. (2406:8600:f03f:1f8::1003, UDP_-_EDNS0_4096_D_KN)
- yahoo.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. (27.123.42.42, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
