Skip to content
https://leagueoflegends.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1093 ms total
FIX
2 redirect(s), 1093 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
Warning::
Redirect overhead: 1093 ms total
Got: 1093 ms

https://leagueoflegends.com

702 ms · HTTP/1.1

301

https://www.leagueoflegends.com/

192 ms · HTTP/1.1

307

https://www.leagueoflegends.com/fr-fr/

199 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://leagueoflegends.com301702 msHTTP/1.1nginx
2https://www.leagueoflegends.com/307192 msHTTP/1.1Netlify
3https://www.leagueoflegends.com/fr-fr/200199 msHTTP/1.1Netlify

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

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
TLS Certificate Expiry & Recommendations
158 days until leaf cert expires — 6 issues to address
REVIEW

Certificate validity

158
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
  • 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, 50 ms lookup
PASS
2 A records, 50 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 34.218.186.158, 184.34.154.65
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1095.awsdns-08.org, ns-1809.awsdns-34.co.uk, ns-212.awsdns-26.com, ns-981.awsdns-58.net
Info::
1 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: 50 ms
Got: 50 ms
A34.218.186.158, 184.34.154.65
AAAA
CNAME
NSns-1095.awsdns-08.org, ns-1809.awsdns-34.co.uk, ns-212.awsdns-26.com, ns-981.awsdns-58.net
MX
10 mail.leagueoflegends.com
TXT
identrust_validate=xViY8YWL74HrtP32ySxitM6QRtkTeirukXmq5F2nGQoC
427333941-1774687
_wcvc62y0ad5lsgk6nv6hgdngohmvsdm
identrust_validate=0GDKfXIxNOBIkY/PZBoFLs70B8m/X2VIChxluubiasYR
google-site-verification=1JtcELUXxKA8Tbb-xxubkrboE4nFH_0Ags0CwThfPKU
google-site-verification=akXT1mkSUfEsiJL6t39NdDiR49juoVTxruux6-yBo8A
globalsign-domain-verification=3Fl4Eqj_V08XH5MZb8lPUQ4LiuWJf4kLzrGscuVilP
ca3-fa7272b37fd84df9b6e46aa444f2f84f
SPF v=spf1 ip4:66.151.63.180 ip4:69.72.136.135 ~all
s88whxgwwqjy2bs2t0b5zbryr1wnvvbn
facebook-domain-verification=zc5uxywe72iwcr8n8bhzhchzeab2iy
CAALookup not available with standard resolver
Resolved in 50 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 25 URLs
PASS
robots.txt present, sitemap with 25 URLs
Info::
robots.txt is present
Got: 84 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 25 entries
Info::
Sitemap index with 25 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 84 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://www.leagueoflegends.com/sitemap_index.xml
 
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

307https://www.leagueoflegends.com/
200https://leagueoflegends.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
leagueoflegends.com — via MarkMonitor Inc., 18 years, 10 months old, hosted on AWS
PASS
leagueoflegends.com — via MarkMonitor Inc., 18 years, 10 months old, hosted on AWS
Info::
Domain registered until Sep 25, 2026 (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: 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

101 days

September 25, 2026

SSL certificate

158 days

Issued by Amazon

Domain age

18 years, 10 months

Registered September 25, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

184.34.154.65

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 September 25, 2007 (18 years, 10 months ago)
Expires September 25, 2026 (5 months)
Last Updated August 24, 2025
Name Servers ns-1095.awsdns-08.org, ns-1809.awsdns-34.co.uk, ns-212.awsdns-26.com, ns-981.awsdns-58.net
DNSSEC Not enabled
Hosting
IP Address 184.34.154.65
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 745 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
174 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
350 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
745 ms
Total Time Total request time from DNS lookup through full response.
745 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 174 ms TLS Handshake 350 ms Server Processing 175 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