Quick answer
New domain emails go to Gmail spam because the domain may be technically valid but still unproven. First verify SPF, DKIM, DMARC alignment, public blacklist status, reverse DNS, TLS, and message-format basics. If those pass, the likely remaining issues are reputation history, volume ramp, recipient expectation, content, or Gmail-private signals.
A new domain can be valid and still untrusted
Correct DNS does not create sending reputation by itself. SPF, DKIM, and DMARC help Gmail authenticate the message. Reputation is built from sending behavior, recipient response, complaint patterns, volume history, and provider-specific signals.
That gap is why new domains feel confusing. A domain can pass every public authentication check and still lack enough positive history for Gmail to treat a campaign as normal. The technical baseline is necessary. It is not the whole delivery system.
Use the public checks first because they are deterministic. If a new domain has broken SPF, disabled DKIM, missing DMARC, or a public blacklist listing, fix that before discussing warmup or content.
Verify authentication before ramping volume
Google's sender guidelines require authentication for senders to personal Gmail accounts and describe stricter requirements for higher-volume senders. The public baseline is SPF, DKIM, and DMARC alignment.
SPF, defined in RFC 7208, should authorize the real outbound platform. If the new domain sends through Google Workspace, Microsoft 365, Postmark, SendGrid, Mailgun, a CRM, or a newsletter tool, those paths need to be represented correctly.
DKIM, defined in RFC 6376, must be enabled in the sending platform, not only published in DNS. A DNS key without real message signing will not help Gmail authenticate that message.
DMARC, defined in RFC 7489, requires alignment with the visible From domain. New domains often fail here when an ESP signs with its own domain or uses a non-aligned return path.
Do not ramp volume until a real Gmail header shows the new domain passing the intended authentication path.
Treat launch timing as evidence
If Gmail spam placement started right after a domain launch, ESP migration, DNS migration, IP change, subdomain change, or first large campaign, the timing is evidence.
Google's sender FAQ treats new domains as a distinct enforcement context for bulk-sender requirements. That does not mean every new domain is automatically untrusted, and it does not give public tools a way to read Gmail reputation. It means launch timing belongs in the diagnosis instead of being ignored after DNS passes.
The domain may be sending more mail than it ever has before. It may be using new DKIM selectors, new tracking domains, new return-path domains, or new shared IPs. It may also be sending to people who have not recently engaged with the brand.
Public DNS checks tell you whether the new setup is broken. They do not prove Gmail has enough positive history for the new setup.
Separate transactional, lifecycle, newsletter, and outreach mail
New domains get into trouble when all message types share one reputation path. Transactional mail, product updates, newsletters, sales outreach, and cold campaigns have different risk profiles.
If a cold outreach campaign damages reputation, it can affect more valuable operational mail that uses the same domain or infrastructure. If a newsletter list is old or weakly opted in, it can create complaint and engagement signals that authentication cannot offset.
The route recommendation is conservative: use the main domain for expected operational mail, use clearly named subdomains only when you understand the reputation tradeoff, and do not mix cold outreach with critical transactional streams.
Relaymetry cannot design the sending architecture for you, but it can show whether the public DNS/authentication layer is coherent before you scale a stream.
Check PTR and TLS when you control the sending server
Google's sender guidelines include valid forward and reverse DNS for sending domains or IPs, plus TLS for mail transmission. These are infrastructure requirements, not content tricks.
For PTR, the important IP is the actual SMTP sending IP. If you use an ESP, that may be outside your direct control. If you run your own mail server, confirm the PTR hostname and forward A/AAAA relationship for the sending IP, not just the website host.
For TLS, a public inbound TLS check is useful for domain health, but it does not prove that one outbound delivery attempt to Gmail used TLS. If Gmail reports a TLS-related failure, keep the bounce text and inspect the sending platform's SMTP logs.
Use Postmaster Tools after public checks are clean
Postmaster Tools can show Gmail-specific data after setup and verification, including spam-rate and reputation-related dashboards when data is available for messages to personal Gmail accounts.
For a brand-new or low-volume domain, Postmaster Tools may not immediately give a useful answer. Lack of visible data is not the same as a clean reputation signal. It may simply mean the domain does not have enough Gmail traffic for the dashboard to be informative.
The best sequence is: public technical baseline first, then real Gmail headers, then Postmaster Tools, then volume/content/list review.
What this does not prove
Relaymetry can prove whether public DNS and SMTP-facing signals look correct from the outside. It cannot prove that Gmail trusts a new domain, that recipients want the messages, or that a ramp plan is safe.
No public checker can guarantee inbox placement for a new domain. A clean report means you have removed obvious public technical failures. It does not create sender history, engagement, or positive reputation.
FAQ
How long does it take for a new domain to stop going to Gmail spam?
There is no public fixed timeline. It depends on sending volume, recipient engagement, complaints, content, infrastructure, and Gmail's private reputation signals.
Should I send more mail to build reputation faster?
Not blindly. Sudden volume can make a new domain look riskier. Send expected mail to engaged recipients first, and avoid large cold or stale-list sends while reputation is weak.
Can a new domain go to spam with perfect SPF, DKIM, and DMARC?
Yes. Authentication proves identity and alignment. It does not prove sender reputation or recipient interest.
Should I use a new subdomain for marketing mail?
Sometimes, but it is not a magic fix. A subdomain can separate risk, but it still needs correct authentication and its own positive sending history.
Does Postmaster Tools work for a low-volume new domain?
It may have limited or no useful dashboard data until there is enough Gmail traffic. Use it when available, but do not skip public SPF, DKIM, DMARC, blacklist, PTR, and TLS checks.
Related guides
- Why Gmail rejects emails — full pillar diagnostic
- SPF, DKIM, and DMARC pass but Gmail sends email to spam — analytical companion
- Gmail 5.7.26 error: unauthenticated mail — SMTP rejection code playbook
- SPF Checker
- DKIM Checker
- DMARC Checker
- Blacklist Lookup — public blocklist check
- TLS Check