Why are my business emails going to spam?
Summary
This guide helps you troubleshoot and resolve: Why are my business emails going to spam?. Follow the steps below to fix the issue.
Common Causes
Email authentication is the process of proving to receiving mail servers that an email sent from your domain is legitimate and not forged. When SPF, DKIM, or DMARC records are missing or incorrectly configured, your outgoing messages are more likely to be flagged as spam or rejected entirely by providers such as Gmail, Outlook, and Yahoo.
Determine Where Your DNS Is Hosted
Before making changes, you must identify where your DNS zone is managed. DNS records may be hosted at your domain registrar or with a third-party DNS provider. Changes made in the wrong location will not take effect.
- Use a WHOIS lookup tool to check your domain's name servers.
- If the name servers point to your registrar (for example, VentraIP or Conetix), log in to your registrar account and use their DNS manager or zone editor.
- If the name servers point to a third party (such as Cloudflare or another hosting provider), log in to that provider's control panel to manage DNS records.
- If you are unsure where your DNS is hosted, contact your IT provider or domain registrar for clarification.
If your MSP manages your DNS on your behalf, do not attempt to edit records yourself. Open a Ticket and request the specific SPF, DKIM, and DMARC values for your email environment.
Quick Fix Steps
- Log in to the control panel where your DNS is hosted (registrar or third-party DNS provider).
- Locate the DNS management, DNS zone, or zone editor section for your business domain.
- Check for existing TXT records related to SPF, DKIM, and DMARC.
- Add or update any missing records using the exact values provided by your email service provider.
- Save the changes and allow time for DNS propagation. This can vary based on TTL settings and may take up to 48 hours.
- Send a test email to an external address to verify delivery.
Detailed Instructions
Checking SPF Records
Sender Policy Framework (SPF) tells receiving servers which mail servers are authorised to send email on behalf of your domain. An SPF record is published as a TXT record in your DNS.
- Open your DNS control panel and select your domain.
- Look for a TXT record that begins with
v=spf1. - If no SPF record exists, create a new TXT record. Use the hostname
@or leave it blank, depending on your DNS provider. - Enter the SPF value provided by your email host. Examples include:
- Microsoft 365:
v=spf1 include:spf.protection.outlook.com -all - Google Workspace:
v=spf1 include:_spf.google.com ~all - cPanel/Conetix/VentraIP email hosting: use the value provided in your hosting welcome email or control panel.
- Save the record.
Only one SPF record should exist per domain. If you use multiple email services, their mechanisms must be combined into a single SPF record rather than creating separate ones.
Checking DKIM Records
DomainKeys Identified Mail (DKIM) adds a digital signature to your outgoing emails, allowing the recipient to verify that the message was not altered in transit.
Microsoft 365
- Sign in to the Microsoft 365 admin center.
- Go to Setup > Domains, then select your domain.
- Choose DNS records and look for the DKIM CNAME records provided by Microsoft.
- Copy these values into your DNS control panel as CNAME records.
- Return to the Microsoft 365 admin center, go to Exchange admin center > Protection > DKIM, select your domain, and choose Enable.
Google Workspace
- Sign in to the Google Workspace admin console.
- Go to Apps > Google Workspace > Gmail > Authenticate email.
- Select your domain and choose Generate new record.
- Copy the generated TXT record values (selector and public key) into your DNS control panel.
- Choose Start authentication in the admin console.
cPanel, Conetix, and VentraIP
- Log in to your hosting control panel (cPanel or provider-specific dashboard).
- Open the Email Deliverability or Authentication section.
- Select Enable DKIM or Generate DKIM key.
- Copy the displayed TXT record name and value into your DNS zone editor.
- Save the changes.
Checking DMARC Records
Domain-based Message Authentication, Reporting, and Conformance (DMARC) tells receiving servers how to handle emails that fail SPF or DKIM checks. It also enables reporting so you can monitor authentication failures.
- In your DNS control panel, create a new TXT record.
- Set the host name to
_dmarc. - Enter a DMARC policy value. A basic starting point is
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com.au, replacing the email address with one you monitor. - Save the record.
Setting a DMARC policy of p=reject before confirming that SPF and DKIM are working correctly can cause legitimate emails to be rejected. Start with p=none and move to stricter policies only after testing.
Email Content and Spam Triggers
Even with correct authentication, email content can trigger spam filters. Review the following before sending business emails:
- Avoid excessive use of capital letters, exclamation marks, and spammy subject lines such as "URGENT" or "ACT NOW".
- Limit the number of attachments and large files. Use secure file-sharing links instead where appropriate.
- Ensure links in your email point to reputable domains and use HTTPS.
- Maintain a reasonable balance of text and images. Emails that are entirely images or contain many images with little text may be flagged.
- Include a physical business address and a clear unsubscribe option in marketing or bulk emails.
IP Reputation and Shared Sending IPs
Your sending IP address has a reputation independent of your domain. If you use shared hosting or a shared email server, other customers on the same IP can affect your deliverability if they send spam.
- Check if your sending IP is listed on email blacklists (RBLs) using a multi-RBL lookup tool.
- If your IP is blacklisted, follow the delisting process provided by the blacklist operator.
- If you send high volumes of email, consider a dedicated IP address to isolate your reputation from other senders.
- For new domains or new IP addresses, implement a warm-up procedure by gradually increasing sending volume over several weeks rather than sending large campaigns immediately.
Reverse DNS (PTR) Records
Reverse DNS, or PTR records, map an IP address back to a hostname. Many receiving mail servers check PTR records to verify that the sending IP matches the domain claiming to send the email.
- PTR records are managed by the owner of the IP address, typically your hosting provider or ISP, not your domain registrar.
- If you send email from a dedicated server or VPS, request that your hosting provider configure a PTR record for your mail server IP pointing to your mail hostname (for example,
mail.yourdomain.com.au). - Shared hosting customers usually cannot manage PTR records directly and should ask their provider to confirm reverse DNS is configured.
Email Forwarding and SPF
Email forwarding can break SPF authentication. When a message is forwarded, the forwarding server becomes the new sender from the perspective of the final recipient. If the forwarding server is not included in your SPF record, the forwarded message may fail SPF and be marked as spam.
- Avoid automatic forwarding of business email to external addresses where possible.
- If forwarding is required, use SRS (Sender Rewriting Scheme) if your email platform supports it.
- Encourage recipients to add your domain to their safe senders list to reduce the impact of forwarded-message failures.
Testing and Monitoring
Pre-Send Testing
Before sending important campaigns or after making DNS changes, use a deliverability testing tool to check your email configuration.
- Visit mail-tester.com or a similar service.
- Send a test email to the address provided by the tool.
- Review the report for SPF, DKIM, DMARC, content, and blacklist issues.
- Address any warnings before sending to your full recipient list.
Interpreting Message Headers
If a recipient receives your email in their spam folder, ask them to share the message headers. Authentication results are often recorded in headers such as:
Authentication-ResultsReceived-SPFDKIM-Signature
Look for pass, fail, softfail, or neutral results. A fail or softfail indicates your SPF or DKIM records need correction.
DMARC Report Monitoring
DMARC aggregate reports (RUA) provide data on how receiving servers handle messages from your domain. Monitor these reports to identify unauthorised senders and authentication failures.
- Ensure your DMARC record includes a
ruaaddress pointing to an inbox you check regularly. - Reports are typically sent as XML files. Use a DMARC report analyser service to interpret the data.
- Gradually move from
p=nonetop=quarantineand thenp=rejectas you confirm legitimate mail is passing authentication.
Troubleshooting
Emails still going to spam after adding records
- Wait for DNS changes to propagate. Propagation time varies by TTL settings and can take up to 48 hours.
- Use a free online DNS lookup tool to confirm your SPF, DKIM, and DMARC records are publicly visible.
- Check that there are no typos in your record values, especially extra spaces or missing punctuation.
- Review the message headers of a received email to see authentication results from the receiving provider.
- Check if your domain or sending IP appears on email blacklists.
- Review email content for spam triggers such as attachments, links, and subject lines.
Receiving bounce-back messages (NDRs)
- Read the non-delivery report carefully. It often states whether the message was blocked due to authentication failure, sender reputation, or content filtering.
- Confirm that the recipient address is correct and that the recipient's mailbox is not full.
- If the error mentions your domain's reputation, ask the recipient to add your address to their safe senders list.
BIMI and Brand Indicators
Brand Indicators for Message Identification (BIMI) is an optional standard that allows your organisation's logo to appear next to authenticated emails in supporting inboxes. BIMI requires a strict DMARC policy (typically p=quarantine or p=reject) and a verified logo certificate. It is not required for basic deliverability but may improve brand recognition and trust.
If you manage your own DNS through a third-party registrar, these changes must be made there—not within your email client or email administration console alone.
If you have verified your DNS records, checked your content and IP reputation, and outgoing emails are still being marked as spam, you may need to investigate other delivery issues. For further assistance, Open a Ticket.
Still Having Issues?
💻 Open a Ticket