Stack Notes
Email marketing and hosting — One domain, two senders, a single reputation
Your newsletter and your invoices leave the building by different routes, and every receiving server judges both of them against the same domain name.
The short answer
Use hosting for the site, the forms and the mailboxes, a dedicated sending platform for anything at volume, and DNS authentication to bind the two into one trusted sending domain. Outbound mail from our plans goes out through MailChannels, and the way you confirm the whole arrangement works is by reading the Authentication-Results header on a message you have sent to yourself.
Below: how to read those headers properly, the three records that authorise two senders without contradicting each other, why alignment fails silently for so many people, and what to measure once campaigns are actually going out.
By the HostingFast team · Reviewed 24 August 2026
24/7
Humans on support, any hour
1-click
WordPress deployment
Free
SSL, issued and renewed
Daily
Backup cadence, every plan
Inbox placement for campaigns rests on sender reputation accumulated across dedicated sending infrastructure, with warmed addresses and feedback loops behind it. That is what an email service provider operates, and it is precisely what hosting SMTP cannot supply at volume — not because the software is worse, but because the reputation model is different.
The part people get wrong is not choosing the split; it is wiring it up. Two senders on one domain means one SPF record that authorises both, a DKIM key published for each, and a DMARC policy sitting over the top. Get that wrong and the campaign platform you are paying for delivers into spam while the invoices from your own mailbox arrive perfectly.
Read the headers before you change any records
Send a message from each sender to an address you can inspect, then open the raw source and find the Authentication-Results header. It states plainly whether SPF passed, whether DKIM passed and whether DMARC passed, and it does so from the receiving server's point of view rather than from a checker's.
Do it for both routes. A very common state of affairs is that mailbox mail passes everything and campaign mail fails DMARC, which nobody notices because the person testing sends from their own desk.
Keep the two header dumps. They are the before-and-after evidence for every DNS change you are about to make, and DNS is exactly the place where you want evidence rather than recollection.
Three records, and the faults inside them
One SPF record per domain — not two. Publishing a second is a configuration error rather than an addition, and it invalidates both. Merge the includes into a single record and keep an eye on the lookup limit, because a record that chains through too many includes fails for a reason nothing tells you about.
DKIM wants its own selector per sender, so your host and your sending platform each sign with their own key and neither one's rotation breaks the other. DMARC should start permissive with an aggregate reporting address, so the reports tell you who is sending as you before you enforce anything.
Alignment is the subtle one: DMARC passes only when the visible From domain matches the domain that authenticated. A platform sending on your behalf from its own domain will pass SPF and still fail DMARC, which is the single most common cause of "it says it is authenticated but it still goes to spam".
Where the line belongs, and the plan behind it
Use hosting for the site, the forms and the mailboxes, a dedicated sending platform for anything at volume, and DNS authentication to bind the two into one trusted sending domain.
In our line-up the site side of that is the Turbo plan: 20 GB of NVMe, up to 25 sites, mailboxes on your own domain with webmail, IMAP, POP and SMTP, spam and virus screening from the start, SSL and migration included, and renewal charged at the order rate.
Pushing a bulk campaign through hosting SMTP is the trap: shared address reputation and hourly send limits turn a routine newsletter into a self-inflicted deliverability incident.
Measure sending, not just sends
Once campaigns are going out, the numbers to watch are bounces, complaints and the pattern in your DMARC aggregate reports. A rising hard-bounce rate means list hygiene; complaints mean content or frequency; unexpected sources in the DMARC reports mean somebody is sending as you.
Treat a new sending domain the way you would treat any cold start — volume gradually rather than all at once, to your most engaged recipients first. The reputation you are building is attached to the domain, which is also the domain your invoices leave from, and that is the reason to be careful with it.
The wiring, not the sales pitch
We are not going to sell you campaign sending we do not run. What we will do is tell you exactly which header to read and which record to fix, because the split arrangement fails in the DNS far more often than it fails in either platform.
NVMe storage and LiteSpeed caching power every tier from the smallest plan up — the signup forms feeding your list are on the fast path along with everything else.
- Authentication-Results tells you the truth
- One SPF record, merged, under the lookup limit
- A DKIM selector per sender
- DMARC permissive first, with reports coming in
Why HostingFast
Standard on every plan
Mailboxes included, not resold
Every hosting plan carries mailboxes on your own domain with webmail, IMAP, POP and SMTP — the transactional half of the split costs nothing extra.
Outbound delivery handled
Mail leaving our plans goes through MailChannels, which is the part of transactional sending most hosts leave to chance.
Screening enabled before you ask
Spam and virus filtering applies to every mailbox by default rather than after the first bad week.
DNS you can edit yourself
SPF, DKIM and DMARC records are yours to change in the panel, so a fix is a five-minute job rather than a ticket.
A company on the record
Vitalcare at Home Ltd, registered in England and Wales — verifiable before your domain's reputation depends on anyone.
One rate, order and renewal
Marketing budgets move around; the hosting line under them does not, because the renewal price is the order price.
Quick Start
From order to online
- 1
Dump the headers from both senders
One message from a mailbox, one from the campaign platform. Read Authentication-Results on each and record what it says.
- 2
Merge SPF, split DKIM
A single SPF record authorising both routes; a separate DKIM selector for each so neither rotation breaks the other.
- 3
Turn DMARC reporting on first
Start permissive with an aggregate address, read a fortnight of reports, then tighten the policy once you know who is sending.
Built In
Loaded onto every plan
- Full SSH with Git and Composer, not a restricted shell
- Softaculous on board for one-click application installs
- LiteSpeed cache built into the server, not bolted on by plugin
- A one-click installer covering WordPress and 400+ applications
- Webmail plus IMAP, POP and SMTP for any mail client
- In-place plan upgrades — no migration when you grow
- First year of your domain included on annual orders
- Mailboxes running on your own domain name
- cPanel, so your existing muscle memory still fits
- Spam and virus screening applied to every mailbox by default
Frequently Asked
What people ask us most often
How do I confirm SPF, DKIM and DMARC actually pass?
Send a message to an address you can inspect, open the raw source and read the Authentication-Results header. It reports each check from the receiving server's own point of view, which is the only opinion that counts. Do it once from a mailbox and once from your campaign platform, because those are two different senders and only one of them is usually broken.
Why does having two SPF records break things?
Because the specification allows exactly one, and a domain publishing two is treated as misconfigured rather than as having twice the permissions. Merge the includes into a single record. While you are there, watch the DNS lookup limit — a record that chains through too many includes fails silently, and nothing in your mail client will ever mention it.
What is alignment, and why does DMARC fail without it?
DMARC requires that the domain your recipients see in the From line matches the domain that actually authenticated the message. A platform sending on your behalf from its own domain can pass SPF and still fail DMARC for that reason alone. The fix is to sign with a DKIM key published under your domain, or to send from a subdomain of yours that the platform is authorised for.
Should DMARC start at a permissive policy?
Yes, with an aggregate reporting address attached. The reports will show you every source sending as your domain, including the ones you had forgotten about — an old form handler, a CRM, a supplier. Read a fortnight of them, fix or authorise what you find, and only then tighten the policy. Enforcing first is how legitimate mail disappears.
Keep reading
Hosting With Staging Environments
Testing a change on a clone before it reaches the list, with the same measurement either side.
Hosting With PostgreSQL
When an application expects Postgres rather than MySQL, and what that changes about the plan.
How to Secure Your Email Account
Locking down the mailbox itself, in the order that closes the biggest gaps first.
Mail Filtering
Spam and virus filtering placed in front of any mailbox, hosted anywhere.
Web Hosting
cPanel hosting on NVMe with SSL, free migration and a year-one domain included.
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.
Get the wiring right.
Mailboxes included, outbound delivery handled, DNS you control, and a renewal rate that matches the order rate.
View Mail Filtering plans