Skip to content
https://sportskeeda.com

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 Amsterdam, Netherlands
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.

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

211
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
  • 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, 6 ms lookup
PASS
2 A records, 6 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 54.151.190.144, 18.141.21.34
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1139.awsdns-14.org, ns-2005.awsdns-58.co.uk, ns-205.awsdns-25.com, ns-826.awsdns-39.net
Info::
7 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: 6 ms
Got: 6 ms
A54.151.190.144, 18.141.21.34
AAAA
CNAME
NSns-1139.awsdns-14.org, ns-2005.awsdns-58.co.uk, ns-205.awsdns-25.com, ns-826.awsdns-39.net
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
30 aspmx5.googlemail.com
30 aspmx4.googlemail.com
TXT
ahrefs-site-verification_0627f0e0d1680b14723f8f512e1dc4984ad569ad0da7862d1408574...
atlassian-domain-verification=gh3aLR/RasHpT/DBB9WrlCxfOLSGsGBIaWX3ynUOi1v1OVAKmK...
ca3-6b9b5bb714564c4ebdc67a0f54238d79
detectify-verification=5e0c9477e04673a352ab9a57a530634b
google-site-verification=4gC-ogMgh8yD3-s1amL7Mqk8U25gpKy1X3MAVt0HCoA
google-site-verification=5N5YyaIzynu432Je4SkbyXOd1iYd0O12aN24aLayocg
google-site-verification=9kMv43QEjIEImvoD7XN_npVlAWLUyzV8XUjsQ3gf_wI
google-site-verification=Jel_Y9o4Arxf-ncksHT6W4nwDdSDGjXr3qUx2JPUKRc
google-site-verification=aYp16-BqpLl2Mxe5UVj3FZqLzXJ86jAURUFdyfhDt4M
google-site-verification=jg9DYZEO1aUN67jLsNHs-Gr6oBlSgycSVrEpTJcFD9o
google-site-verification=pu1esVEx8KjhujCEvS4vT1LxGp-1ffJ6H8GjgBdPMP4
google-site-verification=r5mg92vszlR7oPyQdBM7WtAxb0wxgUM1hxAi1olgdIg
pinterest-site-verification=10e458c7ef60579ffd779feee6dbe620
SPF v=spf1 include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 6 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
Redirect Chain
1 redirect(s), 825 ms total
PASS
1 redirect(s), 825 ms total
Info::
Single redirect
Got: https://sportskeeda.com → https://www.sportskeeda.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 825 ms total
Got: 825 ms

https://sportskeeda.com

633 ms · HTTP/1.1

301

https://www.sportskeeda.com/

191 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sportskeeda.com301633 msHTTP/1.1nginx
2https://www.sportskeeda.com/403191 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.sportskeeda.com/
200https://sportskeeda.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
sportskeeda.com — via GoDaddy.com, LLC, 16 years, 11 months old, hosted on AWS
PASS
sportskeeda.com — via GoDaddy.com, LLC, 16 years, 11 months old, hosted on AWS
Info::
Domain registered until Aug 17, 2035 (9 years, 5 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: GoDaddy.com, 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: AWS
Got: AS16509
Domain expiry

3352 days

August 17, 2035

SSL certificate

211 days

Issued by Amazon

Domain age

16 years, 11 months

Registered August 17, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.151.190.144

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created August 17, 2009 (16 years, 11 months ago)
Expires August 17, 2035 (9 years, 5 months)
Last Updated August 29, 2025
Name Servers ns-1139.awsdns-14.org, ns-2005.awsdns-58.co.uk, ns-205.awsdns-25.com, ns-826.awsdns-39.net
DNSSEC Not enabled
Hosting
IP Address 54.151.190.144
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 636 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
158 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
316 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
636 ms
Total Time Total request time from DNS lookup through full response.
636 ms

Connection waterfall

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