Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1093 ms totalFIX
https://leagueoflegends.com
702 ms · HTTP/1.1
https://www.leagueoflegends.com/
192 ms · HTTP/1.1
https://www.leagueoflegends.com/fr-fr/
199 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://leagueoflegends.com | 301 | 702 ms | HTTP/1.1 | nginx |
| 2 | https://www.leagueoflegends.com/ | 307 | 192 ms | HTTP/1.1 | Netlify |
| 3 | https://www.leagueoflegends.com/fr-fr/ | 200 | 199 ms | HTTP/1.1 | Netlify |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations158 days until leaf cert expires — 6 issues to addressREVIEW
Certificate validity
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 Records2 A records, 50 ms lookupPASS
| A | 34.218.186.158, 184.34.154.65 |
| AAAA | — |
| CNAME | — |
| NS | ns-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 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 25 URLsPASS
User-agent: *
Allow: /
Sitemap: https://www.leagueoflegends.com/sitemap_index.xml
- https://www.leagueoflegends.com/ar-ae/si...
- https://www.leagueoflegends.com/cs-cz/si...
- https://www.leagueoflegends.com/de-de/si...
- https://www.leagueoflegends.com/el-gr/si...
- https://www.leagueoflegends.com/en-au/si...
- https://www.leagueoflegends.com/en-gb/si...
- https://www.leagueoflegends.com/en-us/si...
- https://www.leagueoflegends.com/es-es/si...
- https://www.leagueoflegends.com/es-mx/si...
- https://www.leagueoflegends.com/fr-fr/si...
- https://www.leagueoflegends.com/hu-hu/si...
- https://www.leagueoflegends.com/id-id/si...
- https://www.leagueoflegends.com/it-it/si...
- https://www.leagueoflegends.com/ja-jp/si...
- https://www.leagueoflegends.com/ko-kr/si...
- https://www.leagueoflegends.com/pl-pl/si...
- https://www.leagueoflegends.com/pt-br/si...
- https://www.leagueoflegends.com/ro-ro/si...
- https://www.leagueoflegends.com/ru-ru/si...
- https://www.leagueoflegends.com/tr-tr/si...
- https://www.leagueoflegends.com/en-sg/si...
- https://www.leagueoflegends.com/en-ph/si...
- https://www.leagueoflegends.com/zh-tw/si...
- https://www.leagueoflegends.com/vi-vn/si...
- https://www.leagueoflegends.com/th-th/si...
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceleagueoflegends.com — via MarkMonitor Inc., 18 years, 10 months old, hosted on AWSPASS
102 days
September 25, 2026
158 days
Issued by Amazon
18 years, 10 months
Registered September 25, 2007
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
184.34.154.65
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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