New Domain? How to Get Your First Emails Delivered

You bought a domain, set up hello@yourbusiness.com and sent your first emails. Then a client says they never got your quote, or it turns up in their spam folder. Usually nothing is broken. Your domain just has no history yet.

Why a new domain starts with no trust

Gmail, Outlook and Yahoo decide where an email lands partly by the sender's reputation. Does the domain prove who it is? Do people open, reply or report it as spam? Is its sending steady? A new domain has no answers to any of these questions. It isn't penalised, it's unknown, and unknown senders get a closer look, especially if they suddenly send a lot.

The good news: reputation builds quickly when your first emails go to people who expect them.

Step 1: Set up SPF, DKIM and DMARC before your first email

SPF lists the servers allowed to send email for your domain. Every service that sends as you must be in it: your mailbox, your newsletter tool, your invoicing software, your app. A domain can have only one SPF record.
DKIM signs each email so the receiver can check it really came from you and wasn't changed on the way. Turn it on in every service that sends for you.
DMARC tells receivers what to do with an email that fails those checks and, if the record includes a reporting address (rua), receivers send you reports. Starting at p=none is normal: nothing gets blocked, and you read the reports. Once all your real senders pass, move to p=quarantine, then p=reject.

Since 2024, Gmail and Yahoo require every sender to authenticate their email, and bulk senders to have SPF, DKIM and DMARC. Setting them up on day one means you never have to repair a bad start.

Step 2: Keep everyday email and bulk email apart

Your one-to-one email (replies to clients, quotes, invoices) is your most valuable mail. Newsletters, app notifications and announcements are riskier: more volume, and more people who ignore them.

Many businesses send that second kind through a dedicated sending service on a subdomain, such as news.yourbusiness.com or send.yourbusiness.com. Bulk sending is then easier to monitor on its own, and a campaign that goes wrong is less likely to drag down the mailbox you use with clients. Each sending service needs its own SPF and DKIM setup.

Step 3: Start small, with people who know you

Make your first emails real conversations with clients, partners and people likely to reply. Replies are one of the strongest good signals.
Increase your volume gradually. Going from zero to thousands of emails in one day is a classic spam pattern.
Never send to bought or scraped lists.
Avoid link shorteners, emails that are just one big image, and attachments in a first message.
Use the same sender name and address every time.

Step 4: Handle your first big send with care

Waitlists, pre-orders, event sign-ups: the riskiest moment is often the first big email. Months may have passed, people forget they signed up, and a forgotten sign-up looks like spam.

Say who you are and why they're getting this in the first line: "You joined the waitlist for X in June."
Use a sender name people will recognise.
Include a one-click unsubscribe link. Gmail and Yahoo require one from bulk senders, and an unsubscribe is far better for you than a spam report.
Send in batches over a few hours or days, starting with the most recent sign-ups. Check bounces and complaints before the next batch.
Keep fake addresses off the list from the start. A bot check on the sign-up form stops automated sign-ups. A confirmation email (double opt-in) proves each address is real, at the cost of one more email.

A real example: a launch on a brand-new domain

ClipClip is made by the same founder as this site. ClipClip for Roblox, a marketing platform for Roblox games, is launching soon on a brand-new domain, clipclip.io. Its email setup follows the steps above:

Everything goes out from its own domain: a mailbox for support@clipclip.io, and a separate sending service for the app's emails, with its bounce address on its own subdomain, send.clipclip.io.
Both had SPF and DKIM from day one. The domain has a DMARC record, at p=none for now.
The waitlist sends no confirmation email. A Cloudflare bot check on the sign-up box keeps fake sign-ups off the list. The list gets one email, at launch, with a one-click unsubscribe link.

That last choice has a consequence: the launch email will be the first email most people on the list ever get from clipclip.io. That's exactly the situation Step 4 is for.

Step 5: Check, then keep checking

Send a test to Gmail and Outlook addresses you own. In Gmail, open "Show original" to see whether SPF, DKIM and DMARC say PASS.
Once you send enough email to Gmail users, Google Postmaster Tools shows your spam rate and how your domain is doing.
If emails suddenly start bouncing, check blocklists such as Spamhaus.
Read your DMARC reports, and tighten the policy once everything passes.
Watch spam reports. Gmail asks bulk senders to stay under 0.3% and recommends under 0.1%.

In short

Set up authentication before your first email, keep bulk email apart from your everyday mailbox, start small, and treat your first big send as the moment that sets your reputation.

If you'd rather not touch DNS at all, Shipmailer sets up SPF, DKIM and DMARC on every plan. More in SPF, DKIM and DMARC explained.