Skip to content
https://si.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 4 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
1 redirect(s), 1505 ms total
REVIEW
1 redirect(s), 1505 ms total
Info::
Single redirect
Got: https://si.com → https://www.si.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1505 ms total
Got: 1505 ms

https://si.com

479 ms · HTTP/1.1

301

https://www.si.com/

1026 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://si.com301479 msHTTP/1.1redirector-service
2https://www.si.com/2001026 msHTTP/1.1CloudFront

See the visual redirect chain in the HTTP Probe tab →

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://si.com/ → https://www.si.com/

Consistent

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

Certificate validity

47
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
A+
DNS Records
2 A records, 12 ms lookup
PASS
2 A records, 12 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 35.83.190.225, 44.241.188.24
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1157.awsdns-16.org, ns-1819.awsdns-35.co.uk, ns-474.awsdns-59.com, ns-741.awsdns-28.net
Info::
5 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: 12 ms
Got: 12 ms
A35.83.190.225, 44.241.188.24
AAAA—
CNAME—
NSns-1157.awsdns-16.org, ns-1819.awsdns-35.co.uk, ns-474.awsdns-59.com, ns-741.awsdns-28.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
26C1DCCA46
MS=ms22369655
MS=ms80782080
MS=ms93495782
T0I0M34279
_globalsign-domain-verification=m2caqrJ1kIVyqQ3xPGWo5qP93lYtTkKA0Xyz-eQIA-
airtable-verification=cc7c4ecba9339dd98d28575a1f939dc6
apple-domain-verification=rGtFLx1dBQPK35RZ
atlassian-domain-verification=49CoabLOiRcDOq7aYk5YiRo9mbmOMsuyotiNaBC0Z7Id5yRBgw...
d3bmdi80xb3jem.cloudfront.net
docusign=1037b789-2196-4c77-809c-66b8c6836a02
docusign=550d3e50-7b29-4e9b-8edb-272c801fb362
facebook-domain-verification=yyyv3w5rx5pkpu6j4b5mvsqmknfwck
google-gws-recovery-domain-verification=50323461
google-site-verification=JM0HYeXMzwZJ1PpC42J2vgYeE-NR_zreDuTMeJmNtPA
google-site-verification=K71xxdZMmsclZj94rwAHN4-KqN7-71w4TCxWjEpIDOI
google-site-verification=NXI0vQYm-vJsY1tnINxz2Q9dYSVlNUTfOW1R1igowpE
google-site-verification=WlbkowvStwyJiUSuqTdyEA7-DFv5aEdzBZAJX2lIHHc
google-site-verification=bUpqwbXU00vHWLNGYM-SzjHLYHFpZISN0nd8a_iaql8
google-site-verification=plyb-kJaEvatag0omktSRttmhBXb5evQhfH6tSkd6Yk
have-i-been-pwned-verification=517958ff82c3dcfa6b56d3c48af22b50
knowbe4-site-verification=6e8bc2272a23f6b229a16d1d421f11af
lAipka1cQ8WGr8k1FL9n7R4EV5UM2nrExypMNU7Squm/OkzjwHKtd7BRjv1gMOjcHt0l9IIEhu0vYfQb...
openai-domain-verification=dv-UBEyjIcV7fUyu6L23fw2HGci
SPF v=spf1 include:aspmx.sailthru.com include:_spf.google.com ~all
yahoo-verification-key=3WCMllI0l93vs//RVwfdUD+IJ5X32ca7hi50mYH+7yg=
yahoo-verification-key=VQrrIOsxWaqgo1rt85rk6qCXy5OHiXXdAONFzJYIHW0=
CAALookup not available with standard resolver
Resolved in 12 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 1000 URLs
PASS
robots.txt present, sitemap with 1000 URLs
Info::
robots.txt is present
Got: 1599 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1000 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1599 B Sitemaps referenced 3 User-agents *, ChatGPT-User, ClaudeBot, Claude-Web, Google-Extended, GPTBot, OAI-SearchBot, PerplexityBot Blocking No — crawling allowed
# Allow all search engines to crawl
User-agent: *
Allow: /

# AI Crawlers
User-agent: GPTBot
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: Claude-Web
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Google-Extended
Allow: /

# Allow crawling ads
User-agent: *
allow: /ads.txt

# Embedded widget parameters
User-agent: *
Disallow: *?embed*

# Influencers/Affiliate Links parameters
User-agent: *
Disallow: */*a_aid=*
Disallow: /*?partner=*

# Experiments testing team
User-agent: *
Disallow: */*?mm-experiments=*

# Search box param
User-agent: *
Disallow: /*?*s=*

# Apps param
User-agent: *
Disallow: *?app=*

# FB campaigns
User-agent: *
Disallow: *?fbclid=*

# GEO targeting:
User-agent: *
Disallow: /*?setLocale=*
Disallow: *?georedirect=*

# Unknown Parameters
User-agent: *
Disallow: /*?term=*
Disallow: *?ref=*
Disallow: /*?view_source=*
Disallow: /*?view_medium=*
Disallow: /*?initialLeagueId=*

# GA parameters - Generated from Google caching
User-agent: *
Disallow: *_ga_*
Disallow: */?_gl=*

# Generated from Voltax API url
User-agent: *
Disallow: */api/*

# Voltax HTML Unknown crawled urls
User-agent: *
Disallow: */videos/undefinedc_fill,w_360,ar_16:9,f_auto,q_auto,g_auto/undefined
Disallow: */teams/mainNavigationChevron_icon.svg?*
Disallow: */leagues/mainNavigationChevron_icon.svg?*
Disallow: */undefinedc_fill,w_360,ar_16:9,f_auto,q_auto,g_auto/undefined

#Sitemap XML
Sitemap: https://www.si.com/news-sitemap.xml
Sitemap: https://www.si.com/sitemap.xml
Sitemap: https://www.si.com/feed-sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 1000 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
si.com — via MarkMonitor Inc., 36 years, 3 months old, hosted on AWS
PASS
si.com — via MarkMonitor Inc., 36 years, 3 months old, hosted on AWS
Info::
Domain registered until Jul 5, 2027 (1 years, 2 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

358 days

July 5, 2027

SSL certificate

47 days

Issued by Let's Encrypt

Domain age

36 years, 3 months

Registered July 6, 1990

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.83.190.225

Registrar

MarkMonitor Inc.

Unlocked 4 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 July 6, 1990 (36 years, 3 months ago)
Expires July 5, 2027 (1 years, 2 months)
Last Updated June 3, 2025
Name Servers ns-1157.awsdns-16.org, ns-1819.awsdns-35.co.uk, ns-474.awsdns-59.com, ns-741.awsdns-28.net
DNSSEC Not enabled
Hosting
IP Address 35.83.190.225
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 157 ms TLS Handshake 160 ms Server Processing 157 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