Verify Sending Domain in Mailgun

Why domain verification in Mailgun is critical for inbox placement

Ever sent a batch of emails only to watch them vanish into Gmail’s spam folder—or worse, never arrive at all? It’s not always your content. More often, it’s the sender identity you never verified properly.

Mailgun won’t authenticate your emails without correct domain setup. That means no SPF, DKIM, or DMARC—just a signal to providers like Gmail and Outlook that you can’t be trusted. The result? High bounce rates, blocked inboxes, and a damaged sender reputation, all from one misconfigured DNS record.

Key takeaways

Domain verification in Mailgun enables SPF, DKIM, and DMARC—required for inbox placement by major providers.
A single missing or incorrect DNS record can trigger filtering or outright blocking by Gmail, Microsoft, and others.
Without verification, Mailgun cannot prove your emails come from your domain, leading to high bounce rates and poor deliverability.

What happens if you skip domain verification in Mailgun?

Skipping domain verification in Mailgun means your emails are sent without proper authentication, making them vulnerable to rejection, spam filtering, or complete delivery failure—even if your content is clean. Receiving servers use SPF, DKIM, and DMARC to validate senders, and without them, your messages are treated as untrusted by default. This harms inbox placement and damages sender reputation fast.

How unauthenticated mail gets blocked or flagged

Receiving servers like Gmail and Yahoo use DMARC policies: if your domain lacks valid SPF or DKIM records, your emails may be marked as spam or rejected outright.
Even with a clean message, lack of authentication means your sending reputation isn’t verified—some providers will not process your mail at all, resulting in 100% bounce rates from major inboxes.
Studies from industry sources like RFC 7001 show that unauthenticated emails have significantly higher rejection rates, especially at large ISPs that enforce strict policies.

What happens to your sender reputation

Your sender reputation is built on consistent, authenticated mail. Sending from an unverified domain gives no feedback loop—there’s no way for receiving servers to trust your messages.
Spam traps, feedback loops, and abuse reports can all damage your reputation. With no authentication, recovery can take weeks or months, even after fixing records.
Once an IP or domain is flagged by major blocklists like Spamhaus, removing it requires effort, time, and a track record of clean, verified sending—something hard to rebuild after skipping verification.

Let’s be clear: skipping verification isn’t a shortcut—it’s a setup for delivery failure. The technical foundation of email deliverability is sender authentication. If you're using Mailgun, setting up SPF, DKIM, and DMARC isn’t optional. It’s how you prove you’re not a spammer.

For teams doing bulk sending, running a real-time email verification check before sending can prevent many of these issues. Use a tool like MailTester’s bulk verification to clean your list and catch invalid or risky addresses before they harm your sender reputation.

How to verify your sending domain in Mailgun: a step-by-step process

You verify your sending domain in Mailgun by logging in, navigating to the Domains section, selecting your domain, and then adding the DNS records (SPF, DKIM, DMARC) Mailgun provides. Once those records are live on your DNS provider’s system, wait 10–30 minutes for propagation, then recheck in Mailgun. Once confirmed, your domain is authenticated, which improves inbox placement and sender reputation. No verification means higher risk of being flagged or blocked.

Set up domain authentication with Mailgun

Log in to your Mailgun control panel and go to the Domains section under Settings. This is where you manage all domains tied to your outbound mail.
Select the domain you want to verify and click the Verify Domain button. Mailgun will then generate the exact DNS records you need to publish.
Copy the SPF, DKIM, and DMARC records from the verification screen. These records tell receiving servers how to verify your emails are legitimate. Without them, your messages may be rejected.
Go to your domain’s DNS provider (Cloudflare, GoDaddy, AWS Route 53, etc.) and add these records as TXT or CNAME entries. Be precise—any typo will break authentication.
Wait 10–30 minutes after DNS changes are published. DNS propagation time varies, but most providers update within this window. Avoid rechecking too early.
Return to Mailgun and recheck verification status. If successful, the UI will show “Verified” with a green checkmark. If not, double-check your DNS records for formatting or typos.

Why this matters for inbox placement

Domain authentication isn’t just a formality. It’s a core part of email deliverability. According to research from Return Path, unauthenticated domains see inbox placement rates 20–30% lower than authenticated ones. That’s not a minor difference—it means real emails ending up in junk folders.

The 6 steps described in “Set up domain authentication with Mailgun”, in order.

Once your domain is verified, your messages can carry proper authentication signals. Receiving servers use SPF and DKIM alignment, and DMARC policies to decide whether to accept or block email. A verified domain shows you’re not spoofing, which builds trust. Over time, this helps your sender reputation stay healthy.

If you’re building or cleaning a mailing list, consider checking individual addresses before sending. Tools like MailTester offer email verification to catch invalid or risky addresses early. You can run a bulk list verification, test deliverability with inbox placement tools, or integrate verification into your workflow using the API. Verify your list in bulk to reduce bounces and protect your sender reputation before launching campaigns.

The role of SPF, DKIM, and DMARC in Mailgun authentication

You need SPF, DKIM, and DMARC to verify your sending domain in Mailgun because they collectively prove your identity to receiving servers, reduce spam filtering, and improve inbox placement. SPF authorizes specific mail servers, DKIM cryptographically signs each message, and DMARC defines policy for unauthenticated emails and enables visibility into delivery issues. Together, they form the foundation of email authentication — a must for any sender using Mailgun at scale.

How each protocol works in practice

SPF acts like a whitelist: it tells receiving servers which IP addresses or domains are allowed to send emails on your behalf. Without it, Mailgun’s outbound traffic may be flagged as suspicious.

DKIM adds a digital signature to each email header and body. It verifies that the message hasn’t been altered in transit and confirms the sender’s domain ownership — a key trust signal for inbox providers.

DMARC ties the other two together. It tells receivers what to do with emails that fail SPF or DKIM checks (e.g., quarantine or reject) and provides feedback reports — helping you detect spoofing or misconfigurations.

Authentication alignment table

Protocol	What it does	How it helps in Mailgun	Reference
SPF	Specifies authorized sending servers for your domain	Prevents spoofing, reduces bounce rate from unauthorized sources	RFC 7208
DKIM	Applies a cryptographic signature to each email	Confirms message integrity; improves trust with major ISPs	RFC 6376
DMARC	Defines handling policies for failed authentication and enables report sharing	Enables enforcement of SPF/DKIM, provides insights via aggregate reports	RFC 7489

These protocols don’t work in isolation. A misconfigured SPF can break DKIM alignment, and DMARC requires both to be effective. You can verify your domain’s authentication setup using tools like MailTester’s inbox placement tester, which checks whether your messages would pass authentication and reach inboxes consistently across providers.

How sender reputation impacts inbox placement in Mailgun

Mailgun uses sender reputation signals—like bounce rates, spam complaints, and invalid addresses—to decide if your emails land in inboxes or get filtered into spam. A weak reputation over time leads to gradual deliverability decline, even if your content is on-brand. You can prevent this by cleaning your list regularly and verifying your sending domain.

What affects your sender reputation in Mailgun

Mailgun evaluates your domain and IP reputation in real time. High bounce rates from invalid or non-existent addresses hurt your standing. So do spam complaints—each one signals poor list quality or unengaged recipients. Even sending to dormant or unverified addresses can signal low intent, making inbox placement harder.

Spam traps and role accounts (like sales@ or info@) also damage reputation. These addresses are monitored by email providers and often used as indicators of bad sending practices. Sending to them—especially at scale—can trigger filtering or blocklist placement. That’s why verifying your list before sending matters.

How domain verification and list hygiene protect your sender reputation

Verifying your sending domain in Mailgun is more than a setup step—it’s a trust signal. It proves you control the domain and aren’t spoofing someone else’s name. This step alone improves deliverability by reducing the chance of your emails being flagged as phishing or scam attempts.

But domain verification alone isn’t enough. A high-quality list is the real foundation. Invalid or fake addresses inevitably lead to bounces, which degrade reputation. Use tools like bulk email verification to scrub your list before sending. Real-time validation helps catch issues early, and inbox placement testing helps check how your message performs across different providers.

Industry standards—like RFC 5321 for SMTP and standards set by organizations like the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG)—emphasize that consistent sending behavior and clean lists are key to long-term deliverability. Tools that analyze reputation signals, like those used by Mailgun, rely on these same patterns. You’re not just sending emails—you’re building a track record.

Why you should test inbox placement even after domain verification

Domain verification in Mailgun ensures your server is authenticated, but it doesn’t guarantee your emails will land in inboxes. Even correctly configured domains can be filtered by Gmail, Outlook, or Yahoo based on sending patterns, content quality, or reputation history. You need to test real-world inbox placement to know if your messages are actually arriving where they should.

Authentication isn’t enough—reputation and behavior matter

Domain authentication (SPF, DKIM, DMARC) proves you’re authorized to send from that domain, but it doesn’t guarantee delivery. Email providers like Gmail evaluate your sending behavior daily—volume spikes, poor engagement, or content that triggers spam filters can reduce inbox placement, even with perfect alignment.

For example, a sudden influx of 10,000 emails from a domain with no prior sending history may look suspicious. Even if your DNS records are valid, providers may still place your messages in the spam folder or block them entirely. This is why ongoing monitoring and real-world testing are essential.

Simulate what real users experience

The only way to validate inbox delivery is to test how your emails appear in real email clients. Tools like MailTester’s inbox placement tester simulate delivery across Gmail, Outlook, and Yahoo using actual inboxes—giving you a true picture of how your messages are treated.

Let’s say you verify your domain in Mailgun, set up the correct records, and send a test email. You’re told “delivered” by the SMTP server—but that doesn’t mean it landed in the inbox. It might be stuck in spam, or even caught by greylisting. You need to know what happens after delivery.

Using a tool like MailTester’s inbox tester lets you check actual delivery outcomes across multiple providers. It shows whether messages appear in the primary inbox or get moved to spam, and gives you actionable feedback. This level of insight is missing from basic SMTP or DNS checks. It’s not just about sending—it’s about being received.

For continuous verification across your list, MailTester offers a bulk verification service that checks thousands of addresses at once, flagging invalid, risky, or disposable addresses before you send. You can also integrate this directly with Mailgun or other platforms via the real-time API for automated list hygiene.

Ultimately, authentication is just the first step. Inbox placement depends on behavior, content, and reputation. Test it. Verify it. Deliver reliably.

How to combine Mailgun with MailTester for better deliverability

You can improve inbox placement by validating new email addresses before sending through Mailgun using MailTester’s real-time API, cleaning bulk lists to remove invalid, disposable, and role-based emails that hurt sender reputation, and testing how your messages land in real inboxes with MailTester’s inbox-placement tool. This trio of steps reduces bounces, avoids spam traps, and gives you confidence your campaigns will reach real users.

Verify every new address in real time

When someone signs up, check their email address instantly with MailTester’s real-time verification API. It confirms validity, detects role accounts like info@ or sales@, and flags disposable domains before you send. This avoids sending to addresses that will bounce or are likely to be marked as spam.

Integrate the API directly into your signup workflow. It takes under 200ms per check and returns clear results: valid, catch-all, invalid, or risky. You’ll cut your bounce rate by up to 40% on new subscribers, depending on list quality.

Learn how real-time verification works in practice: test the API with real data.

Run bulk verification to clean your list

Even well-maintained lists degrade over time. Use MailTester’s bulk list verification to find and remove invalid, role-based, and disposable addresses in bulk. These types of addresses aren’t just dead weight—they harm your sender reputation, especially if they trigger bounces or spam complaints.

MailTester detects catch-all domains and identifies risky patterns like short-lived email providers. This helps you avoid being flagged by providers like Gmail or Outlook based on poor list hygiene. A clean list isn’t just about fewer bounces—it’s about building a reputation that earns inbox placement.

Check your current list hygiene: run a free bulk verification.

Test inbox placement before sending to real users

Even with a clean list and proper authentication, your message might not land in the inbox. MailTester’s inbox-placement tool sends test emails to Gmail, Yahoo, Outlook, and other major providers. It tells you whether your message lands in the primary inbox or gets filtered to clutter.

This tool shows you how your branding, content, and sending practices are perceived by inbox providers. If a message is marked as “Promotions” or “Social,” it’s not failing—just being routed differently. You can adjust your content and authentication settings to improve placement before scaling.

Test how your messages really land: run a real inbox test.

Combine Mailgun’s robust delivery with MailTester’s precise validation and deliverability testing. The result isn’t just better deliverability—it’s fewer wasted sends, a stronger sender reputation, and emails that actually reach the inbox. No guesswork. Just measurable results.

Best practices for maintaining domain verification and deliverability

You verify your sending domain in Mailgun to prove ownership and build trust with receiving servers. But verification alone isn’t enough. To maintain strong inbox placement, audit your DNS records monthly, avoid sending spikes, and monitor complaints and bounces in real time using feedback loops. These habits prevent reputation damage and keep your emails out of spam.

Keep DNS records intact and valid

Check your SPF, DKIM, and DMARC records every month using tools like MXToolbox or RFC 7208 (which defines SPF) to confirm they’re still in place and correctly formatted.
Accidental removals happen—especially after DNS changes. A missing or misconfigured record breaks authentication and can lead to inbox filtering.
Use MailTester’s email checker to verify that addresses from your domain pass basic syntax and domain validation before sending.

Stick to predictable sending patterns

Sudden jumps in volume—sending 10,000 emails in one hour when your usual rate is 1,000 per day—trigger suspicion from anti-spam systems.
Gradually scale your sending volume and keep consistent patterns over time. Mailgun’s throttling and monitoring tools can help you adjust based on real-time feedback.
If you’re using Mailgun with a list from a third party, validate the list with bulk verification first to remove dead, disposable, or invalid addresses. A cleaner list means fewer rejections and less strain on your sender reputation.
Set up Feedback Loops (FBLs) with major ISPs like Gmail, Yahoo, and Outlook to get real-time reports when users mark your emails as spam.
Monitor bounce and complaint rates through Mailgun’s delivery reports and your own analytics. A complaint rate above 0.1% signals trouble.
Act fast when complaints or hard bounces appear—remove addresses immediately and review sending practices.

Sender reputation is built over time. A single spike in complaints or bounces can erase months of progress.

How MailTester’s in-app AI assistant improves deliverability workflows

You can use MailTester’s in-app AI assistant to quickly understand why a domain or address is low-risk or high-risk, get plain-English explanations of technical issues like SPF failures or greylisting, and take immediate corrective actions—without leaving your Mailgun workflow.

Interpreting results with clarity, not confusion

Not every verification result is black or white. Some domains return “risky” or “catch-all” flags that don’t tell you what to do next. MailTester’s AI takes those ambiguous outcomes and breaks them down. It identifies whether a domain has weak authentication, if it’s prone to bounce loops, or if it’s linked to known spam patterns—then explains it in plain language.

Let’s say an address passes validation but shows low inbox placement in testing. The AI doesn’t just flag it. It says: “This domain has no DKIM signature, which lowers trust with providers like Gmail and Outlook.” You get the issue and the fix in one glance, saving hours of log diving.

Seamless integration into your Mailgun pipeline

MailTester works directly with Mailgun through its API and integrations, meaning you don’t have to switch tools. After verifying a list, you can analyze deliverability patterns in real time using the Inbox Tester. The AI automatically highlights trends—like why 22% of recipients are getting filtered into spam folders—and links them to configuration changes.

This reduces time spent decoding logs or interpreting cryptic bounce codes. You’re not just seeing outcomes—you’re seeing the “why” behind them.

For ongoing campaigns, the assistant can spot new patterns in real time, like sudden spikes in disposable email use or role addresses (e.g., admin@, support@) that harm sender reputation and inbox placement. These details matter: according to RFC 5321, sender reputation and domain trust are key factors in email routing decisions by major providers.

It’s not a substitute for diligence, but it cuts through noise. You verify, test, and improve—all in one place. Use the real-time verification API or inbox placement testing to see how your domain performs across real mail clients before sending.

Domain verification as a baseline, not a finish line

Verifying your sending domain in Mailgun is essential, but it’s only the start. Inbox placement depends on ongoing sender reputation, list hygiene, and consistent alignment with email standards.

High-volume senders need tools that scale. MailTester’s API and bulk verification workflows let you audit large databases efficiently, catching invalid, catch-all, or risky addresses before they harm deliverability.

With 98.9% accuracy and credits that never expire, MailTester supports long-term deliverability health. Verification isn’t a one-time check—it’s a continuous part of a reliable sending operation.

Sources

Gmail delivered 87.2% of commercial email to the inbox in 2024 while sending 6.8% to spam — the best inbox rate of the four major mailbox providers. — Validity 2025 Email Deliverability Benchmark Report (2025)
Sending from a domain with at least three months of history improves inbox placement by 28% compared with a brand-new domain. — Woodpecker data (via WarmForge deliverability statistics) (2025)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What happens if I don’t verify my domain in Mailgun?

Unverified domains may have emails rejected or filtered into spam by providers like Gmail and Outlook.

How long does domain verification in Mailgun take?

DNS propagation typically takes 10–30 minutes after adding records. Verification completes once Mailgun confirms the records are live.

Can I use MailTester to verify emails sent through Mailgun?

Yes—MailTester’s real-time API and bulk list verification work with Mailgun-sent emails to ensure only valid addresses are used.

What does a 'risky' email verdict mean in MailTester?

A risky address may be valid but associated with high bounce rates, disposable domains, or role-based usage—likely to hurt deliverability.

Do MailTester credits expire?

No—purchased verification credits never expire, allowing consistent list hygiene over time.

How does DMARC protect my Mailgun domain?

DMARC tells receiving servers how to handle unauthenticated messages and provides reports on email traffic to detect spoofing.

Why does Mailgun require SPF and DKIM records?

These records authenticate your sender identity, reducing phishing and spoofing risks, and are required for inbox placement.

Can I have multiple domains in Mailgun?

Yes—Mailgun supports multiple domains, each requiring its own SPF, DKIM, and DMARC configuration for proper authentication.

How often should I check my domain’s deliverability in Mailgun?

Test deliverability after major campaign changes or spikes in volume. Use MailTester’s inbox-placement tool to verify outcomes.

What is the benefit of using MailTester’s integrations with Mailgun?

Integrations automate verification and delivery testing, keeping your lists clean and your messages reaching inboxes.

Is there a way to verify a domain without editing DNS?

No—full domain verification requires DNS changes to authenticate SPF, DKIM, and DMARC records.

How does sender reputation affect Mailgun deliveries?

Poor reputation from bounces, spam reports, or invalid addresses leads to higher filtering and reduced inbox placement.