惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
The Last Watchdog
The Last Watchdog
TaoSecurity Blog
TaoSecurity Blog
PCI Perspectives
PCI Perspectives
L
LINUX DO - 最新话题
H
Heimdal Security Blog
S
Security Archives - TechRepublic
www.infosecurity-magazine.com
www.infosecurity-magazine.com
T
Troy Hunt's Blog
SecWiki News
SecWiki News
S
Secure Thoughts
The Cloudflare Blog
Last Week in AI
Last Week in AI
Google DeepMind News
Google DeepMind News
Attack and Defense Labs
Attack and Defense Labs
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
量子位
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
V
Visual Studio Blog
N
News and Events Feed by Topic
E
Exploit-DB.com RSS Feed
博客园 - Franky
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
酷 壳 – CoolShell
酷 壳 – CoolShell
Know Your Adversary
Know Your Adversary
M
MIT News - Artificial intelligence
V
V2EX
Webroot Blog
Webroot Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
Cyberwarzone
Cyberwarzone
博客园 - 【当耐特】
月光博客
月光博客
Y
Y Combinator Blog
B
Blog RSS Feed
Recent Announcements
Recent Announcements
S
Schneier on Security
H
Hacker News: Front Page
Stack Overflow Blog
Stack Overflow Blog
NISL@THU
NISL@THU
小众软件
小众软件
雷峰网
雷峰网
P
Privacy International News Feed
腾讯CDC
大猫的无限游戏
大猫的无限游戏
博客园 - 叶小钗
C
Cyber Attacks, Cyber Crime and Cyber Security
V
Vulnerabilities – Threatpost
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
News and Events Feed by Topic

Resend RSS Feed

6 Tips for Accessible Emails Welcoming Manoel do Amaral, our new Brand Designer Welcoming Michael Vaz, our new Customer Success Engineer Six Steps to Improve Your Sender Reputation Welcoming Tatira Andrade, our new Executive Assistant Welcoming Pedro Ivo Hudson, our new Design Engineer Welcoming Diel Duarte, our new Open source Engineer Welcoming Areia Spinner, our new Recruiter Resend Forward: A Conference about Craft React Email 6.0 Custom Tracking Domains AI Email Editor Introducing Automations Welcoming Ahmed Tolba, our new SRE Engineer Welcoming Aneil Singh, our new Founding Account Executive Welcoming Lucas Motta, our new Software Engineer Welcoming Trey Knowles, our new Founding Account Executive Welcoming Anxhela Carciu, our new SRE Engineer Introducing DMARC Analyzer Welcoming Evan Thibodeau, our new Customer Success Engineer Welcoming Derich Pacheco, our new Software Engineer Welcoming Alec Ventura, our new Data Engineer Welcoming Felipe Freitag, our new Software Engineer Welcoming Mateusz Wos, our new Software Engineer Incident report for February 15, 2026 Email automation for OpenClaw How to Create a DevTools Agent Skill Introducing Email Skills Why You Should Embrace the Promotions Tab Slater Smith, our new Customer Success Engineer Do You Need a Warmup Service? Welcoming Zá Scalon, our new Brand Designer How Replit Built Effortless Email Sending Features 1,000,000 users Top 10 new features in 2025 Welcoming Danilo Campos, our new Design Engineer How Dub Uses Webhooks to Power Features Incident report for November 18, 2025 Resend Forward 5: Wrap Up One More (AI) Thing React Email 5.0 Unsubscribe Topics New Contacts Experience Introducing Templates Inbound Emails $3M to Make Email Safer Hacktoberfest 2025 Four Ways to Hurt Your Sender Reputation Resend MCP Hackathon Welcoming Christina Martinez, our new Developer Experience Engineer How to read a DMARC report Welcoming Erin Levine, our new Chief of Staff How to Validate Form Inputs Engineering an AI App Welcoming Lucas da Costa, our new Software Engineer Welcoming Lucas Vieira, our new Software Engineer Resend acquires Briefer How Raycast Modernized their Email Sending How to Get Email Consent DMARC Policy Modes Welcoming Gabriel Miranda, our new Software Engineer Rebranding Resend The 7 Best Email Verification APIs for Developers How DMARC Applies to Subdomains Welcoming Pedro Gomes, our new Software Engineer Do You Need a Dedicated IP? The 6 best notification infrastructure services The Fixer Why Your Emails are Going to Spam Engineering Idempotency Keys Microsoft’s bulk sending requirements for 2025 Welcoming Rehan van der Merwe, our new Devops Engineer 400,000 users and beyond Welcoming Cassio Zen, our new Software Engineer Resend acquires Mergent Welcoming Carolina Josephik, our new Software Engineer Launch Week: Behind the Scenes Welcoming Isabella Aquino, our new Software Engineer Resend Forward 4: Wrap Up React Email 4.0 Multiplayer Editor Broadcast API Multiple Teams new.email Public Launch Welcoming Anna Ward, our new Postmaster How Gumroad Migrated 100M Emails to Resend Welcoming João Melo, our new Software Engineer Welcoming Jp Valery, our new Customer Success Engineer What is AX (Agent Experience) and how to improve it Welcoming Pauline Chin, our new Customer Success Engineer Introducing new.email How we use Friction Logs to improve the product Top 10 Email Deliverability Tips Welcoming Giovana Yahiro, our new Designer Engineer What BIMI's Changes Mean for Email Top 10 new features in 2024 Design Engineering an X Component Welcoming Alexandre Cisneiros, our new Software Engineer Resend raises $18M Series A Welcoming Danilo Woznica, our new Designer Engineer
How to warm up a new domain
Jp Valery · 2025-04-18 · via Resend RSS Feed

When you start sending emails from a brand-new domain, you have to prove to inbox service providers that you're not a spammer.

As we launched our new product, new.email, a specialty-trained LLM that helps create email templates, we needed a plan to warm up this new domain.

Why do we have to warm up a domain?

When a domain with no sending history suddenly starts blasting out emails, inbox providers take notice.

Since they prioritize protecting their users from spam, they’ll often take a cautious approach, closely monitoring engagement signals like opens, clicks, and spam complaints.

If they don’t see positive engagement—or worse, if users start marking your emails as spam—your domain’s reputation takes a hit, making it harder or impossible for your emails to reach the inbox.

Think of it like building credit. At first, lenders don’t know if they can trust you, so you have to start small and establish reliability over time. Without this reputation, inbox providers might slow down your deliveries, send your emails straight to spam, or even block them entirely.

Since this is a topic that often concerns our customers, we wanted to transparently share our own experience warming up a domain that was critical to our business.

This guide focuses on brand-new domains. If you’re working with an existing domain, we also have some general best practices that apply to both new and established senders.

What key questions should you ask?

Every good plan starts with a clear goal. The easiest way to approach domain warm-up is to work backwards from your target goals by asking key questions.

  1. What volume will you be sending?
  2. When do you need your reputation established?
  3. Which subdomains to use?

Let's break down each of these.

1. What volume will you be sending?

For new.email, we planned to send at least three types of emails in varying volumes:

  • account-related emails like signups and password resets
  • in-app emails that users could generate and send to themselves
  • marketing emails to our waitlist

We had an ever-growing waitlist, which meant a potential surge in volume for each type as new users gained access to the platform. In all, we wanted to plan on having capacity to send thousands of emails per day.

2. When do you need your reputation established?

Our goal was to launch new.email on March 24.

Based on our experience and the expected email volume, we aimed for a six-week ramp-up period (starting on February 11) to gradually increase volume while staying within safe thresholds that inbox providers expect to see from new senders.

Generally speaking, the larger your target volume, the longer you should plan for warm-up. Since we were using an invite-based model, our initial volume was naturally small and gradually increased—perfectly mimicking an organic warm-up schedule.

3. Which subdomains to use?

We followed a best practice we always recommend: separating transactional, marketing, and product-generated emails onto different domains.

Subdomains help protect deliverability by ensuring that issues with one type of email (e.g., marketing campaigns) don’t negatively impact critical transactional emails.

In one way, however, this added a bit of complexity to our warm-up plan. We needed to warm up three domains instead of just one. Also, brand-new domains—those registered only recently—often face even more scrutiny because spammers frequently buy fresh domains and burn them out quickly.

What strategies should you pursue?

Once you know your target volume and timeline, the next step is figuring out how to actually start sending emails from your new domains in a way that looks natural to inbox providers. Here’s what we did.

  1. Use a double opt-in form
  2. Use multiple subdomains
  3. Gradually increase sending volume

1. Use a double opt-in form

To ensure that our first emails were landing in engaged inboxes, we made our early access signups double opt-in. This meant that when someone signed up, they received an email asking them to confirm their address before being added to our list.

This approach provided multiple benefits.

  1. It eliminated fake or mistyped email addresses, keeping our list clean.
  2. It ensured that every recipient was a real person who wanted to hear from us—exactly the kind of engagement signals inbox providers look for when evaluating a new sender.
  3. We added email validation to prevent invalid or risky addresses from signing up in the first place, reducing the likelihood of bounces.

If you want to learn more about keeping your email list clean, check out our guide on Audience Hygiene.

2. Use multiple subdomains

As mentioned earlier, we split our sending across multiple subdomains:

  • one for transactional emails
  • one for marketing
  • one for product-generated messages

This wasn’t just for organization—it was a deliberate strategy to protect our reputation. If marketing emails ever ran into deliverability issues, our critical transactional messages wouldn’t be affected.

Inbox providers evaluate sending reputation at the domain and subdomain level. By keeping different email types separate, we reduced the risk of a single problem affecting all our emails. This setup did add complexity to our warm-up plan, but it was well worth it for long-term deliverability.

3. Gradually increase sending volume

We started with extremely small volumes and increased gradually. Initially, we invited early users via DMs on 𝕏 (formerly Twitter) to keep volume low and controlled.

As our warm-up progressed, we began sending marketing emails in progressively larger batches, focusing first on our most engaged audiences.

At the same time, every new account triggered a confirmation email, steadily increasing our transactional volume in a natural way.

How you can prepare

If you're planning to warm up a new domain, here’s a simple checklist to follow:

  1. Plan your target sending volume.
  2. Set a clear deadline for when you need your reputation established.
  3. Verify your domains as early as possible.
  4. Make sure you’re sending to high-quality, engaged recipients.
  5. Increase your sending volume gradually over time.
  6. Monitor your deliverability metrics and adjust as needed.

Warming up a domain is a process, but it pays off by ensuring your emails reliably land in inboxes instead of spam folders. If you take the time to do it right, you’ll build a strong sender reputation that serves you well in the long run.