lego.com — domain analysis
lego.com blocks automated analysis, answering with Cloudflare interstitial instead of its homepage. Its certificate, DNS and registration records are still readable and are reported below.
This site blocks automated analysis.
It answered our request with Cloudflare interstitial rather than its
homepage, so nothing below is derived from its actual content — doing so would describe
the bot wall, not the site. The certificate and robots.txt data are still accurate,
because those are served to everyone.
How does lego.com compare with other domains analysed here?
Measured against the 83 domains in this index. This is a
small, self-selected sample — the domains people happened to look up — not a
representative sample of the web.
| Response time | Faster than 88% of them (median 438ms) |
|---|---|
| Domain age | Older than 88% of them |
Related domains in this index
Analysed domains sharing the same network (AS16509 Amazon.com, Inc.):
Sharing a network means sharing a host or CDN. It implies nothing about a
relationship between the sites themselves.
When was lego.com registered?
lego.com was registered on 22 August 1995, which makes it about 31 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is CSC Corporate Domains, Inc..
Registration runs until 21 August 2027.
The domain carries 4 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 22 August 1995 |
|---|---|
| Expires | 21 August 2027 |
| Registrar | CSC Corporate Domains, Inc. |
| Registry status | client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
Where is lego.com hosted?
The first address resolves to infrastructure in Paris, France.
The network is operated by AWS CloudFront (GLOBAL) (AS16509 Amazon.com, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is lego.com running on?
No platform, framework or analytics fingerprints were found in the homepage markup of lego.com. That usually means hand-written HTML, an uncommon stack, or a page assembled entirely at the edge.
No recognisable platform, framework or analytics fingerprints were found in the homepage markup.
How does the homepage respond?
The server answered with HTTP 403 over
HTTPS.
At 118ms to first byte this response is fast for a homepage measured from a single European location.
At 6KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 5,659 bytes |
| Declared language | not declared |
| Mobile viewport | not declared |
What does the homepage say about itself?
The homepage has no title element at all, which leaves search engines to invent one from the page content.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
No H1 heading was found, so the page offers no single top-level statement of what it is.
No viewport meta tag is declared, so mobile browsers will render the page at desktop width and scale it down.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | — none — (0 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | — none — (0 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 0 images (0 without alt text) |
Is lego.com served over a valid certificate?
The HTTPS certificate is issued by Amazon and is
valid until 2027-02-26, which is 144 days from the date of this check. It covers
1 hostname.
- lego.com
The certificate has 144 days left to run.
It covers 1 hostname, so it was issued for this site specifically.
Which security headers does it set?
None of the 6 headers checked are set. That is the default state of most servers rather than evidence of a problem, but it means the browser is given no instructions it could otherwise act on.
| Header | Set | Value |
|---|
How is DNS configured for lego.com?
| IP addresses | 52.222.169.50, 52.222.169.66, 52.222.169.84, 52.222.169.22, 2600:9000:218f:9a00:7:a59e:e6c0:93a1, 2600:9000:218f:ca00:7:a59e:e6c0:93a1, 2600:9000:218f:ae00:7:a59e:e6c0:93a1, 2600:9000:218f:8800:7:a59e:e6c0:93a1, 2600:9000:218f:b200:7:a59e:e6c0:93a1, 2600:9000:218f:7200:7:a59e:e6c0:93a1, 2600:9000:218f:7c00:7:a59e:e6c0:93a1, 2600:9000:218f:9c00:7:a59e:e6c0:93a1 |
|---|---|
| Reverse DNS | server-52-222-169-50.cdg52.r.cloudfront.net, server-52-222-169-66.cdg52.r.cloudfront.net |
| Name servers | sara.ns.cloudflare.com, cory.ns.cloudflare.com |
| Mail (MX) | lego-com.mail.protection.outlook.com (pri 10) |
| SPF | v=spf1 include:spf.corp.lego.com include:spf.protection.outlook.com include:dpdhl._spf.dhl.com -all |
| TXT records | 47 |
lego.com resolves to 12 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 1 exchanger.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to server-52-222-169-50.cdg52.r.cloudfront.net, server-52-222-169-66.cdg52.r.cloudfront.net, which usually names the hosting provider.
Can lego.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 6 named authorities (iodef mailto:[email protected], issue amazon.com, issue amazonaws.com, issue amazontrust.com), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What does robots.txt allow?
robots.txt is 784 bytes and names
1 user-agent group.
It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.lego.com/sitemap.xml
- https://www.lego.com/aboutus/sitemap.xml
- https://www.lego.com/legal/sitemap.xml
- https://www.lego.com/local-news/sitemap.xml
- https://www.lego.com/service/sitemapindex.xml
- https://www.lego.com/sustainability/sitemap.xml
AI crawler policy
robots.txt names no AI crawlers specifically, so they fall under whatever rule
applies to User-agent: *.
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
Frequently asked questions
Does lego.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
Where does this data come from?
Every figure was measured by our own server on 5 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own lego.com and want this page removed.
Ask through the contact page on this site, from an address at the domain, and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 5 October 2026.
Analyse another domain →
Note: CamoCrypt is security & education only — no prices, no predictions, no investment advice. Verify every address and contract yourself; we cannot recover lost funds and neither can anyone who contacts you claiming they can.