- What's new
Continuing Our Commitment: HTTPS Innovation And Optimization
Mailgun is making several changes to our domain verification requirements, which will go into effect in two separate phases. This blog post contains a list of steps that you can reference to help you determine if you need to make any changes to your configuration to continue using the service.
Any domain created from this date forward will require verification through the use of a DKIM and SPF record to send and receive messages.
All domains, regardless of the creation date, will require verification to continue sending and receiving messages.
All subdomains of mailgun.org will be treated as sandbox domains, which are domains that allow sending to a list of up to five authorized recipients.
Mailgun is making these changes to our verification system to provide an additional proof of ownership check. Over the last several years, we’ve gradually increased the verification requirements based on industry best practices to ensure optimal deliverability. These changes mean that all domains on your account will be handled consistently regardless of when they were created.
You can determine if these changes impact your account by following the steps below:
1) Login to the Mailgun control panel and select the Domains section.
2) Select any domain that is in the orange “unverified” state.
3) In the Domain Verification & DNS section, locate the records with the red warning indicator.
4) In the DNS administration tool provided by your DNS or hosting provider, add all records under the section “DNS Records for Sending”. We have guides available that describe this process for the most common providers.
5) After the records have been added, click the “Check DNS Records Now” button. Due to caching, up to 24 hours may be required before Mailgun is able to resolve the newly created records.
6) Once verification has been completed successfully, your domain will switch to a “verified” state.
1) Login to the Mailgun control panel.
2) Check for domains listed under the “sandbox domains” header on the dashboard homepage.
3) Ensure that your application is not relying on any of the listed sandbox domains for sending and receiving. If sandbox domains are being used, you must create a sending domain by clicking the “Add Domain” button under the sending domains section.
Additionally, you can use the logs and reporting features of the Mailgun control panel to determine what domains are actively sending and receiving messages on your account. If you need assistance making these changes, please reach out to our support team by creating a ticket here.
Learn about our Deliverability Services
Looking to send a high volume of emails? Our email experts can supercharge your email performance. See how we've helped companies like Lyft, Shopify, Github increase their email delivery rates to an average of 97%.
Last updated on August 28, 2020
Continuing Our Commitment: HTTPS Innovation And Optimization
Easier and Faster Implementation with Our Updated SDKs
Inbox Placement - Delivery Made Simple
Lock It Down! Welcome, 2 Factor Authentication
Introducing The 5 User Roles: Keep The Riffraff Out Of Your Mailgun Account
How Quickly Can Mailgun Process My Messages? Introducing The Rapid Fire Delivery SLA
Mailgun Announces Improvements To Logs Feature To Increase Visibility Into Deliverability Problems
Mailgun Rolls Out Changes To Email Validation API Including New Features And Pricing Model
Interested In Learning A New Language? Mailgun Is Too!
Analyze And Optimize Engagement With The New Campaigns
InboxReady x Salesforce: The Key to a Stronger Email Deliverability
Become an Email Pro With Our Templates API
Google Postmaster Tools: Understanding Sender Reputation
Navigating Your Career as a Woman in Tech
Implementing Dmarc – A Step-by-Step Guide
Email Bounces: What To Do About Them
Announcing InboxReady: The deliverability suite you need to hit the inbox
Black History Month in Tech: 7 Visionaries Who Shaped The Future
How To Create a Successful Triggered Email Program
Designing HTML Email Templates For Transactional Emails
InboxReady x Salesforce: The Key to a Stronger Email Deliverability
Implementing Dmarc – A Step-by-Step Guide
Announcing InboxReady: The deliverability suite you need to hit the inbox
Designing HTML Email Templates For Transactional Emails
Email Security Best Practices: How To Keep Your Email Program Safe
Mailgun’s Active Defense Against Log4j
Email Blasts: The Dos And Many Don’ts Of Mass Email Sending
Email's Best of 2021
5 Ideas For Better Developer-Designer Collaboration
Mailgun Joins Sinch: The Future of Customer Communications Is Here
Always be in the know and grab free email resources!
By sending this form, I agree that Mailgun may contact me and process my data in accordance with its Privacy Policy.