Free Tool
Website Technical Audit
Run a free website technical audit before you ship or migrate.
What it calculates
A consolidated infrastructure snapshot: DNS resolution, redirect chain, TLS certificate, security headers, SPF/DMARC/MX posture, robots.txt, and sitemap discovery for the apex domain.
Why it matters
Launch delays usually trace to DNS, HTTPS, or crawl blocks — not content. Operators need a single preflight before campaigns, migrations, or investor demos.
The Learn Domains moat
Check → Diagnose → Activate → Ship fixes → Measure lift
Monitoring tools stop at the score. Learn Domains turns gaps into ranked actions inside your command center.
- 1Check
You ran the checker on your domain and topic.
Done - 2Diagnose
Readiness score + live mention gaps on missed prompts.
Learn more - 3Activate
Connect site, add Knowledge Base, generate Mission Brief.
Learn more - 4Ship + measure
Growth Orders → content drafts → Signal AI referrals.
Learn more
Apex domain only — no paths, IPs, or ports.
What this checker verifies
DNS A/AAAA/CNAME resolution, HTTPS redirects, TLS certificate validity and hostname coverage, security headers (HSTS, CSP, XCTO), SPF/DMARC/MX records, robots.txt availability, and sitemap discoverability.
Scans run from Learn Domains infrastructure against the apex domain you submit. We do not crawl arbitrary URLs, probe ports, or run penetration tests. Results describe observed configuration at scan time.
Treat output as operator signal — not a security certification, ranking guarantee, or legal attestation.
How to interpret the result
The health score weights critical infrastructure failures heavily. A single expired certificate or missing DNS answer can block all traffic even when content is perfect.
Severity labels rank urgency: critical issues often block traffic or trust; high issues degrade deliverability or crawl efficiency; medium and low items are worth scheduling before they compound.
When a finding is marked inference or needs human review, confirm in your DNS host, CDN, or registrar before shipping a production change.
Common causes of this issue
Incomplete DNS cutover, CDN SSL modes set to flexible, stale SPF after changing email providers, or robots.txt accidentally blocking crawlers during staging merges.
Misconfigured migrations, partial CDN setups, and copied DNS templates are the usual culprits. Compare www and apex behavior when redirects look inconsistent.
If you recently changed hosts, allow TTL propagation before re-checking — a stale cache can look like a failure for up to 48 hours.
How to fix it
Fix resolution and TLS first, then mail authentication, then crawlability files. Align www and apex canonical behavior before tuning headers.
Document what you changed and when. Technical change detection inside Learn Domains compares future scans to this baseline so regressions surface in the Operator.
For email posture issues, coordinate with whoever owns your ESP (Google Workspace, SendGrid, etc.) so SPF and DMARC align with live senders.
When to re-check
Run again after DNS TTL propagation (often 1–24 hours) and after certificate renewals. Schedule weekly scans during active launch windows.
Re-run after DNS TTL windows, certificate renewals, or deploys that touch edge configuration. Weekly monitoring catches drift before launch deadlines.
Connected workspaces in Learn Domains store scan history — public checks are ephemeral snapshots for visitors.
Related Learn Domains workflows
Connect the domain in Learn Domains to save scans, diff against prior runs, and open /tech preflight in the Operator without re-entering context.
Learn Domains treats technical health as growth infrastructure — the same engine powers Mission Brief priorities when fixes block activation.
Start a $1 trial to connect the domain, run full Technical Preflight in the Operator (/tech), turn findings into Growth Orders, and monitor technical health alongside Mission Brief priorities.
Examples
Pre-launch migration
Scenario: You moved hosts Friday night and need to confirm HTTPS and redirects before Monday ads.
Outcome: Preflight surfaces missing HSTS, a long redirect chain, or SPF gaps before spend goes live.
Agency client handoff
Scenario: A client insists the site is ready; you need evidence before accepting the launch sign-off.
Outcome: Exportable findings list what is confirmed vs what still needs registrar or CDN changes.
Use cases
- Pre-launch QA for marketing sites
- Post-migration verification
- Investor or partner technical diligence
- Baseline before connecting GSC and GA4
Learn Domains perspective
Learn Domains treats technical health as growth infrastructure — the same engine powers Mission Brief priorities when fixes block activation.
FAQ
- Is the Website Technical Audit free?
- Yes. Anonymous visitors can run a limited number of checks per day. Results are cached briefly to keep scans fast. Full history, change detection, and Growth Orders require a Learn Domains workspace.
- Does this scan my entire site?
- No. Public tools inspect DNS, HTTPS entry points, robots.txt, sitemap discovery, mail records, and response headers for the apex domain. They do not brute-force paths or audit every URL.
- Can I scan any domain?
- You can check publicly registered domains you have permission to evaluate. We block internal networks, localhost, and platform abuse targets. Rate limits apply per visitor and per domain.
- How is this different from Learn Domains in the app?
- The app runs the same Technical Intelligence engine with saved history, workspace context, AI Operator interpretation, and one-click Growth Orders. Public tools deliver a snapshot; the product runs the operating loop.