Skip to content
https://foxsports.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.foxsports.com/
200https://foxsports.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 37 ms lookup
PASS
1 A records, 37 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.220.112.240
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns04.dns.fox, ns02.foxdoua.com, ns02.dns.fox, ns03.dns.fox, ns01.dns.fox, ns04.foxdoua.com, ns01.foxdoua.com, ns03.foxdoua.com
Info::
2 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: 37 ms
Got: 37 ms
A23.220.112.240
AAAA—
CNAME—
NSns04.dns.fox, ns02.foxdoua.com, ns02.dns.fox, ns03.dns.fox, ns01.dns.fox, ns04.foxdoua.com, ns01.foxdoua.com, ns03.foxdoua.com
MX
10 mxa-00195501.gslb.pphosted.com
10 mxb-00195501.gslb.pphosted.com
TXT
google-site-verification=oaNvZcLjLxhKWK5NRyXAF1o98RCaLIT01HNMbxUY21ggoogle-site-...
SPF v=spf1 mx a:mail.foxsports.com include:spf-00195501.pphosted.com -all
airtable-verification=2ad0b6c3b5e5222653e94ed5623f69a5
MS=ms77124483
facebook-domain-verification=wylijrao17zgcrqldcvvm98spja5q0
adobe-idp-site-verification=10f6011913207e944a026129f59881b0cb1078801a8c11229c6e...
postman-domain-verification=a70a812194f28ec0194827f913fb2779c7e9683a23953aad5a5d...
MS=ms58172965
CAALookup not available with standard resolver
Resolved in 37 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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
Redirect Chain
1 redirect(s), 187 ms total
PASS
1 redirect(s), 187 ms total
Info::
Single redirect
Got: https://foxsports.com → https://www.foxsports.com/ (301)
Info::
WWW normalization redirect

https://foxsports.com

130 ms · HTTP/1.1

301

https://www.foxsports.com/

57 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://foxsports.com301130 msHTTP/1.1AkamaiGHost
2https://www.foxsports.com/20057 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 428 URLs
PASS
robots.txt present, sitemap with 428 URLs
Info::
robots.txt is present
Got: 183 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 428 entries
Info::
Sitemap index with 428 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 183 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /maintenance/

Disallow: /foxbox/

Disallow: /xid


Sitemap: https://www.foxsports.com/sitemap.xml

Sitemap: https://www.foxsports.com/sitemap.xml?type=news
sitemap.xml 200 OK
Type Sitemap Index URLs 428 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
foxsports.com — via GoDaddy Corporate Domains, LLC, 28 years, 1 months old, hosted on Akamai
PASS
foxsports.com — via GoDaddy Corporate Domains, LLC, 28 years, 1 months old, hosted on Akamai
Info::
Domain registered until Aug 9, 2027 (1 years, 3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: GoDaddy Corporate Domains, LLC
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: Akamai
Got: AS16625
Domain expiry

419 days

August 9, 2027

SSL certificate

122 days

Issued by DigiCert Inc

Domain age

28 years, 1 months

Registered August 10, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.220.112.240

Registrar

GoDaddy Corporate Domains, LLC

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy Corporate Domains, LLC
Created August 10, 1998 (28 years, 1 months ago)
Expires August 9, 2027 (1 years, 3 months)
Last Updated September 20, 2022
Name Servers ns01.dns.fox, ns01.foxdoua.com, ns02.dns.fox, ns02.foxdoua.com, ns03.dns.fox, ns03.foxdoua.com, ns04.dns.fox, ns04.foxdoua.com
DNSSEC Enabled
Hosting
IP Address 23.220.112.240
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 41 ms TCP Connect 30 ms TLS Handshake 62 ms Server Processing 36 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