How to Test Your Contact Form (Properly)
Most broken contact forms look perfectly fine. Here is how to test yours end to end — and how to find out the next time it quietly stops delivering.
Common signs of this issue
- You have no idea when your form last delivered a real message.
- Enquiries have dried up, but the form still shows a cheerful "thank you" when you try it.
- You tested it by emailing yourself and it arrived — so you assume everyone else's messages arrive too.
- A customer says they contacted you and never heard back, and you have no record of their message.
- The form was set up by someone who has since left, and nobody has checked it since.
- You changed hosts, changed email providers, updated plugins, or redesigned the site — and never retested the form afterwards.
- Form notifications go to an address that nobody actually reads any more.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Submit a real test from outside your own systems. Use a phone on mobile data and an email address on a different provider from your own. Testing from your own office network and your own domain hides some of the most common failures.
- Fill it in like a customer would — a normal name, a real-looking phone number, and a couple of sentences. Don't type "test test test": spam filters treat that exactly as it reads, and you may be testing the one message shape that gets blocked.
- Check the inbox that should receive it, then check that inbox's spam and junk folders, then check any filters or rules that might be quietly moving form mail into a folder you never open.
- Confirm what the visitor sees. After sending, is there a clear confirmation message or thank-you page? A form that submits silently makes people submit again, or leave assuming it is broken.
- Test on a phone, not just a laptop. Most enquiries now come from mobile. Check that every field is reachable, the keyboard doesn't cover the submit button, and any anti-spam checkbox actually works on a small screen.
- Try to break it on purpose: leave a required field empty, enter a deliberately malformed email address, and paste in a long message. You want to see a helpful error, not a dead button or a lost message.
- Check whether messages are also stored on the site, not only emailed. Most form tools can save every submission in the dashboard as well as sending it. That single setting turns a silent email failure from a lost customer into a minor annoyance.
- Write down the date you tested and put a repeat in the calendar — monthly is plenty for most small sites. A test you did once two years ago tells you nothing about today.
What this usually means
A contact form has two halves, and only one of them is visible. The visitor's half either works or obviously doesn't. The delivery half — website hands the message to a mail server, mail server hands it to your inbox, your inbox decides where to put it — fails silently by design. That is why a form can show "thank you" for months while every message quietly disappears.
The classic mistakes all live in that invisible half: sending from an address at your own domain that your mail provider does not authorise, so the message is discarded as forgery; notifications aimed at an old staff address; a spam filter that learned to bin the notifications; anti-spam settings turned up so high that real visitors are blocked; or a plugin update that quietly reset the notification settings back to defaults.
Which is why the only test that means anything is a full end-to-end one: submit from outside, receive in the real inbox, and confirm the visitor was told it worked. Everything short of that — the form loads, the button animates, the plugin says it is active — proves nothing about whether your next customer will actually reach you.
What not to do
- Don't test only from your own computer and your own email address; that is the one path most likely to work even when everyone else's fails.
- Don't rely on the on-screen thank-you as proof of delivery — it usually appears whether or not the email ever left the building.
- Don't test with the message body "test" and then conclude your form is fine when it lands in spam.
- Don't leave form notifications going to a single person's address; use one that at least two people can read, so nothing stalls when someone is away.
- Don't turn anti-spam protection all the way up to stop junk. Blocking every real enquiry is a far more expensive problem than deleting a few spam messages.
- Don't assume a form that worked at launch still works. Host moves, email migrations, and plugin updates all break delivery without ever touching how the form looks.
When to get help
If your test messages never arrive and the form settings look right, the problem is usually mail authentication — SPF, DKIM, and DMARC records, or the site sending mail through the wrong route entirely. That is a fiddly, invisible area where a professional will find the answer in minutes and a business owner can lose an afternoon. Getting help is also sensible if the form is your main source of enquiries: it is worth having someone set up stored submissions and an automatic delivery check once, so that a silent failure never costs you weeks of leads again.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
How do I know if my contact form is working?
Submit it from outside your own network with an email address on a different provider, then confirm the message arrives in the real destination inbox — not just that the site showed a thank-you page. Anything less does not prove delivery.
Why did my test email arrive but customer messages don't?
Usually because your test came from a trusted address or network. Messages from strangers can be caught by spam filters, blocked by anti-spam settings on the form, or rejected because the site is not authorised to send mail using your domain.
Is there a contact form checker tool?
Uptime and monitoring services can submit a form on a schedule and alert you when it fails, and most form plugins can log every submission in the site's dashboard. Between the two you get an automatic record and an alert, rather than finding out from an annoyed customer.
How often should I test my contact form?
Monthly for most small business sites, and always after a host change, an email provider change, a redesign, or a round of plugin updates — those are the four changes that most often break delivery.
What are the most common contact form mistakes?
Sending notifications to an unread address, keeping no stored copy of submissions, spoofing the visitor's address as the sender, too much anti-spam friction, no confirmation message for the visitor, and asking for far more fields than the enquiry needs.
Should form submissions be saved on the website?
Yes. Storing them means an email failure costs you nothing but a notification. It is one checkbox in most form tools and it is the single most useful safeguard you can turn on.