Why Is My Email Going to Spam and How to Fix It

When mail you send from your Ultra Web Hosting domain keeps landing in recipients' spam folders, it is almost never bad luck. Modern mail servers judge every message on authentication, sending reputation, and content, and a gap in any one of those three areas is enough to get you filtered. This guide is about outbound mail (messages you send that end up flagged), not inbound filtering. It walks through the records that prove you are a legitimate sender, how to check your domain and sending IP against blacklists, and the content and list habits that keep you in the inbox.

01. Why Legitimate Mail Gets Flagged

Receiving servers such as Gmail, Outlook, and Yahoo do not have a person reading your message and deciding it looks spammy. They run every inbound message through automated scoring, and a handful of factors carry most of the weight. Understanding which factors apply to you saves a lot of guessing.

• Authentication gaps. If a receiving server cannot verify the message really came from your domain, it treats it as suspicious. This is SPF, DKIM, and DMARC, covered in Section 02. It is the most common cause and the easiest to fix.
• Reputation. Both your sending domain and the IP address it came from carry a reputation score based on past behavior: complaint rates, spam-trap hits, and whether either appears on a blacklist. A new domain has no reputation, which is its own problem (Section 07).
• Content and structure. Certain patterns push the spam score up: misleading subject lines, all-image messages with no text, broken HTML, shortened links, and a From address that does not match the authenticated domain (Section 05).

02. The Three Records That Matter Most

SPF, DKIM, and DMARC are DNS records that let a receiving server confirm your mail is genuine. If you do nothing else in this guide, set up all three. Here is what each one does and where to get the full setup steps.

• SPF (Sender Policy Framework) is a TXT record that lists which servers are allowed to send mail for your domain. The receiver checks whether the sending server is on that list. Full steps are in our SPF guide.
• DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. The receiver uses a public key in your DNS to confirm the message was not altered and really came from your domain. See our DKIM guide.
• DMARC ties the two together and tells receivers what to do when a message fails both checks. It also sends you reports so you can see who is sending as your domain. See our DMARC guide.

A short version of the records looks like this. Replace yourdomain.com with your own domain and adjust the SPF includes to match the servers you actually send from.

; SPF (one TXT record at the zone root)
yourdomain.com.   TXT   "v=spf1 include:_spf.yourhost.com -all"

; DMARC (one TXT record at _dmarc)
_dmarc.yourdomain.com.   TXT   "v=DMARC1; p=none; rua=mailto:[email protected]"

DKIM is enabled per-domain in cPanel or your mail provider, which publishes the public-key TXT record for you. For the full picture on how all three work together, read Understanding Email Authentication: SPF, DKIM, and DMARC. To build valid records without hand-editing syntax, use our SPF Generator and DMARC Generator.

03. Check Your Domain and IP Against Blacklists

A blacklist (also called an RBL or DNSBL) is a published list of domains and IP addresses known for sending spam. Receiving servers query these lists in real time, and a listing can send your mail straight to spam or get it rejected outright. If your authentication is clean but mail still fails, check for a listing next.

1. Run your domain and your sending IP address through our tools suite blacklist check. It queries the major RBLs in one pass.
2. If you are not sure which IP your mail leaves from, send a test message to yourself and read the headers (Section 09). The earliest Received: line that is not your own client shows the sending IP.
3. Note every list that reports a hit. Each blacklist is run by a different organization with its own delisting process.

Requesting delisting is usually straightforward once the underlying problem is fixed:

1. Fix the cause first. Delisting a domain or IP that is still sending spam gets you relisted within hours. Find and stop the source: a compromised script, a hacked mailbox, or a badly managed mailing list.
2. Visit the blacklist operator's site. Each hit from the check links to the list that flagged you. Most operators have a lookup and removal form.
3. Submit the delisting request for your domain or IP. Some remove automatically after a clean period; others need a manual request.
4. Recheck after a day. Re-run the blacklist check to confirm the listing cleared.

04. Reverse DNS and the PTR Record

Forward DNS turns a hostname into an IP address. Reverse DNS (the PTR record) does the opposite: it turns the sending IP back into a hostname. Receiving servers check that the sending IP has a PTR record and that it resolves to a real hostname. A missing or generic PTR is a strong spam signal, because legitimate mail servers almost always have proper reverse DNS.

• On a shared IP, we set and maintain the PTR record for the mail server, and it points at our mail hostname rather than your domain. That is normal and correct: your SPF and DKIM prove the mail is yours, not the PTR. You do not need to do anything here.
• On a dedicated IP (VPS, dedicated server, or a dedicated IP add-on), the PTR should resolve to a hostname you control, and that hostname's forward record should point back to the same IP. This forward-confirmed reverse DNS is what receivers want to see. If it is missing or wrong, ask us to set the PTR, since it is configured at the IP level and not in your zone.

05. Content and Formatting Triggers

Once authentication and reputation are clean, the message itself is what remains. Spam filters score content, and a few habits reliably push that score up. None of these will sink a well-authenticated message on their own, but together they add up fast.

• Spammy subject lines. All caps, rows of exclamation marks, "FREE", "ACT NOW", and money symbols read as bulk spam. Write the subject the way you would to a colleague.
• All-image emails. A message that is one big image with almost no text is a classic spammer trick to dodge content scanning. Keep a healthy ratio of real text to images.
• Broken or bloated HTML. Unclosed tags, inline styles copied out of a word processor, and huge nested tables raise suspicion. Clean, simple HTML scores better.
• Link shorteners. Filters distrust shortened links because they hide the real destination. Link to your actual domain instead.
• Mismatched From address. The visible From domain should match the domain that authenticated the message (SPF and DKIM). Sending as [email protected] while the mail authenticates for a different domain triggers DMARC failures and looks like spoofing.

06. Authenticating Third-Party Senders

The moment you send mail through a service other than your own mail server (a newsletter platform, a CRM, a helpdesk, a website contact form that relays through an external provider), that service becomes a sender for your domain. If you do not authorize it, its mail fails SPF and DKIM and lands in spam, even though you sent it on purpose.

Authorizing a third-party sender is two records:

1. Add their SPF include. Your provider publishes an include string, for example include:_spf.mailprovider.com. Merge it into your single SPF record. Do not create a second SPF record.
2. Publish their DKIM record. The provider gives you a CNAME or TXT record (usually a selector like s1._domainkey.yourdomain.com) to add to your DNS. This lets their signature verify against your domain.
3. Enable DKIM signing in the provider's dashboard once the DNS record resolves.

A combined SPF record that authorizes your host and a newsletter platform looks like this. Note it is still one record, one -all at the end:

yourdomain.com.   TXT   "v=spf1 include:_spf.yourhost.com include:_spf.mailprovider.com -all"

07. Sending Volume and Warming Up a New Domain

A brand-new domain or a domain that has never sent mail has no reputation. Receiving servers treat unknown senders cautiously, and a sudden burst of a few thousand messages from a domain they have never seen looks exactly like a spam campaign. The fix is to build reputation gradually, a practice called warming up.

• Start small. For the first days or weeks, send modest volumes to your most engaged recipients (people who open and reply). Positive engagement builds reputation fastest.
• Ramp up steadily. Increase volume over days, not all at once. Doubling daily is aggressive; a smoother ramp is safer for a fresh domain.
• Keep the pattern consistent. Erratic spikes look suspicious. Regular, predictable sending reads as a legitimate business.
• Watch your bounces and complaints as you scale. If either climbs, slow down and clean the list before continuing.

08. List Hygiene, Bounces, and Unsubscribe

How you manage your recipient list affects deliverability as much as any DNS record. Receiving servers watch how recipients react to your mail, and sending to dead or unwilling addresses is one of the fastest ways to wreck a good reputation.

• Remove hard bounces. A hard bounce means the address does not exist. Keep mailing it and you look like a spammer working a purchased list. Drop hard-bounced addresses after the first or second bounce.
• Handle soft bounces sensibly. A soft bounce (full mailbox, temporary problem) can be retried, but repeated soft bounces over weeks should be pruned too.
• Never buy or scrape lists. Purchased lists are full of spam traps, and hitting a trap can blacklist your domain immediately. Only mail people who asked to hear from you.
• Honor unsubscribes at once. Continuing to mail someone who opted out generates complaints, and complaint rate is one of the heaviest reputation factors.
• Support one-click unsubscribe. Gmail and Yahoo now expect bulk senders to include a working one-click unsubscribe header and a visible unsubscribe link. Missing it can send your whole campaign to spam.

09. Test Your Setup Before a Big Send

Never launch a campaign or roll out a new sending configuration without testing first. A two-minute check saves you from mailing thousands of people from a broken setup.

1. Send to yourself. Mail a test message from your real sending path (the newsletter tool, the contact form, the mailbox in question) to an address you control on a different provider, ideally a Gmail or Outlook account.
2. Open the raw headers. In Gmail, open the message, click the three-dot menu, and choose Show original. In Outlook, open the message and view message source or properties.
3. Look for the three passes. Near the top you want to see spf=pass, dkim=pass, and dmarc=pass. Any fail, softfail, or none points straight at the record to fix.
4. Confirm the records independently. Cross-check with our SPF Lookup, DKIM Lookup, and DMARC Lookup so you know what is actually published, not just what you think you added.
5. Check the folder. Note whether the test landed in the inbox or spam at each major provider you care about, and read any spam-reason the provider shows.

Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of [email protected] designates
         198.51.100.10 as permitted sender) [email protected];
       dkim=pass [email protected] header.s=default;
       dmarc=pass (p=NONE dis=NONE) header.from=yourdomain.com

10. When a Shared IP Neighbor Hurts Reputation

On a shared hosting plan, your mail leaves from an IP address shared with other accounts. That works well the vast majority of the time, because we monitor outbound mail and act on abuse. Occasionally, though, another account on the same IP sends something that gets the address listed, and your mail catches the blast even though you did everything right.

Here is how to tell the difference and what to do:

1. Confirm your own setup is clean first. Run the Section 09 test. If your SPF, DKIM, and DMARC all pass and your content is reasonable, the problem is not on your side.
2. Check the sending IP against blacklists with our tools suite. If the shared IP is listed but your domain is not, that points to a neighbor.
3. Open a ticket. We can see outbound mail activity on the IP, identify the source of the abuse, stop it, and handle delisting with the blacklist operators. This is not something you can fix from your account, and you should not have to.
4. Consider a dedicated IP if you send meaningful volume and want full control of your sending reputation. On a dedicated IP, your reputation is entirely yours, for better or worse. Ask us whether it fits your plan.

Quick Recap: Getting Out of Spam

If you only do six things from this guide, do these:

1. Publish exactly one SPF record, plus DKIM and DMARC so receivers can verify your mail is genuinely yours.
2. Check your domain and sending IP against blacklists and request delisting once you have fixed the cause.
3. Make sure the sending IP has proper reverse DNS, especially on a dedicated IP where the PTR should resolve to a hostname you control.
4. Authenticate every third-party sender by merging its include into your one SPF record and publishing its DKIM.
5. Keep your list clean and your content honest: drop hard bounces, honor unsubscribes, and skip the spammy subject lines.
6. Test before every big send by mailing yourself and confirming spf=pass, dkim=pass, and dmarc=pass in the headers.

Last updated July 2026 · Browse all Email and Webmail articles