---
title: "Contact Form Not Sending Email? How to Find Where It Went"
description: "A customer says they filled in your form and heard nothing. The five places an enquiry can vanish, a five-minute test that finds which one, and how to fix it."
url: "https://arlingtonwebsitedesigner.com/blog/contact-form-not-sending-email/"
lang: "en"
published: "2026-03-12"
modified: "2026-03-12"
author: "Cal Hewitt"
tags: ["what-goes-on-a-site","running-the-business"]
image: "https://arlingtonwebsitedesigner.com/og/blog-contact-form-not-sending-email.jpg"
---

# Contact Form Not Sending Email? How to Find Where It Went

[Cal Hewitt](https://arlingtonwebsitedesigner.com/about/cal-hewitt/)Published March 12, 202611 min read

- what goes on a site
- running the business

![Contact Form Not Sending Email? How to Find Where It Went](https://arlingtonwebsitedesigner.com/images/post-contact-form-not-sending-email.jpg)

A customer mentions, in passing, that they filled in your form a fortnight ago and never heard back. You go and look and there is nothing in your inbox. Now you are stuck between two possibilities that feel very different: either the form has been quietly broken and you have no idea for how long, or business has simply been slow and this one person is misremembering. You cannot tell which, and every article you open assumes you are on WordPress and opens by recommending a plugin. The good news is that the answer takes about five minutes to establish, and it works the same way whatever your site is built on.

### Key Takeaways

#### A success message on the page proves one thing only

that the form's own system accepted the submission. It says nothing about your inbox.

#### An enquiry can die at five separate points

, and knowing which one changes who fixes it and how.

#### Test from a different address and a different device

, because logged in on your own laptop is not what a customer meets.

#### A form that worked for years and stopped in 2024 has a likely cause

sender authentication requirements that changed in February that year.

#### The only honest measure of the damage is a count

, not a revenue figure. Count submissions with no matching notification over a defined period.

## Is It Broken, or Is Nobody Writing?

This is the question, and it is answerable today rather than after weeks of wondering.

The underlying thing worth knowing is that an HTML form does not send email. It sends the data somewhere, and something at that end decides what happens next: store it, notify somebody, hand it to another service, or fail. The [documentation on how form data is sent](https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data) describes exactly that separation, and it matters here for one practical reason.

It means "Thank you, your message has been sent" is a statement the page chose to display at a particular stage. It is honest about that stage and it is not a delivery receipt. A form can show that message every single time while nothing ever reaches you.

So, the two possibilities collapse into one test. Send yourself a submission under controlled conditions and follow it. If it arrives, the form works and business was quiet. If it does not, you now have a specific fault to chase rather than a worry.

## What Is the First Test to Run?

Do this now, before you change any settings, because changing settings first destroys the evidence of what was actually wrong.

Open your site the way a customer does. Log out, or use a private browsing window, on a phone rather than the computer you built the site on. Go to the contact page as a visitor would.

Fill the form in completely, using an email address that is not your business one. A personal address on a different provider is ideal, because it tests a different receiving mail system. In the message field, write something you will recognise and the time, for example "test submission, 2:15pm Tuesday".

Submit it and write down exactly what the page did. Did it show a success message, reload, go to a thank-you page, show an error, or appear to do nothing at all? That response is your first piece of evidence.

Then wait ten minutes and check three places, in this order: the inbox you expect it in, that inbox's spam or junk folder, and any shared or forwarded mailbox the form might actually be pointed at. That last one catches more cases than people expect, because the destination address is frequently something set years ago by somebody who has left.

What the page did, and what it tells you

Hover or tap a row to highlight it.

| What happened after you submitted | What it rules in | Where to look next |
| --- | --- | --- |
| Success message, email arrived | Nothing is broken | Business was quiet. Check the form is easy to find |
| Success message, no email | The form accepted it. The notification or delivery failed | The form's own records, then the notification settings |
| Visible error message | The submission did not complete | The form itself, or a required field the customer could not see |
| Page did nothing at all | Something blocked the submission in the browser | Often a script error or a blocked resource |
| Went to a blank or missing page | The destination is wrong or gone | The form's configured action |

What happened after you submittedSuccess message, email arrived

What it rules inNothing is broken

Where to look nextBusiness was quiet. Check the form is easy to find

What happened after you submittedSuccess message, no email

What it rules inThe form accepted it. The notification or delivery failed

Where to look nextThe form's own records, then the notification settings

What happened after you submittedVisible error message

What it rules inThe submission did not complete

Where to look nextThe form itself, or a required field the customer could not see

What happened after you submittedPage did nothing at all

What it rules inSomething blocked the submission in the browser

Where to look nextOften a script error or a blocked resource

What happened after you submittedWent to a blank or missing page

What it rules inThe destination is wrong or gone

Where to look nextThe form's configured action

## Where Can an Enquiry Actually Disappear?

There are five links in the chain and an enquiry can be lost at any one of them. Naming them is most of the diagnosis, because each has a different owner and a different fix.

The first is the browser. The visitor pressed the button and the data never left, usually because of a script error, a blocked file or a validation rule they could not see. The give-away is a page that appears to do nothing.

The second is the receiving system. The data arrived somewhere and either got rejected or got stored. Most form systems keep their own record of submissions, and that record is the single most useful thing to look at, because it separates "nobody submitted" from "you were not told".

The third is the notification. The submission is safely stored and nothing generated an email about it, or generated one addressed somewhere you do not read. A changed recipient address makes a perfectly working form look completely dead.

The fourth is delivery. The email was generated and the receiving mail server rejected it, deferred it, or accepted it and filed it as spam. This is where the 2024 changes bite, and there is a section on it below.

The fifth is the human one. The message arrived, in an inbox, and nobody saw it. A filter rule, a shared inbox nobody owns, a forwarding rule pointing at a former employee, or simply a busy week.

![A phone showing a submitted contact form with a success message, beside a laptop displaying an empty email inbox and a notepad listing five checkpoints](https://arlingtonwebsitedesigner.com/images/post-contact-form-not-sending-email-1.jpg)

## What Does a Proper Check Involve?

If you hand this over, the work should produce an evidence trail rather than a statement that it is fixed now. Ask to see the trail; it is the difference between a diagnosis and a guess.

It starts with the controlled test, recorded: which address, which device, what time, what the page did. Then the form's own submission history, to establish one of three states clearly. Nothing arrived. Something arrived and was rejected. Something arrived and was stored.

Then the notification configuration: the destination mailbox, the sending address, the reply-to behaviour, and whether anything changed recently, including on the domain. Then the delivery record, which for most sending services shows whether a message was accepted, deferred, bounced, suppressed or delivered, along with what the receiving server said. Worth knowing: "delivered" means the receiving mail system took it, not that a person read it.

Then the recipient side, which is the part that gets skipped. Spam and quarantine, filter rules, forwarding, shared inbox routing, and whether the mailbox is even accessible.

Then one fix at a time, and the same controlled test again. Fixing three things at once means never knowing which one mattered, and it means the next occurrence starts from scratch.

One thing worth deciding while somebody has their hands in this: who should be able to read submissions, how long they are kept, and whether the form asks for more information than it needs. Those are decisions about people's data rather than technical switches, and this is the natural moment to make them.

## How Long Does Any of This Take?

There is no honest universal figure for diagnosis and repair, because it depends on which link broke and who controls it. A wrong notification address is a two-minute fix. A domain authentication problem needs whoever administers your DNS.

What can be stated are two documented monitoring delays, and they are worth knowing so you do not read a delay as a failure. Google says its [Postmaster Tools](https://support.google.com/mail/answer/14668346?hl=en) data is typically updated within 24 hours and can take longer, and that a compliance status can take up to seven days to reflect a correction. DMARC.org says aggregate reports are usually generated daily and advises allowing at least 24 hours after publishing a record before expecting the first one.

So, a fix can be correct on Tuesday and the monitoring that proves it will not catch up until later in the week. The controlled test is your immediate proof; the monitoring is the confirmation.

### What happens when

1.  1

    #### \*\*Your controlled test\*\*: five minutes, and it settles the broken-or-quiet question immediately

2.  2

    #### \*\*Reading the form's own submission history\*\*: same session, and it is the most informative single step

3.  3

    #### \*\*The repair\*\*: no universal figure. A wrong address is minutes, a DNS change involves another person

4.  4

    #### \*\*Postmaster Tools data\*\*: typically within 24 hours, and up to seven days to reflect a compliance correction

5.  5

    #### \*\*First DMARC aggregate report\*\*: allow at least 24 hours after publishing the record

## What Does a Repair Cost?

There is no published, platform-neutral price for this work, and quoting an hourly figure as if there were would be inventing one. The range genuinely runs from correcting a typo in a notification address to repairing an integration, DNS records, access permissions or mailbox routing.

What can be shown is what the sending services themselves charge, which is useful context and is not a repair quote. Retrieved on 3 September 2026, [Postmark's pricing](https://postmarkapp.com/pricing) lists a free tier at 100 emails a month, Basic at $15.00 a month for its displayed 10,000-email volume, Pro at $16.50, Platform at $18.00, and DMARC monitoring from $14 per domain per month. [Mailgun's pricing](https://www.mailgun.com/pricing/) lists a free tier at 100 emails a day, Basic from $15 a month for 10,000 emails, Foundation at $35 for 50,000 and Scale at $90 for 100,000, each after a stated free month.

Those figures show the low end of the sending side. They do not mean every form needs a paid service, and they do not include anybody's time.

Scope grows when custom code is involved, when several forms or domains are affected, when access has to be recovered, when a DNS change needs coordinating with another administrator, when delivery monitoring is being added, or when the investigation turns into a wider security question. If you are weighing that against everything else you pay for, [what a website costs you every month](https://arlingtonwebsitedesigner.com/blog/what-a-website-costs-you-every-month/) covers the recurring items that tend to arrive alongside this one.

## What Can You Check Yourself?

More than you would think, and none of it risks anything.

Run the controlled test. Check spam and junk. Find out which address the form is actually configured to notify, which is usually visible in the form settings without touching anything. Check whether that mailbox still exists and whether anybody reads it. Look at the form's own list of submissions if it keeps one, because that alone answers the original question. Note the date of the last enquiry you definitely received, since that dates the fault.

Where to stop is narrower here than in most website work, and it is specific. Do not change DNS records, sender authentication settings, or mail routing on a live domain unless you know what the current values do, because a mistake there can stop all of your email rather than just the form's. Do not delete or reinstall the form to see if that fixes it, because you will lose the stored submissions that are your evidence. And do not paste credentials or API keys into an email or a support ticket while asking for help.

One more thing, and it matters for the customer rather than for you. If somebody tells you they sent something sensitive through a form that turned out to be broken, do not ask them to send it again through the same form until you have confirmed it works.

![A screen showing a list of stored form submissions with dates, next to a printed note recording the last enquiry the owner definitely received](https://arlingtonwebsitedesigner.com/images/post-contact-form-not-sending-email-2.jpg)

## Why Did a Form That Worked for Years Suddenly Stop?

This is the single most useful thing in this article for anybody whose form used to be fine, and it is barely mentioned in the advice you will find elsewhere.

Google introduced sender requirements for messages sent to personal Gmail accounts from 1 February 2024. Its [guidance for senders](https://support.google.com/mail/answer/81126) recommends SPF, DKIM and DMARC for all sending domains, and says unauthenticated messages can be rejected or placed in spam. It also notes that a third-party sender left out of your SPF record is more likely to be marked as spam.

Read that in the context of how most contact forms work. The form generates an email that claims to come from your domain, and sends it through some other service: your host, a plugin, a form provider. If your domain's records do not authorise that service to send on your behalf, the message is exactly the shape the new rules were written to catch.

So, a form built in 2019, working perfectly, sending through a route nobody documented, can quietly start going to spam or being rejected outright without a single thing changing on your website. The site did not break. The rules around it did.

The fix is not complicated but it is not a website change either. It is a matter of establishing which service actually sends your form's mail, and making sure your domain's records say that is allowed. Whoever administers your DNS does that part.

**Quiz: Where did it go?**

1. You submit a test from your personal address. The page shows a success message, your form's dashboard lists the submission, and nothing arrives in your business inbox or its spam folder. Which link broke?
   - The notification or the delivery, and the form's records prove the submission itself was fine **(correct answer)**
   - The form is broken
   - Nobody was submitting the form
   - The browser blocked it

## Frequently Asked Questions About contact form not sending email

**My form says the message was sent. Does that mean it was delivered?**

No. It means the form's own system accepted the submission and chose to display that message. Delivery to your inbox is a separate step, further down the chain.

**Why are my form emails going to spam?**

Most often because the service sending them is not authorised to send on behalf of your domain. Google says unauthenticated messages can be rejected or placed in spam, and that a third-party sender missing from your SPF record is more likely to be marked that way.

**How do I test my contact form properly?**

Logged out, on a different device, using an email address at a different provider, with a recognisable message and the time in it. Then check the expected inbox, its spam folder, and whichever mailbox the form is genuinely configured to notify.

**How long has it been broken?**

The date of the last enquiry you definitely received is your upper bound, and the form's own submission history usually gives you the exact answer if it keeps one.

**How much business did I lose?**

Honestly, nobody can tell you that from the outside. What you can count is the number of submissions with no matching notification over a defined period, which is a real figure rather than an estimate. Anything beyond that needs your own records of what an enquiry is typically worth.

**Should I just reinstall the form?**

Not until you have looked at its stored submissions. Reinstalling can destroy the record that tells you what was actually happening, and it fixes nothing if the fault is in the notification or the delivery.

- **Form action**: where the browser sends the data when somebody presses the button
- **Submission record**: the form system's own stored list of what people sent
- **Notification**: the email generated about a submission, which is separate from the submission itself
- **SPF**: a record on your domain listing which services are allowed to send email as you
- **DKIM**: a signature proving a message really came from your domain and was not altered
- **DMARC**: a policy telling receiving servers what to do when the checks above fail

## Moving Forward

The question you started with was whether the form is broken or nobody is writing, and it is settled by one controlled submission from a different address on a different device. From there the chain has five links, and each of them is checkable: the browser, the form's own record, the notification, the delivery, and the inbox somebody actually reads.

The two changes worth making afterwards are small. Point the notification at two people rather than one, so a single mailbox going quiet cannot cost you a month of enquiries. And put a test submission in the calendar every few months, which takes two minutes and is the only reason anybody ever finds this early.

If you would rather have somebody follow the chain and show you where it broke, [Arlington Website Designer](https://arlingtonwebsitedesigner.com/) works with businesses around Arlington, TX and this is a common enough first job that it usually ends in a small fix rather than a new form. Tell us what your customer described and roughly when, through [the contact page](https://arlingtonwebsitedesigner.com/contact/), and you will get back which link failed and what it takes to close it.

## More articles

- [The Website Accessibility Letter, and What Reduces the Risk](https://arlingtonwebsitedesigner.com/blog/website-accessibility-and-the-demand-letter/)
- [When a Post Takes Off and Your Website Cannot Take the Weight](https://arlingtonwebsitedesigner.com/blog/when-a-post-takes-off-and-your-site-cannot-take-it/)
- [Should I Add a Chatbot to My Website? A Practical Answer](https://arlingtonwebsitedesigner.com/blog/should-you-put-a-chatbot-on-your-website/)

## Thinking about a site that does this for you?

Tell us what your business does and where you want to be found. We will tell you what we would build and what it would take.

[Start a project](https://arlingtonwebsitedesigner.com/contact/)