Not live for public requests. No form on this page can run a scan today. Owned-site scanning is a separate loop and does not run from this page.

Current status — read this first

The inbound scan pipeline is not live for public requests today. Public and third-party scanning is unhalted (HIS 2026-08-26: the halt was a Lighthouse-to-novel-toolset retool). Unhalting is permission, not execution — this page does not claim a public scan has run. Owned-site scanning is separately authorized and is a different loop; it does not run from this page, and this page does not report whether that loop has started. There is no form on this page that can run a scan, dispatch CI, host a report, or trigger any callback. This shell exists so the front door is honest and reachable before any dynamic surface is wired.

What this flow will do when live (Model A inbound)

  • A site owner enters their public website URL and a contact email.
  • They check a consent box acknowledging how we may use their contact information and what the scan covers — final consent language is counsel-pending and not quoted here.
  • After consent and validation, a mechanical scan runs against the public homepage; findings are reviewed before any prospect-facing report is hosted at a private, tokenized path.
  • We do not cold-call. Any voice follow-up requires a logged hand-raise after consent — not implied by requesting a scan.

Turnstile, form handlers, suppression-ledger checks, CI dispatch, and report hosting at scan.df-d.com are excluded from this static shell and fenced to later Pages Functions leaves per SPEC §1.

What the request will ask for (described — not rendered)

When the live form ships, it will collect three things. This page does not render those controls — including disabled or inert inputs — because a consent control in the DOM is still a consent control, and this company's product reads DOM for exactly that class of defect.

  • Your site URL The public homepage you want scanned.
  • An email address So we can reach you about the results.
  • A consent acknowledgement Permission to scan the submitted URL and contact you about the findings; final wording is counsel-pending and is not quoted on this shell.

Until that live surface exists, contact onboard@dogfooddigital.com if you want to be notified when inbound scan requests open.

What we will not claim on this surface

  • No calibrated ba-score or published threshold values — see /standard.
  • No named-business defect gallery or public rankings.
  • No promise that we will call you without the consent scaffolding above and counsel sign-off.
  • No claim that outbound scout→scan outreach is running — that pipeline is archived/stopped; see our transparency page for how scanning behaves when it resumes.
  • The M2 scan “call me to discuss” path is not this URL. This page is not Retell (RC) and not DFDC. This seat does not write dfd-leadgen.

Related pages

Contact

Dogfood Digital LLC
Email: onboard@dogfooddigital.com