Email Deliverability
Emails Going to Spam? Here's the Deliverability Fix
A step-by-step checklist to get your messages back in the inbox: authentication records, sending habits, and reputation monitoring that actually work.
3
Core auth records: SPF, DKIM, DMARC
24/7
Human support for DNS troubleshooting
Free
SSL on every mailbox webmail login
30-day
Money-back guarantee on hosting plans
In short
Emails go to spam mainly because of missing authentication (SPF, DKIM, DMARC), a low-reputation sending IP, or content that trips spam filters. To stop it, publish correct SPF/DKIM/DMARC DNS records, set up a matching reverse DNS (PTR) entry, avoid spammy phrases and broken HTML, and warm up new domains or servers gradually before sending in volume.
Most deliverability problems are fixed within a few days once authentication is corrected and a mailbox provider re-evaluates your sending reputation.
If your newsletters, invoices, or transactional emails keep landing in recipients' spam folders, the cause is rarely one single mistake — it's usually a combination of missing DNS authentication, a shared IP with a poor reputation, and content that pattern-matches to junk mail. Gmail, Outlook, and Yahoo all score incoming mail on dozens of signals before deciding where it lands.
The good news is that almost every deliverability issue is fixable at the DNS and server level, without touching your email client. This guide walks through the checks in the order mailbox providers actually apply them, so you can fix the highest-impact issues first.
Authenticate Every Message You Send
Mailbox providers treat unauthenticated mail as suspicious by default. SPF (Sender Policy Framework) lists which servers are allowed to send mail for your domain, DKIM signs each message with a private key so receivers can verify it wasn't altered in transit, and DMARC tells receiving servers what to do when SPF or DKIM fail — and where to send reports. Without all three published as TXT records, a growing share of inboxes will quarantine or reject your mail outright, especially at Gmail and Yahoo, which now require authentication for any sender pushing meaningful volume.
Set up SPF first by adding a single TXT record listing your sending servers, then enable DKIM signing in cPanel's Email Deliverability tool, which generates the correct selector and key automatically. Finish with a DMARC TXT record starting at a monitoring-only policy (p=none) so you can review reports for a week or two before moving to quarantine or reject, which stops spoofed mail from damaging your domain's name.
Avoid Spam-Trigger Content and Keep Your List Clean
Even fully authenticated mail can land in spam if the message itself looks like junk. Filters weigh subject lines full of urgency or all-caps words, image-only emails with barely any text, mismatched display names, shortened or suspicious-looking links, and a poor text-to-HTML ratio. Sending to old, purchased, or scraped address lists is even more damaging, because a high bounce rate or spam-complaint rate tells providers your sending pattern looks like abuse, not legitimate mail.
Keep formatting simple, include a real physical address and working unsubscribe link where relevant, and remove hard bounces after the first failed attempt rather than retrying. A list you've built from genuine sign-ups, with people who open and reply to your mail, is worth far more to your reputation than a bigger list full of dead or disinterested addresses.
Reverse DNS, PTR Records and Sending IP Reputation
Reverse DNS, or a PTR record, maps a sending IP address back to a hostname — the opposite direction of a normal A record. Many receiving mail servers check that the PTR hostname for your sending IP resolves to something plausible (ideally matching or related to your domain or mail server name) before accepting the message. A missing or mismatched PTR record is one of the most common reasons a brand-new server gets flagged, because it's a classic signature of throwaway spam infrastructure.
On shared hosting this is normally configured by the host against the server's IP pool, so it's worth confirming with support that your sending IP has a sensible PTR entry rather than a generic hostname. If you send from a dedicated or VPS IP, you can request a custom PTR record matching your mail server's hostname, which pairs with SPF and DKIM to build a consistent, verifiable identity for every message you send.
Warm Up New Servers and Watch Blocklists
A brand-new IP or domain with no sending history looks exactly like a spammer's setup to filtering algorithms, even with perfect authentication. Warming up means sending a small, steadily increasing volume — starting with your most engaged contacts who reliably open and reply — over one to two weeks rather than blasting a full list on day one. This builds a track record of low complaints and high engagement before you scale up.
Alongside warmup, check your sending IP and domain periodically against public blocklists such as Spamhaus or Barracuda's list; a single compromised script or old contact form can get an IP flagged without your knowledge. If you do land on a blocklist, the delisting process usually requires fixing the underlying issue first (like a leaked mail script) and then submitting a removal request, which typically clears within a day or two once the cause is resolved.
Hosting That Doesn't Fight Your Deliverability
Shared IPs on overcrowded, poorly managed hosting are a common hidden cause of spam-folder placement — one abusive neighbor account can drag down a whole server's reputation. Hosting Cheap runs mail on NVMe-backed infrastructure with proper DKIM tooling built into the control panel, so authentication is a few clicks rather than a manual DNS puzzle.
Our 24/7 human support team can check PTR records, review DMARC reports, and help you interpret a blocklist listing if one ever appears, rather than leaving you to decode raw headers alone.
- One-click SPF/DKIM/DMARC setup from the control panel
- 24/7 human support for DNS and mail server troubleshooting
- Free auto-renewing SSL secures webmail and SMTP logins
- Daily backups protect mailbox data if anything goes wrong
Why Hosting Cheap
What you get
Built-in DKIM tooling
Generate and publish DKIM keys from the control panel without hand-editing DNS zone files.
Clean sending IPs
Mail servers are monitored for abuse so your messages aren't dragged down by a noisy neighbor.
24/7 support
Reach a real person any time you need help reading a DMARC report or a blocklist notice.
Free SSL everywhere
Webmail, SMTP, and IMAP connections are encrypted automatically at no extra cost.
Daily backups
Mailbox contents are backed up daily so a misconfiguration never means lost mail.
30-day guarantee
Test your deliverability setup risk-free with a 30-day money-back guarantee.
How It Works
Get set up in a few steps
Publish SPF, DKIM, and DMARC
Add the three authentication TXT records through the Email Deliverability tool in cPanel.
Clean your list and content
Remove bounced addresses and simplify subject lines and HTML before your next send.
Warm up and monitor
Ramp volume gradually with engaged contacts, then check blocklists periodically.
Included
Everything you need, on every plan
- SPF TXT record published and listing all authorized senders
- DKIM signing enabled with the correct selector
- DMARC TXT record set to p=none for monitoring, then tightened
- PTR (reverse DNS) record matches your sending server's hostname
- Bounced and inactive addresses removed from your mailing list
- Subject lines and HTML kept simple, with a working unsubscribe link
- Sending volume ramped gradually on any new domain or IP
- Sending IP checked against major blocklists on a regular basis
FAQ
Frequently asked questions
Why do my emails go to spam even with correct SPF and DKIM?
Authentication only proves the message really came from you — it doesn't guarantee inbox placement. Content, sending reputation, list quality, and engagement rates all factor into the spam decision, so a fully authenticated message from a poor-reputation IP or with spammy wording can still be filtered.
What is the difference between SPF, DKIM, and DMARC?
SPF lists which servers may send mail for your domain, DKIM cryptographically signs messages so receivers can verify they weren't altered, and DMARC tells receiving servers what to do when SPF or DKIM checks fail, plus where to send reporting data. All three work together rather than replacing one another.
How long does it take to fix deliverability after a DNS change?
Most mailbox providers re-evaluate reputation within a few days of a fix, though DNS propagation itself is usually complete within a few hours. If you were previously blocklisted, delisting can take a day or two after the underlying cause is resolved.
Do I need a PTR record on shared hosting?
Yes, but it's typically managed by the host against the shared IP pool rather than by you directly. It's still worth confirming with support that the PTR hostname for your sending IP looks legitimate, since a generic or missing PTR is a common spam signal.
Can one bad email account affect my whole domain's reputation?
On a poorly managed shared server, yes — if another account on the same IP sends abusive mail, receiving servers can lower reputation for the whole IP, affecting everyone on it. This is why the quality of the host's abuse monitoring matters as much as your own sending practices.
How do I check if my domain is on an email blocklist?
Use a public blocklist lookup tool against your sending IP and domain name. If you're listed, resolve the cause first (such as a compromised script or leaked SMTP credentials) and then submit a removal request to the specific blocklist operator.
Stop Losing Emails to the Spam Folder
Get hosting with built-in DKIM tools, clean sending IPs, and 24/7 human support for every DNS fix.
Get Started