lwworks.com is a live website built on Squarespace, registered in 2024, served from New York, United States. It has a valid HTTPS certificate, 3 of 6 common security headers.
What is lwworks.com about?
The words appearing most often on the homepage, excluding common filler, are
a rough indication of subject matter rather than a description of the business:
- soon ×2
Does lwworks.com publish the usual trust pages?
All four of the pages a established business normally publishes were found:
about, contact, privacy and terms.
These were checked at conventional paths only, so a site using different URLs may
publish them elsewhere.
How does lwworks.com compare with other domains analysed here?
Measured against the 74 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 64% of them (median 463ms) |
|---|---|
| Security headers | More than 72% of them |
| Domain age | Older than 14% of them |
Related domains in this index
Other analysed domains served from the same country:
When was lwworks.com registered?
lwworks.com was registered on 13 December 2024, which makes it about 1 year old.
The registrar of record is Squarespace Domains LLC.
Registration runs until 13 December 2027.
The domain carries 2 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 13 December 2024 |
|---|---|
| Expires | 13 December 2027 |
| Registrar | Squarespace Domains LLC |
| Registry status | client delete prohibited, client transfer prohibited |
Where is lwworks.com hosted?
The first address resolves to infrastructure in New York, United States.
The network is operated by Squarespace, Inc. (AS53831 Squarespace, 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 lwworks.com running on?
lwworks.com exposes 1 identifiable technology: Squarespace.
- Squarespace
How does the homepage respond?
The server answered with HTTP 200 over
HTTPS.
At 335ms to first byte this response is unremarkable for a homepage measured from a single European location.
At 3KB the HTML is unusually small, which typically means the page builds itself client-side after load.
The HTML is compressed with gzip.
| Server header | Squarespace |
|---|---|
| Compression | gzip |
| Page size | 2,997 bytes |
| Declared language | not declared |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is only 11 characters, which is short enough that it probably is not describing the page so much as naming it.
There is no meta description, so the snippet shown in search results is assembled by the search engine from whatever text it considers relevant.
1 of 2 images carry no alt attribute, which leaves them unreadable to screen readers and uninterpretable to image search.
The html element declares no lang attribute, which removes a signal both screen readers and translation tools rely on.
| Title | Coming Soon (11 chars) |
|---|---|
| Meta description | — none — (0 chars) |
| H1 | lwworks.com (1 on the page) |
| Canonical | not set |
| Open Graph title | not set |
| Headings / images | 0 H2s, 2 images (1 without alt text) |
Is lwworks.com served over a valid certificate?
The HTTPS certificate is issued by Let's Encrypt and is
valid until 2026-11-07, which is 33 days from the date of this check. It covers
1 hostname.
- lwworks.com
The certificate has 33 days left to run.
It covers 1 hostname, so it was issued for this site specifically.
Let's Encrypt certificates are free and run on 90-day terms, so this site is almost certainly renewing automatically.
Which security headers does it set?
3 of 6 are set (HSTS, X-Content-Type-Options, X-Frame-Options). Absent: Content Security Policy, Referrer-Policy, Permissions-Policy.
With no Content Security Policy, any script that reaches the page — including one injected through a compromised third-party dependency — runs with full access to it.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=15552000 |
| Content Security Policy | no | — |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | no | — |
| Permissions-Policy | no | — |
How is DNS configured for lwworks.com?
| IP addresses | 198.49.23.145 |
|---|---|
| Reverse DNS | 198.49.23.145 |
| Name servers | ns-cloud-e2.googledomains.com, ns-cloud-e4.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e1.googledomains.com |
| Mail (MX) | no mail records |
| SPF | not published |
| TXT records | 0 |
lwworks.com resolves to a single address, so there is no DNS-level redundancy.
No MX records are published, so this domain does not receive mail at its apex. Mail sent to it will bounce.
No SPF record is published. Receiving servers therefore have no published rule for who may send mail as this domain, which makes spoofing it materially easier.
Reverse DNS resolves to 198.49.23.145, which usually names the hosting provider.
Who runs DNS and mail for lwworks.com?
DNS is operated by Google Cloud DNS rather than self-hosted name servers.
No AAAA records are published, so the site is reachable over IPv4 only.
Can lwworks.com be spoofed in email?
No DMARC record is published, so there is no instruction telling receiving servers what to do with mail that fails authentication. In practice that means forged mail from this domain is likely to be delivered.
No CAA records are published, so any certificate authority may issue a certificate 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 795 bytes and names
30 user-agent groups.
It disallows all crawlers from the site root.
No sitemap is declared in robots.txt.
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| claudebot | allowed |
| google-extended | allowed |
| ccbot | allowed |
| applebot-extended | allowed |
| bytespider | allowed |
| anthropic-ai | allowed |
robots.txt disallows all general crawlers from the site root, which is an explicit decision to stay out of search results.
No sitemap is declared in robots.txt, so crawlers must discover pages by following links.
Named AI crawlers are explicitly allowed (gptbot, claudebot, google-extended, ccbot, applebot-extended, bytespider, anthropic-ai).
What structured data does the homepage publish?
No JSON-LD or microdata was found on the homepage.
What does lwworks.com load from third parties?
The homepage pulls resources from 2 third-party hosts (assets.squarespace.com, fonts.googleapis.com). Each one sees the visitor IP and user agent on every page load.
1 cookie is set before any interaction (crumb).
1 resource is referenced over plain HTTP on an HTTPS page, which browsers block or flag as mixed content.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| crumb | yes | no | none/unset |
Does lwworks.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both lwworks.com and www.lwworks.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can lwworks.com be crawled?
No readable sitemap was found, so crawlers have to discover every page by following links.
A deliberately invalid URL returns HTTP 200 rather than 404. That is a soft 404: every mistyped or stale link becomes an indexable page, which inflates the site with duplicates.
What tracking does lwworks.com run?
No analytics or advertising trackers were detected on the homepage of lwworks.com, which is unusual for a commercial site.
How does lwworks.com look when shared?
No Open Graph or Twitter Card tags are present. Links shared to social platforms will fall back to whatever the platform can scrape, usually just a bare URL.
How are images, fonts and scripts handled?
2 images on the homepage, 1 of them lazy-loaded (50%).
Modern image formats are in use (2 WebP/AVIF references).
Fonts are loaded from Google Fonts, which means every page view also contacts Google. Self-hosting removes that dependency.
The page pulls 2 external stylesheets and 5 external scripts, with 0 carrying defer or async.
Is lwworks.com accessible and current?
The page uses 0 landmark elements and 0 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index lwworks.com?
The homepage carries a noindex directive, so it is asking search engines to keep it out of results entirely.
No canonical URL is declared, which leaves duplicate addresses of this page to be resolved by the search engine.
The homepage carries 0 internal and 1 external link across 1 outside host.
Visible text is only 3.1% of the HTML, which indicates the page is assembled in the browser rather than served as content.
How is lwworks.com delivered?
No Cache-Control header is sent for the HTML, so caching behaviour is left to browser defaults.
No favicon is declared in the markup.
Frequently asked questions
Does lwworks.com set the usual HTTP security headers?
It sets 3 of 6. The ones not present are: Content Security Policy, Referrer-Policy, Permissions-Policy.
Does lwworks.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is lwworks.com built with?
The homepage exposes these fingerprints: Squarespace. A site behind a CDN or rendered server-side may use more than it reveals.
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 lwworks.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 →