Skip to content
https://yahoo.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
2 redirect(s), 722 ms total
REVIEW
2 redirect(s), 722 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.yahoo.com/
Info::
Redirect overhead: 722 ms total
Got: 722 ms
Info::
Cross-domain redirect detected

https://yahoo.com

330 ms · HTTP/1.1

301

https://www.yahoo.com/

95 ms · HTTP/1.1

302

https://fr.yahoo.com/?p=us

296 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yahoo.com301330 msHTTP/1.1ATS
2https://www.yahoo.com/30295 msHTTP/1.1ATS
3https://fr.yahoo.com/?p=us200296 msHTTP/1.1ATS

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

B
TLS Certificate Expiry & Recommendations
132 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

132
days left
0d 30d 60d 90d+

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
6 A records, 30 ms lookup
PASS
6 A records, 30 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 74.6.231.21, 74.6.231.20, 74.6.143.26, 74.6.143.25, 98.137.11.164, 98.137.11.163
Info::
Has 6 IPv6 (AAAA) record(s)
Got: 2001:4998:24:120d::1:1, 2001:4998:124:1507::f001, 2001:4998:24:120d::1:0, 2001:4998:44:3507::8000, 2001:4998:124:1507::f000, 2001:4998:44:3507::8001
Info::
5 nameserver(s) configured
Got: ns3.yahoo.com, ns1.yahoo.com, ns5.yahoo.com, ns4.yahoo.com, ns2.yahoo.com
Info::
3 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 30 ms
Got: 30 ms
A74.6.231.21, 74.6.231.20, 74.6.143.26, 74.6.143.25, 98.137.11.164, 98.137.11.163
AAAA2001:4998:24:120d::1:1, 2001:4998:124:1507::f001, 2001:4998:24:120d::1:0, 2001:4998:44:3507::8000, 2001:4998:124:1507::f000, 2001:4998:44:3507::8001
CNAME—
NSns3.yahoo.com, ns1.yahoo.com, ns5.yahoo.com, ns4.yahoo.com, ns2.yahoo.com
MX
1 mta6.am0.yahoodns.net
1 mta5.am0.yahoodns.net
1 mta7.am0.yahoodns.net
TXT
SPF v=spf1 redirect=_spf.mail.yahoo.com
google-site-verification=w4N2bNopAWw1xYrdXKORILxx-WW3_LIiyX6dIMIidgk
google-site-verification=GLp01gkFNopm_JItbLxml4iuVbTgJa3rKu0-eq1RvsE
edb3bff2c0d64622a9b2250438277a59
facebook-domain-verification=gysqrcd69g0ej34f4jfn0huivkym1p
google-site-verification=2b0Glh8l2icXIAgAcjOcFx16Jt26yWDgEyrk5hPD-ZY
google-site-verification=xoBvU6aKxP0gYgNL0iXqF0EccAg6nFrO7XxsHnc3iNQ
google-site-verification=GU8WAl0zPqaxdcZqDjuN7pqdfPCpR9Amz9rwxMG91qw
google-site-verification=2b8irRvU5a2h4Mb-H_fdqNrqWjS00qmPfPcWqm8BhxI
Zoom=13284637
google-site-verification=Z3-Vh6zqUMgybVH4wQl1GxKSKN7JE13kyCyeZ3TZZ-I
_globalsign-domain-verification=HOeO-_wfYsqBPIRhct0u92OioWzwfg5YahDu63Jvbg
CAALookup not available with standard resolver
Resolved in 30 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
IPv6 Readiness
IPv6 reachable (169 ms)
PASS
IPv6 reachable (169 ms)
Info::
IPv6 is configured and reachable at 2001:4998:24:120d::1:1, 2001:4998:124:1507::f001, 2001:4998:24:120d::1:0, 2001:4998:44:3507::8000, 2001:4998:124:1507::f000, 2001:4998:44:3507::8001
Got: 169 ms connect
IPv6 Ready
AAAA Records 2001:4998:24:120d::1:1, 2001:4998:124:1507::f001, 2001:4998:24:120d::1:0, 2001:4998:44:3507::8000, 2001:4998:124:1507::f000, 2001:4998:44:3507::8001 Connection Reachable (169 ms)
A+
Crawlability
robots.txt present, sitemap with 242 URLs
PASS
robots.txt present, sitemap with 242 URLs
Info::
robots.txt is present
Got: 1624 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 242 entries
Info::
Sitemap index with 242 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1624 B Sitemaps referenced 3 User-agents Claude-Web, Nutch, omgilibot, NewsNow, ClaudeBot, AlphaBot, ChatGPT-User, FacebookBot, Perplexity-ai, SeznamBot, ImagesiftBot, magpie-crawler, omgili, PerplexityBot, PiplBot, YouBot, AwarioSmartBot, cohere-ai, AwarioRssBot, BLEXBot, img2dataset, Neevabot, Scrapy, Seekr, TurnitinBot, ZumBot, ADmantX, Buzzbot, claritybot, FriendlyCrawler, GPTBot, PetalBot, Claude-SearchBot, Bytespider, CCBot, Google-Extended, huggingface, Meltwater, news-please, SentiBot, OAI-SearchBot, *, anthropic-ai, Diffbot, panscient.com, scoop.it Blocking No — crawling allowed
User-agent: *
Disallow: /info/p.gif
Disallow: /p/
Disallow: /r/
Disallow: /bin/
Disallow: /caas/
Disallow: /blank.html
Disallow: /includes/
Disallow: /_td_api
Disallow: /tdv2_fp
Disallow: /nel_ms
Disallow: /fp_ms
Disallow: /sports_fp_ms
Disallow: /search_ms
Disallow: /_tdpp_api
Disallow: /_remote
Disallow: /_multiremote
Disallow: /_tdhl_api
Disallow: /digest
Disallow: /fpjs
Disallow: /myjs
Disallow: /news/m/

User-agent: ADmantX
User-agent: AlphaBot
User-agent: anthropic-ai
User-agent: AwarioRssBot
User-agent: AwarioSmartBot
User-agent: BLEXBot
User-agent: Buzzbot
User-agent: Bytespider
User-agent: CCBot
User-agent: ChatGPT-User
User-agent: claritybot
User-agent: Claude-Web
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: Diffbot
User-agent: FacebookBot
User-agent: FriendlyCrawler
User-agent: Google-Extended
User-agent: GPTBot
User-agent: huggingface
User-agent: ImagesiftBot
User-agent: img2dataset
User-agent: magpie-crawler
User-agent: Meltwater
User-agent: Neevabot
User-agent: news-please
User-agent: NewsNow
User-agent: Nutch
User-agent: omgili
User-agent: omgilibot
User-agent: panscient.com
User-agent: Perplexity-ai
User-agent: PerplexityBot
User-agent: PetalBot
User-agent: PiplBot
User-agent: scoop.it
User-agent: Scrapy
User-agent: Seekr
User-agent: SentiBot
User-agent: SeznamBot
User-agent: TurnitinBot
User-agent: YouBot
User-agent: ZumBot
Disallow: /

User-agent: Claude-SearchBot
User-agent: OAI-SearchBot
Disallow: */articles/

Sitemap: https://www.yahoo.com/news/weather/sitemap.xml
Sitemap: https://www.yahoo.com/news-sitemap-index.xml
Sitemap: https://www.yahoo.com/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 242 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.yahoo.com/
200https://yahoo.com/

Preferred variant: non-www

HTTP → HTTPS

301http://yahoo.com/ → https://yahoo.com/

Consistent

A+
Domain Intelligence
yahoo.com — via MarkMonitor Inc., 31 years, 8 months old
PASS
yahoo.com — via MarkMonitor Inc., 31 years, 8 months old
Info::
Domain registered until Jan 19, 2027 (9 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Domain expiry

217 days

January 19, 2027

SSL certificate

132 days

Issued by DigiCert Inc

Domain age

31 years, 8 months

Registered January 18, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:4998:124:1507::f001

Registrar

MarkMonitor Inc.

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created January 18, 1995 (31 years, 8 months ago)
Expires January 19, 2027 (9 months)
Last Updated December 18, 2025
Name Servers ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com
DNSSEC Not enabled
Hosting
IP Address 2001:4998:124:1507::f001
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 548 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
18 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
175 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
176 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
548 ms
Total Time Total request time from DNS lookup through full response.
548 ms

Connection waterfall

DNS Lookup 18 ms TCP Connect 175 ms TLS Handshake 176 ms Server Processing 180 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback