Skip to content
https://sportingnews.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700::6812:fd8, 2606:4700::6812:ed8
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700::6812:fd8]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700::6812:fd8, 2606:4700::6812:ed8 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
Redirect Chain
2 redirect(s), 84 ms total
REVIEW
2 redirect(s), 84 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.sportingnews.com/

https://sportingnews.com

32 ms · HTTP/1.1

301

https://www.sportingnews.com/

21 ms · HTTP/1.1

302

https://www.sportingnews.com/us

31 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sportingnews.com30132 msHTTP/1.1cloudflare
2https://www.sportingnews.com/30221 msHTTP/1.1cloudflare
3https://www.sportingnews.com/us20031 msHTTP/1.1cloudflare

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
67 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f005ba53e4d1679-SJC
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f005ba53e4d1679-SJC
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.14.216, 104.18.15.216
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:fd8, 2606:4700::6812:ed8
Info::
2 nameserver(s) configured
Got: roxy.ns.cloudflare.com, sonny.ns.cloudflare.com
Info::
6 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: 9 ms
Got: 9 ms
A104.18.14.216, 104.18.15.216
AAAA2606:4700::6812:fd8, 2606:4700::6812:ed8
CNAME
NSroxy.ns.cloudflare.com, sonny.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
10 aspmx4.googlemail.com
TXT
_globalsign-domain-verification=SQONiBgTxRVzPPtIHjei_IUGCiAa0KxoVWFw1QfVes
ca3-011b6f7c4d1b4d3390a032f871be95e6
ca3-587af32f402843edac412a24b504d818
facebook-domain-verification=nhgmd6j21i84hnwue5xijmtruo870z
globalsign-domain-verification=KaParXxs1OHDy7o8CMbPpHBN-2m_mzwdPqKMMQ66a6
google-site-verification=CdWx3rweJY_4ZzY6LLDfZ1DrYwVgLzhtvy4KLS5us7Y
google-site-verification=R06TbkbxAmmAxtBJ36J87VhSZaiA4bRq2Nej2M0FYF8
tollbit-domain-verification=0d2cdadbb8cf64f90c9f941e328c2740a0f3318196d4d412257f...
SPF v=spf1 include:aspmx.sailthru.com include:_spf.google.com include:amazonses.com ...
CAALookup not available with standard resolver
Resolved in 9 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+
Crawlability
robots.txt present, sitemap with 4 URLs
PASS
robots.txt present, sitemap with 4 URLs
Info::
robots.txt is present
Got: 4482 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 4 entries
Info::
Sitemap index with 4 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 4482 B Sitemaps referenced 24 User-agents FriendlyCrawler, DuckDuckBot, DuckAssistBot, Google-CloudVertexBot, ImagesiftBot, magpie-crawler, peer39_crawler, YouBot, Googlebot, PerplexityBot, AwarioRssBot, CCBot, ia_archiver, Scrapy, web-archive-net.com.bot, *, Slurp, cohere-training-data-crawler, meta-externalfetcher, news-please, Claude-Web, archive.org_bot, DataForSeoBot, Diffbot, FacebookBot, peer39_crawler/1.0, Bingbot, anthropic-ai, Bytespider, ClaudeBot, cohere-ai, europarchive.org, heritrix, omgili, AmazonAdBot, Arquivo-web-crawler, AwarioSmartBot, Meta-ExternalAgent, Nicecrawler, Timpibot, TurnitinBot, GPTBot, OAI-SearchBot, ChatGPT-User, Applebot-Extended, Meta-ExternalFetcher, Amazonbot, ia_archiver-web.archive.org, LinkArchiver, meta-externalagent, omgilibot, Primalbot, Quora-Bot, Google-Extended Blocking No — crawling allowed
# The Sporting News is made available for your personal, non-commercial use subject to our Terms of Service:

# https://sportingnewsholdings.com/policies/terms-of-use/

# Use of any automated system of software, including use of any artificial intelligence or machine learning tool, model, system, algorithm, product or other technology which is intended or designed to gather or extract any data from The Sporting News website is strictly prohibited.


User-agent: *

Disallow: /api

Disallow: /api/url

Disallow: /api/url/article?uuid=*

Disallow: /px/

Disallow: /user

Disallow: /user/

Disallow: /service

Disallow: /service/

Disallow: /test/

Disallow: /nba-service/

Disallow: /module/nba-live-test

Disallow: /fantasy/player-updates?page=*

Disallow: /?page=*

Disallow: /zephr/*

Disallow: /blaize/*

User-agent: Googlebot 

User-agent: Bingbot 

User-agent: Slurp

User-agent: DuckDuckBot 

Allow: /


User-agent: OAI-SearchBot

Allow: /


User-agent: PerplexityBot

Allow: /


User-agent: ChatGPT-User

Allow: /


User-agent: Claude-Web

Allow: /


User-agent: AmazonAdBot

Allow: /


#Other disallow rules

User-agent: Amazonbot

Disallow: /


User-agent: anthropic-ai

Disallow: /


User-agent: Applebot-Extended

Disallow: /


User-agent: archive.org_bot

Disallow: /


User-agent: Arquivo-web-crawler

Disallow: /


User-agent: AwarioRssBot

Disallow: /


User-agent: AwarioSmartBot

Disallow: /


User-agent: Bytespider

Disallow: /


User-agent: CCBot

Disallow: /


User-agent: ClaudeBot

Disallow: /


User-agent: cohere-ai

Disallow: /


User-agent: cohere-training-data-crawler

Disallow: /


User-agent: DataForSeoBot

Disallow: /


User-agent: Diffbot

Disallow: /


User-agent: DuckAssistBot

Disallow: /


User-agent: europarchive.org

Disallow: /


User-agent: FacebookBot

Disallow: /


User-agent: FriendlyCrawler

Disallow: /


User-agent: Google-CloudVertexBot

Disallow: /


User-agent: heritrix

Disallow: /


User-agent: ia_archiver

Disallow: /


User-agent: ia_archiver-web.archive.org

Disallow: /


User-agent: ImagesiftBot

Disallow: /


User-agent: LinkArchiver

Disallow: /


User-agent: magpie-crawler

Disallow: /


User-agent: Meta-ExternalAgent

User-agent: meta-externalagent

Disallow: /


User-agent: Meta-ExternalFetcher

User-agent: meta-externalfetcher

Disallow: /


User-agent: news-please

Disallow: /


User-agent: Nicecrawler

Disallow: /


User-agent: omgili

Disallow: /


User-agent: omgilibot

Disallow: /


User-agent: peer39_crawler

User-agent: peer39_crawler/1.0

Disallow: /


User-agent: Primalbot

Disallow: /


User-agent: Quora-Bot

Disallow: /


User-agent: Scrapy

Disallow: /


User-agent: Timpibot

Disallow: /


User-agent: TurnitinBot

Disallow: /


User-agent: web-archive-net.com.bot

Disallow: /


User-agent: YouBot

Disallow: /


User-agent: GPTBot

Disallow: /


User-agent: Google-Extended

Disallow: /


User-agent: FacebookBot

Disallow: /


User-agent: Meta-ExternalAgent

User-agent: meta-externalagent

User-agent: Meta-ExternalFetcher

User-agent: meta-externalfetcher

Disallow: /

# sitemaps

Sitemap: https://www.sportingnews.com/mx/sitemap.xml
Sitemap: https://www.sportingnews.com/mx/news-sitemap.xml

Sitemap: https://www.sportingnews.com/us-es/sitemap.xml
Sitemap: https://www.sportingnews.com/us-es/news-sitemap.xml

Sitemap: https://www.sportingnews.com/br/sitemap.xml
Sitemap: https://www.sportingnews.com/br/news-sitemap.xml

Sitemap: https://www.sportingnews.com/th/sitemap.xml
Sitemap: https://www.sportingnews.com/th/news-sitemap.xml

Sitemap: https://www.sportingnews.com/in/sitemap.xml
Sitemap: https://www.sportingnews.com/in/news-sitemap.xml

Sitemap: https://www.sportingnews.com/jp/sitemap.xml
Sitemap: https://www.sportingnews.com/jp/news-sitemap.xml

Sitemap: https://www.sportingnews.com/es/sitemap.xml
Sitemap: https://www.sportingnews.com/es/news-sitemap.xml

Sitemap: https://www.sportingnews.com/ar/sitemap.xml
Sitemap: https://www.sportingnews.com/ar/news-sitemap.xml

Sitemap: https://www.sportingnews.com/us/sitemap.xml
Sitemap: https://www.sportingnews.com/us/news-sitemap.xml

Sitemap: https://www.sportingnews.com/ca/sitemap.xml
Sitemap: https://www.sportingnews.com/ca/news-sitemap.xml

Sitemap: https://www.sportingnews.com/au/sitemap.xml
Sitemap: https://www.sportingnews.com/au/news-sitemap.xml

Sitemap: https://www.sportingnews.com/uk/sitemap.xml
Sitemap: https://www.sportingnews.com/uk/news-sitemap.xml


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.sportingnews.com/
200https://sportingnews.com/

Preferred variant: non-www

HTTP → HTTPS

301http://sportingnews.com/ https://www.sportingnews.com/

Consistent

A+
Domain Intelligence
sportingnews.com — via SafeNames Ltd., 30 years, 10 months old, hosted on Cloudflare
PASS
sportingnews.com — via SafeNames Ltd., 30 years, 10 months old, hosted on Cloudflare
Info::
Domain registered until Nov 21, 2026 (7 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: SafeNames Ltd.
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: Cloudflare
Got: AS13335
Domain expiry

158 days

November 21, 2026

SSL certificate

67 days

Issued by Google Trust Services

Domain age

30 years, 10 months

Registered November 22, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.15.216

Registrar

SafeNames Ltd.

Unlocked 2 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 SafeNames Ltd.
Created November 22, 1995 (30 years, 10 months ago)
Expires November 21, 2026 (7 months)
Last Updated December 1, 2024
Name Servers roxy.ns.cloudflare.com, sonny.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.18.15.216
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 32 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
32 ms
Total Time Total request time from DNS lookup through full response.
32 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 3 ms TLS Handshake 10 ms Server Processing 10 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