Mailgun sends the API calls. Your domain still has to earn the inbox.
Mailgun warms dedicated IPs automatically, but its own guidance says a new domain will most likely need warming itself. Keep sending through the Mailgun API or SMTP exactly as you do now. Add your brand domain here and we build its reputation while Mailgun keeps sending.
Keep sending from Mailgun. Warm the domain here.
Add and verify your own domain in Mailgun
Every account starts with a sandbox domain that is for testing only and delivers just to Authorized Recipients. Real sending needs your own domain, verified with the SPF and DKIM TXT records shown in the control panel. Until they verify, Mailgun holds the domain to a daily sending cap.
Know what Mailgun warms, and what it does not
Automatic IP Warmup raises the limits on a dedicated IP in stages and rolls the overflow onto your other IPs. It warms the IP. Mailgun’s own guide says domain reputation is separate and a new domain will most likely need warming itself, and each Mailgun domain, subdomains included, gets its own DKIM authority.
Add your brand domain to Inbox Boost
Use the domain in your From address, such as yourapp.com. The sending subdomain Mailgun uses, such as mg.yourapp.com, stays with Mailgun. We set up what the domain needs and build its sender reputation for you. Nothing to connect to Mailgun: no API key, no webhook, no change to your account.
Keep every API call and SMTP send on Mailgun
Password resets, receipts, notifications: all of it stays on Mailgun. Mailbox providers score the domain in your From address, so the reputation built here counts for every Mailgun send from yourapp.com.
Check where Mailgun mail lands
Inbox placement tests show whether your application mail reaches the inbox or Spam across the major mailbox providers, and blacklist monitoring keeps watching the domain once it is warm.
- Nothing to connect: no Mailgun API key, webhook or integration
- Nothing to change: your code, SMTP credentials and templates stay exactly as they are
- Shared or dedicated IP: it works either way, because the reputation belongs to the domain
- Watched after warmup: blacklist and authentication monitoring on your brand domain
The parts of the platform this plan leans on.
A Mailgun domain, warmed without pausing a single send.
Four checkpoints, in order. Click any step or let it play.
Mailgun questions, answered.
Does Inbox Boost connect to my Mailgun account?
Mailgun already warms dedicated IPs. Why warm the domain too?
I am on Mailgun’s shared IPs. Does this still help?
Should I add yourapp.com or mg.yourapp.com?
Can I see whether it is working?
Checked against Mailgun's own documentation on 12 October 2026. Mailgun is a trademark of its owner; SenderSignal is not affiliated with it.
Other transactional & smtp: Amazon SES, Postmark, SparkPost, Resend, Mailjet. All use cases.
Warm the domain behind your Mailgun mail.
Start free, add your brand domain, and keep every API call going to Mailgun while its reputation builds.