Verify that website emails actually arrive

Estimated reading time : 3 min · Published October 5, 2026

Inventory messages and senders

List contact notifications, confirmations, account recovery, invoices and newsletters. For each stream, record its sending service, domain, recipient, expected volume and person responsible for errors. An essential transactional message and a promotional campaign require different decisions.

For a contact form, use a From address on a domain authorised by the sending service. A validated visitor address may be used as Reply-To; using it as From means sending on behalf of a domain you do not control. Provide a monitored address for replies.

Have domain authentication checked

SPF describes authorised senders, DKIM supports signature verification and DMARC evaluates alignment with the domain displayed in From. They complement one another but do not guarantee inbox placement. Requirements depend on the recipient service and sending volume: consult current provider guidance.

Ask the email owner to compare domains used by the website, business tools and automated messages. Adding a sending platform may require DNS changes. Inventory legitimate streams and arrange observation before adopting a rejection policy. Public pages must never contain connection credentials or private keys.

Test the whole journey

Use consenting test addresses to submit an enquiry on a phone, then check storage, the internal notification, visitor confirmation and the ability to reply. Try several mailbox providers. Inspect spam folders, authentication headers and links; one test with the sender’s own mailbox does not cover other recipients.

Include an invalid address, a temporary refusal, a blocked recipient and a retry after failure. Retain a test reference, time and observed state. Avoid copying private message bodies into logs. Acceptance by the email service must not be described as proof that the message was read.

Handle errors and preserve continuity

Distinguish permanent bounces from temporary incidents using the provider’s returned codes. Define retry handling and a process for invalid destinations. For newsletters, test unsubscribe and its effect on the next campaign. A contact enquiry is not an agreement to join a mailing list.

If an enquiry was recorded but email failed, give the team a way to retrieve it without forcing the visitor to start again. Repeat tests after DNS migration, provider changes or form updates. Deliver an inventory of streams, states, test results and the person responsible for alerts.

Reference documents

Content updated on October 5, 2026

Record checks and findings in the acceptance log

Acceptance matrix to adapt to your project

These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

Test cases, expected outcomes and useful evidence
Case	Expected outcome	Evidence to retain
Recorded enquiry	The team can retrieve the submission.	Test reference and receiver-side check.
Authentication	The sender domain is authorised and expected checks pass.	Anonymised headers from a test email.
Invalid address	Failure is handled without endless retries.	Recorded state and recovery procedure.
Reply and unsubscribe	Actions match the message type.	Reply or mailing-list removal test.

Frequently asked questions

Does a passing SPF or DKIM result suffice?

It confirms an authentication check, not receipt, reading or inbox placement. Verify alignment, the actual delivery path, reported errors and message relevance too.

Should email failure after storage appear as a failed submission?

The message should reflect what happened. If the enquiry was saved, confirm receipt without claiming an email was delivered. The team needs a way to retrieve and process the enquiry.

Can DNS settings be copied from another website?

Values depend on the services authorised to send for your domain. Have the email owner establish and test settings using your provider’s documentation.