Back from secure checkout
Square sent you back to Automation Setup. We will verify the payment and email the setup details to the address entered at checkout. If you need to add anything, use the contact form below.
Lead-path monitoring
Contact form not sending email? Find out before customers give up.
A page can say a form was submitted even when nothing reaches your inbox. The failure may be in the browser, the handler, the notification provider, or the final delivery. Check whether the public form is visible for free, then monitor the whole path if it matters.
Free check — no email required
Can an outside monitor see your contact form?
Enter your homepage or the exact page with the form. We load that page and up to three contact pages linked from it, then look for a recognizable form or lead endpoint. The checker does not enter data, press submit, or store the URL after the request.
What this result means. Finding a form proves that an outside check can reach and recognize the public lead path. It does not prove the form submits, the handler works, or the notification reaches your inbox. Those are separate checks in the paid monitor.
Why a visible contact form can still stop sending email
The page and form can look normal while the work after the click is broken. A serverless function may be missing after a deploy, a mail credential may have expired, a spam filter may be swallowing legitimate messages, or a notification integration may be returning an error nobody records. That is why checking the page alone is useful, but incomplete.
Does the free contact form checker submit my form?
No. It loads the public page and up to three contact pages linked from it, then looks for a recognizable form or lead endpoint. It does not enter data or press submit.
Can the free check prove my contact form is sending email?
No. A visible form can still fail after submission because of a broken handler, expired credential, spam filter, or notification problem. Delivery requires an authorized test submission and confirmation at the destination.
What happens if the checker finds my form?
The result identifies the page where the lead path was found and can carry that page into checkout for one 30-day monitoring term. The paid monitor adds endpoint probes and authorized browser submission tests.
Work through the contact-form delivery troubleshooting checklist →
What we actually check
Two independent checks, because they fail for different reasons. An endpoint can answer
200 while the notification behind it is broken, and a form can look fine in a
browser while its handler is returning an error to real submissions.
Endpoint probes, every 5 minutes
Your lead and contact endpoints get called on a five-minute cycle and the response is checked, not just the connection. A missing function, a bad deploy, or a handler returning the wrong status is caught within minutes.
A real browser submits a real test lead
A headless browser loads your form, fills it, and submits it the way a customer would, then we confirm the submission actually arrived. This is the check that catches the failures a status probe cannot see.
Route health across the site
Redirects, canonical hosts, and the pages your ads and listings point at get verified on the production domain and on any deployment-preview URL you provide, so a broken destination can be separated from an intentional redirect.
Alerts to somewhere you actually look
We agree on the alert path during setup and confirm it before the term starts. Alerts fire only after a failure survives re-checking, so a transient network blip does not train you to ignore the monitor.
The longer version: exactly what gets checked and what we do when it breaks →
The operating record
We did not build this to sell it. It is the monitoring we run on our own portfolio, and these are its current numbers, not projections or a target.
Counts measured 2026‑08‑30.
The whole system is covered by a test suite that runs against production, daily. It also checks whether the source tree changed underneath it, because a run that cannot say what it tested has not really passed. The most recent run that could say so was on 2026‑08‑07: 261 passed, 0 failed, 2 skipped in 58 minutes, with one route check passing on its immediate retry. Runs since then have been green but were started against a working tree, so we do not count them.
What we are not claiming. We have no customers on this service yet — it is new, and you would be early. We are not promising uptime, rankings, or a response time we have not measured. The numbers above describe our own infrastructure, which is the only thing we can honestly show you before there is a customer to point at.
Price
Lead-path monitoring
$49 / 30 days, per site
- Endpoint probes every 5 minutes
- Daily real-browser form submission test
- Route-health checks on production and any preview you provide
- Failure alerts through the setup channel
- A summary of what we checked during the term
- One 30-day term; no automatic renewal
We load your page and check we can actually see the form before we take any money. If we can’t reach it, we say so and charge you nothing — talk to us and we’ll sort it out. This checkout buys one 30-day term and does not renew automatically.
Tell us what you want watched
Send the URL of the page your leads come through. We will check whether the path is monitorable as it stands, tell you what we would watch, and say so plainly if it is not a fit.