0122
Transport & TLS
HTTPS, the certificate, protocol versions, HSTS and the encrypted path a visitor actually takes.
Weighted 16%Website migration audit
Is your site ready to move?
Enter any website. We check the things that decide whether a migration is clean or expensive: HTTPS and the certificate, www and apex, metadata, HSTS, llms.txt,security.txt, well-known files, headers and more.
What we check
159 checks, grouped the way a migration actually fails.
Most checks are ours: we fetch the pages, read the headers, parse the HTML and do the TLS handshake. We only call an outside service where a Worker genuinely cannot see the answer.
0210
Hosts & redirects
Whether www, the apex and http all agree on one canonical address, without chains or duplicate content.
Weighted 10%0321
Metadata & social
Titles, descriptions, canonicals, Open Graph, structured data and the signals search engines and social platforms read.
Weighted 12%0419
Crawl & index
robots.txt, sitemaps, status codes, AI crawler rules and whether the site can be understood and indexed cleanly.
Weighted 12%0519
Well-known & trust
security.txt, llms.txt, change-password, MTA-STS, app associations and the other machine-readable trust files.
Weighted 8%0632
Security & privacy
Security headers, CSP, cookie flags, mixed content, email authentication and the domain's own security posture.
Weighted 14%0719
Performance & UX
Server response, page weight, compression, render-blocking assets, caching and — when available — Lighthouse and Core Web Vitals.
Weighted 14%0817
Migration readiness
What the site runs on, how much content there is, and what moving it to Lexiphanic would involve.
Weighted 14%How it works
Enter the address
One domain is enough. We normalise it and audit the apex and www together, because that is where most migration surprises start.
We check the site
HTTPS and the certificate, redirects, metadata, HSTS, llms.txt, security.txt, well-known files, headers, email DNS and the rest.
Read the report
A shareable, printable report with the evidence, why each finding matters, and what we would do about it before the move.
Methodology
A score you can take apart.
The overall score is a weighted average of eight categories. Individual checks are pass, warning, fail or informational. Checks that do not apply — or that we could not run — are shown honestly and excluded from the score.
Grades
A 90–100B 80–89C 70–79D 60–69E 50–59F below 50
| Category | Checks | Weight |
|---|---|---|
| Transport & TLS | 22 | 16% |
| Hosts & redirects | 10 | 10% |
| Metadata & social | 21 | 12% |
| Crawl & index | 19 | 12% |
| Well-known & trust | 19 | 8% |
| Security & privacy | 32 | 14% |
| Performance & UX | 19 | 14% |
| Migration readiness | 17 | 14% |
Pass
The signal is present and sensible.
Warning
Present, but weaker or incomplete.
Fail
Missing or actively working against the site.
Not checked
Blocked, not applicable, or no data.
This is a public-page health check, not a penetration test. We fetch a small sample of pages, do not attempt to log in, and do not test for vulnerabilities.
Is it really free?+
Yes. It is a public tool, not a trial. There is no account and no card. We use it as the first conversation about a migration.
What do you actually check?+
Around 90 signals across transport and TLS, host canonicalisation, metadata, crawlability, well-known files, security headers, performance and migration readiness. The full list is below.
Do you store the site or my details?+
We store the domain, the date and the public findings so the report URL stays stable. We do not use analytics or advertising cookies. See the privacy note.
Why is a check marked “not checked”?+
Some sites block automated requests, some checks need a working PageSpeed Insights key, and some files are optional. We say so rather than turning a missing signal into a failure.
Ready when you are