Skip to content
https://yahoo.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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), 603 ms total
REVIEW
2 redirect(s), 603 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: 603 ms total
Got: 603 ms
Info::
Cross-domain redirect detected

https://yahoo.net

153 ms · HTTP/1.1

301

https://www.yahoo.com/

110 ms · HTTP/1.1

302

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

340 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yahoo.net301153 msHTTP/1.1ATS
2https://www.yahoo.com/302110 msHTTP/1.1ATS
3https://fr.yahoo.com/?p=us200340 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

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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

Certificate validity

140
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
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.158.7, 76.223.84.192
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns4.yahoo.com, ns3.yahoo.com, ns1.yahoo.com, ns5.yahoo.com, ns2.yahoo.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 45 ms
Got: 45 ms
A13.248.158.7, 76.223.84.192
AAAA—
CNAME—
NSns4.yahoo.com, ns3.yahoo.com, ns1.yahoo.com, ns5.yahoo.com, ns2.yahoo.com
MX—
TXT
amazonses:l26oCOl4p7bPrhrse4RcrTu1iKNbHWhxrblwY0RX9YM=.
amazonses:TtryBTe3Q/LLz0Nwcy8OUv0qcYXzI8tPR6ixqIuw90s=
amazonses:EnbnmFEAKBMZSbTqWyo4E+hzXrPANKQHQ1ugEiFWZzo=.
573939513d9744fbb2d6d771db0da5f1
_globalsign-domain-verification=NYU1O1TQAqUirL7_fn8foXUwdv6btiX5cgvqDhz5ep
_globalsign-domain-verification=yN9zuBTHNuXh064MiJWs5z7PX_fYWqjKiqfqZjv8Gz
Yahoo! Inc.
amazonses:jAUY35DpkZkklWFLdBdQfGMg8/BATXxQy/FvNNjFMfs=.
google-site-verification=A3PWHiaNNyze9dUd912GqDlLtRAOiJWfTyz7wASIUpg
amazonses:fO/t01sOa8kmYFgc1Ng5JKmkQf/hE2A/PP+dTpho7Ps=.
amazonses:R3I1t36hqiAYva5U4WNUN40GcC4RcscNPLaxs8Qz7fo=.
xwKIyW1RR2lzEBJdk5a8vtPQ50/5gvqfB74NsfgSzeQ=
amazonses:X4Z9c+WtlYvX1WqYuZaMcCr6poj4zcB9anTAi/vLTN4=.
CAALookup not available with standard resolver
Resolved in 45 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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 Perplexity-ai, scoop.it, AwarioRssBot, FacebookBot, PerplexityBot, TurnitinBot, CCBot, SeznamBot, Meltwater, huggingface, img2dataset, magpie-crawler, omgili, PiplBot, anthropic-ai, Bytespider, Claude-Web, Diffbot, ImagesiftBot, PetalBot, cohere-ai, GPTBot, omgilibot, Scrapy, YouBot, Claude-SearchBot, ChatGPT-User, claritybot, ClaudeBot, Neevabot, SentiBot, ZumBot, NewsNow, *, AlphaBot, AwarioSmartBot, FriendlyCrawler, Google-Extended, Seekr, OAI-SearchBot, ADmantX, BLEXBot, Buzzbot, news-please, Nutch, panscient.com 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

301https://www.yahoo.net/
200https://yahoo.net/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
yahoo.net — via MarkMonitor Inc., 29 years, 10 months old, hosted on AWS
PASS
yahoo.net — via MarkMonitor Inc., 29 years, 10 months old, hosted on AWS
Info::
Domain registered until Nov 3, 2026 (6 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

140 days

November 3, 2026

SSL certificate

140 days

Issued by DigiCert Inc

Domain age

29 years, 10 months

Registered November 4, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.158.7

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 November 4, 1996 (29 years, 10 months ago)
Expires November 3, 2026 (6 months)
Last Updated October 2, 2025
Name Servers ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com
DNSSEC Not enabled
Hosting
IP Address 13.248.158.7
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 200 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
48 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
101 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
200 ms
Total Time Total request time from DNS lookup through full response.
201 ms

Connection waterfall

DNS Lookup 48 ms TCP Connect 1 ms TLS Handshake 101 ms Server Processing 51 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