Skip to content
https://www.lego.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
1 redirect(s), 1753 ms total
REVIEW
1 redirect(s), 1753 ms total
Info::
Single redirect
Got: https://www.lego.com → https://www.lego.com/en-es (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.lego.com
Warning::
Redirect overhead: 1753 ms total
Got: 1753 ms

https://www.lego.com

135 ms · HTTP/1.1

302

https://www.lego.com/en-es

1618 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.lego.com302135 msHTTP/1.1cloudflare
2https://www.lego.com/en-es2001618 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8b99343e840498-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8b99343e840498-CDG
A+
DNS Records
2 A records, 48 ms lookup
PASS
2 A records, 48 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.8.208, 104.18.9.208
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:8d0, 2606:4700::6812:9d0
Info::
2 nameserver(s) configured
Got: evelyn.ns.cloudflare.com, harley.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 48 ms
Got: 48 ms
A104.18.8.208, 104.18.9.208
AAAA2606:4700::6812:8d0, 2606:4700::6812:9d0
CNAME—
NSevelyn.ns.cloudflare.com, harley.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 48 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:8d0, 2606:4700::6812:9d0
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:8d0, 2606:4700::6812:9d0 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 17 URLs
PASS
robots.txt present, sitemap with 17 URLs
Info::
robots.txt is present
Got: 786 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 17 entries
Info::
Sitemap index with 17 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 786 B Sitemaps referenced 6 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /identity/
Disallow: /cart
Disallow: /checkout
Disallow: /account/wishlist
Disallow: /innovation-intake-ideas
Disallow: /innovation-intake-editor
Disallow: /insiders/event/
Disallow: /kids/search?q=
Disallow: /scan/
Disallow: /in-store/
Disallow: /member/
Disallow: /reward/
Disallow: /*?icmp=
Disallow: /*?consent-modal=show
Disallow: /*&consent-modal=show
Disallow: /*/galleries/
Disallow: /careers/
Disallow: /careers/stories*


# List of Sitemap Files
Sitemap: https://www.lego.com/sitemap.xml
Sitemap: https://www.lego.com/aboutus/sitemap.xml
Sitemap: https://www.lego.com/legal/sitemap.xml
Sitemap: https://www.lego.com/local-news/sitemap.xml
Sitemap: https://www.lego.com/service/sitemapindex.xml
Sitemap: https://www.lego.com/sustainability/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 17 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.lego.com/
301https://lego.com/

Preferred variant: www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
lego.com — via CSC Corporate Domains, Inc., 31 years old
PASS
lego.com — via CSC Corporate Domains, Inc., 31 years old
Info::
Domain registered until Aug 21, 2026 (4 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: CSC Corporate Domains, Inc.
Domain expiry

40 days

August 21, 2026

SSL certificate

40 days

Issued by Google Trust Services

Domain age

31 years

Registered August 22, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:28fd:3000:7:a59e:e6c0:93a1

Registrar

CSC Corporate Domains, Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar CSC Corporate Domains, Inc.
Created August 22, 1995 (31 years ago)
Expires August 21, 2026 (4 months)
Last Updated August 17, 2025
Name Servers cory.ns.cloudflare.com, sara.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2600:9000:28fd:3000:7:a59e:e6c0:93a1
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

A+
HTTP Probe Timing
Total 97 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
21 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
97 ms
Total Time Total request time from DNS lookup through full response.
97 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 16 ms TLS Handshake 21 ms Server Processing 30 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