Deliverability Notes
Email hosting vs free email — Read the headers before you argue about mailboxes
Quotes are going out from a freemail address, some of them are not being answered, and nobody has yet opened a message header to find out whether they even arrived.
The short answer
Check the Authentication-Results header on a message you actually sent: if SPF, DKIM and DMARC do not all pass and align under a domain you control, your mail is being judged on somebody else's reputation and no amount of rewriting the subject line fixes that.
A domain mailbox is what puts those three records under your control. Below: how to read the headers, why WordPress mail disappears when the same address works fine from a desktop client, and how to move mailboxes without a delivery gap.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target
24/7
Support, all hours
Free
SSL on all plans
NVMe
Storage class
Most conversations about business email are about credibility, and credibility is real — but it is downstream of something more concrete. If a message never reaches the inbox, its sending address was never going to matter.
Deliverability leaves evidence. Every message carries headers recording whether it passed SPF, whether the DKIM signature verified, and whether DMARC found the two aligned with the visible From domain. That evidence is free, it takes a minute to read, and almost nobody looks at it.
The header that tells you the truth
Send a message to an account on a different provider, open it, and view the original. Find the Authentication-Results header and read three verdicts: spf, dkim and dmarc. You want pass on all three, and you want the domains in the header to be the domain in your visible From address.
Alignment is the part people miss. SPF can pass for a sending service while DMARC still fails, because the domain that authorised the send is not the domain the recipient sees. That mismatch is what pushes otherwise legitimate business mail into a spam folder.
Publish a DMARC record with a reporting address and the aggregate reports arrive without you asking. They tell you every source sending as your domain, which is how you discover the invoicing tool nobody mentioned and the old plugin still using the wrong host.
Why WordPress mail vanishes when Outlook works
PHP's mail function hands the message to the local transport with no signature and no relationship to your domain's published records. The same mailbox, sent from a desktop client through authenticated SMTP, is signed and aligned. That is why one works and the other silently does not.
The fix is to make WordPress send through authenticated SMTP using the mailbox you actually own, so DKIM signs it and DMARC aligns it. Outbound mail here is handled by MailChannels, which puts a maintained sending reputation in front of the message rather than a shared web-server IP.
Then verify it. Trigger a real transactional message — a password reset is ideal — and read the headers on what arrives. Configuration that looks correct in a settings screen and fails in the header is common enough to be worth ten seconds of checking.
Where mail lives versus where the site lives
MX records are independent of the A record, which means the mailbox does not have to live wherever the website lives. Standalone email hosting exists here for exactly that case: a domain whose site sits elsewhere but whose mail you want on a proper platform.
Every hosting plan already includes mailboxes on your own domain, with webmail plus IMAP, POP and SMTP, and spam and virus screening switched on from the start. For most small businesses that is the whole requirement and it is already paid for.
Succession is the unglamorous argument for it. Mailboxes that belong to the business transfer cleanly when staff change; a decade of client correspondence in somebody's personal freemail account does not, and that becomes a legal problem long before it becomes a technical one.
Moving without a gap in delivery
Lower the MX record's time to live a day or two before you cut over, so the change propagates in minutes rather than hours. This is the single step that turns a nervous switch into an uneventful one, and it has to be done in advance because the old TTL governs how long the old value is cached.
Create the mailboxes first, then move the archive with an IMAP transfer, then change the MX. Keep forwarding running on the old side while records settle so nothing in flight is lost. An hour covers most single-user setups.
Afterwards, re-check the headers. Confirm SPF, DKIM and DMARC still pass and align from the new host, and confirm the aggregate reports show only the senders you expect. A move is also the ideal moment to find the forgotten script still sending as you.
Evidence beats reassurance
Any provider can promise good delivery. The header on a message you sent yourself is the only version of that claim you can verify, which is why this page hands you the check rather than the promise.
Mailboxes on your own domain come with every hosting plan, with spam and virus screening on by default and MailChannels handling outbound.
- Authentication-Results, read in full
- Alignment, not just an SPF pass
- SMTP for WordPress, never PHP mail
- Lower the MX TTL before you move
Why HostingFast
Standard on every plan
Mailboxes included with hosting
Your own domain, webmail plus IMAP, POP and SMTP, with no separate subscription to buy.
MailChannels on outbound
A maintained sending reputation in front of your messages instead of a shared web-server address.
Screening on by default
Spam and virus filtering applied to every mailbox from the moment it is created.
Standalone email hosting
For a domain whose website lives somewhere else entirely, mail can still sit on a proper platform.
Records you control
SPF, DKIM and DMARC published under your own domain, which is what makes alignment possible at all.
Sync across every device
IMAP keeps webmail, phone and desktop showing the same messages in the same state.
Quick Start
From order to online
- 1
Read the headers on a real message
Send to an account at a different provider, view the original, and find the Authentication-Results line. Three passes and matching domains means you are being judged on your own reputation; anything else is the problem you came here to find.
- 2
Route WordPress through authenticated SMTP
Stop the site using PHP mail and point it at the mailbox you own, so DKIM signs the message and DMARC aligns it. Then trigger a password reset and read the headers on what actually arrives.
- 3
Lower the MX TTL before cutover
Drop the time to live a day or two ahead of the move so the change lands in minutes. Create mailboxes, transfer the archive over IMAP, switch the record, and keep forwarding running while it settles.
Built In
Loaded onto every plan
- Mailboxes on your own domain included with every hosting plan
- IMAP, POP and SMTP on standard ports, with browser webmail alongside
- Spam and virus screening on every mailbox as standard
- MailChannels handling outbound delivery for your messages
- SPF, DKIM and DMARC records published under a domain you control
- Standalone email hosting for a domain whose site is hosted elsewhere
- DNS records editable from the control panel, TTLs included
- Daily backups covering mail alongside files and databases
- Free migration, with mailboxes brought across by our engineers
- Renewal at the rate you ordered at, and no setup fee at any point
Frequently Asked
What people ask us most often
How do I prove a message passed SPF, DKIM and DMARC?
Send it to an account on another provider, open the original message source, and read the Authentication-Results header. It states each verdict explicitly. Check that the domains named there match your visible From domain — a pass without alignment still fails DMARC and still lands in spam.
Why does WordPress mail go to spam when the same address works from my mail client?
Because PHP's mail function hands the message straight to the local transport with no DKIM signature and no relationship to your published records, while your mail client authenticates properly. Route the site through authenticated SMTP on the mailbox you own and the signature and alignment come back.
What TTL should the MX record have before a move?
Lower it a day or two ahead of the switch so resolvers stop caching the old value for hours. Do it in advance rather than at cutover, because the current TTL governs how long the old record survives. After the move settles, put it back to something sensible.
Can I keep the website where it is and move only the mailboxes?
Yes. MX records are independent of the A record, so mail and web can live at different providers. Standalone email hosting exists here for that case, and every hosting plan also includes mailboxes on your own domain if you would rather keep both in one place.
Keep reading
VPS vs Dedicated Servers
Steal time, disk latency and utilisation — the measurements that decide virtual against physical.
Hosting for Portfolios With Booking
What a scheduler embed costs a portfolio in milliseconds, and how to get most of it back.
How to Send Email From WordPress Reliably
Getting transactional mail out of WordPress reliably, with the header check at the end.
Email Hosting
Real mailboxes on your own domain, with screening and outbound handling included.
Web Hosting
cPanel hosting on NVMe behind LiteSpeed, with SSL, migration and a year-one domain.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Put the records under your own name.
Mailboxes on your own domain with screening included, MailChannels on outbound, and DNS you can edit yourself.
View Email Hosting plans