Why contact form emails land in spam or never arrive
A contact form that sends mail as your own domain without authorisation is treated like a forged message. What SPF, DKIM and DMARC do for form emails, and a five-minute test to run on yours.
On this page
Contact form emails usually land in spam or disappear when the message claims to come from your domain but your domain has not authorised the service that sent it. Gmail and other providers treat that as a possible forgery. The fix is a DNS and settings job rather than a form redesign, and you can check whether you have the problem in about five minutes.
How does a contact form send email?
When someone submits the form, your website hands the message to an email service, which delivers it to your inbox. The message needs a "From" address. Many forms use your own address, such as info@yourbusiness.com.au, because it looks tidy. But the email service is a third party sending on behalf of your domain, and unless your domain's DNS says that is allowed, receiving servers have no way to tell it apart from someone faking your address.
What do SPF, DKIM and DMARC do?
They are three DNS-based checks that let a receiving server confirm a message really came from who it says.
- SPF is a DNS record listing the services allowed to send mail for your domain.
- DKIM adds a cryptographic signature to each message, which the receiver checks against a public key published in your DNS.
- DMARC tells receivers what to do when a message fails those checks, and requires the domain in the visible "From" address to line up with the SPF or DKIM domain.
Your email provider, and the service your form uses to send, each give you the exact records to add. Adding them is a one-off change at whoever manages your DNS.
What does Google require of senders?
Google's email sender guidelines say that since 1 February 2024 all senders to Gmail accounts must set up SPF or DKIM authentication for their sending domains. Senders of more than 5,000 messages a day to Gmail must set up SPF, DKIM and DMARC, and the guidelines also ask senders to keep the spam rate reported in Postmaster Tools below 0.30%. A small business form sends far fewer than 5,000 messages a day, so the basic rule is the one that applies, but the same guidelines are a fair description of what mailbox providers look for. You can read the full text in Google's email sender guidelines.
What do Gmail and Yahoo require of senders?
The table sets out what each provider's own sender page says, as at November 2026. A contact form sends far fewer than 5,000 messages a day, so the "all senders" column is the one that applies, and the bulk column shows where mailbox providers are heading.
| Requirement | Gmail, all senders | Gmail, bulk (5,000+ a day) | Yahoo, all senders | Yahoo, bulk |
|---|---|---|---|---|
| SPF or DKIM | Either one | Both | Either one at a minimum | Both |
| DMARC | Not required | Required, policy can be none | Not required | Required, at least p=none, and it must pass |
| From domain aligned with the SPF or DKIM domain | Not stated | Required | Not stated | Required |
| Spam rate | Below 0.3% in Postmaster Tools | Below 0.30% (below 0.10% recommended) | Below 0.3% | Below 0.3% |
| Forward and reverse DNS on sending IPs | Required | Required | Required | Required |
| One-click unsubscribe | Not required | Marketing and subscribed mail only | Not required | Marketing and subscribed mail only |
| Source | Google email sender guidelines | same page | Yahoo sender best practices | same page |
Yahoo's page does not define a bulk threshold. One-click unsubscribe applies to marketing mail and not to a form notification, so a contact form does not need it. Google also requires TLS for all senders, and says DKIM keys should be at least 1024 bits with 2048 recommended.
How do you test whether your form emails arrive and are authenticated?
- Submit your own form using an address that is not your business address, such as a personal Gmail account.
- Find the notification in the inbox that receives enquiries. If it is in spam, you already have the answer.
- In Gmail, open the message, use the three-dot menu and choose "Show original". The summary at the top shows a pass or fail result for SPF, DKIM and DMARC.
- If any of the three says fail or neutral, send the details to whoever manages your DNS and your form's email service.
- Repeat the test from a second provider, such as an Outlook or iCloud address, because providers do not all judge the same way.
- Use your phone on mobile data rather than the office network, and check the spam folder and any other address that might be receiving enquiries.
- Test again after any change to hosting, email provider, domain or site rebuild. If you manage the site, watch the logs at the moment you submit, because a success message proves the page responded and does not prove an email left.
What should the form use as its sender and reply address?
A more robust setup is for the form to send from an address on a domain that has been authenticated with the email service, and to put the visitor's address in the "Reply-To" field. Replying to the notification then goes to the person who enquired, and the "From" address is one the sending service is permitted to use. If your form currently sends as the visitor's own address, change that, because it is the pattern most likely to fail authentication.
Why can a contact form say "sent" when nothing arrives?
A form can show a success message before it has checked that the email left. After we moved a group of client sites to a different host on 28 August, we found three forms failing in three different ways. The code was the same on both hosts. What did not travel with it was the settings: the email service's key, the address the site sends from, and the address enquiries go to. Those live in the hosting account, not in the code. The full account of the move is in our post on what happens when a host fails.
| Failure | What the visitor saw | What happened | How long before it was found |
|---|---|---|---|
| Enquiries sent to the wrong person | Normal success message | The setting for where enquiries are delivered still held an address of ours from the testing phase, so every enquiry reached us and the client saw none | 28 August to 1 September |
| A form that broke loudly | An error | The hosting account held no custom settings, so the site tried to send with a missing key | 28 August to 1 September |
| A success message that was not true | "You're on the list" | The "from" address was built as hello@undefined because the host passed along the database but not the plain settings values. The email service rejected each message, the site's code logged the error and carried on | 28 August to 1 September |
All three were found by auditing each site's hosting settings on 1 September, then submitting a real enquiry. Nothing in the code was wrong in the first case, and nothing was visible from outside in any of them.
What should a form do when sending fails?
A form that cannot send should say so to the visitor at the moment it fails and give them another way to reach you, such as a phone number. It should also tell somebody on your side by a second route, so a failure is noticed in minutes rather than when a quiet week turns into a quiet month. The sign-up form in the third case had been built so that a failed email could never get in the way of a signup. That suits the visitor and does nothing for the business when no person reads the log.
A shared sending domain adds one more risk. The domain our forms send from had its DNS go offline from 30 August to 1 September while it was on hold over a renewal. The authentication records were unreadable in that window, so mail sent then risked rejection or spam filing. We cannot tell from the tools we have whether any was.
Should you keep a copy of every enquiry somewhere other than email?
Yes. Even a correctly authenticated email can be delayed, filtered or deleted by mistake. If the form also stores each submission in a database, a CRM or a spreadsheet, a lost email does not become a lost lead. This is part of counting the enquiries you already get: you cannot measure what your site produces if some enquiries never reach you.
Who needs access to fix it?
You need access to your DNS, your email provider and your form's sending service. If you are not sure who holds those logins, start with who actually owns your website. The same list of accounts is the one in what to connect first when you add tools to a site.
If you would like someone to run the test on your form and tell you what to change, request a free website audit.
Common questions
- Why are my website contact form emails going to spam?
- Usually because the message claims to come from your domain but your domain has not authorised the service that sent it, so Gmail and other providers treat it as a possible forgery. The fix is a DNS and settings job, not a form redesign.
- What are SPF, DKIM and DMARC records for email?
- Three DNS-based checks that confirm a message came from who it says. SPF lists the services allowed to send for your domain, DKIM signs each message against a key published in your DNS, and DMARC tells receivers what to do when a message fails and requires the visible From domain to line up.
- Does Gmail require email authentication for contact form messages?
- Since 1 February 2024 Google requires all senders to Gmail accounts to set up SPF or DKIM for their sending domains. Senders of more than 5,000 messages a day must set up SPF, DKIM and DMARC, a volume a small business form will not reach.
- How do I check if my contact form emails pass SPF, DKIM and DMARC?
- Submit your own form from a personal Gmail address, open the notification, choose Show original from the three-dot menu and read the pass or fail results at the top. Repeat from an Outlook or iCloud address, because providers do not all judge the same way.
- Which email address should my contact form send from?
- An address on a domain that has been authenticated with the sending service, with the visitor's address in the Reply-To field. Sending as the visitor's own address is the pattern most likely to fail authentication.
- Why does my contact form say it was sent but I get nothing?
- The form can show a success message before checking that the email left. If the sending service rejects the message, or a setting it needs is missing after a hosting move, the visitor still sees a success page and nobody is told.
- How do I test that my contact form really delivers?
- Submit a real enquiry from a phone on mobile data, with a name and email you control, then check the inbox, the spam folder and any other address that might be receiving leads. Repeat after any change to hosting, email or the site.
- How do I make sure no contact form enquiry gets lost?
- Have the form store each submission in a database, CRM or spreadsheet as well as emailing it. Then a delayed, filtered or deleted email does not become a lost lead.
Want a website that turns readers into customers?
A custom site, hosting and upkeep for one monthly fee, with your leads and Google results in a dashboard you can check any time.