Domain verification changes for new and existing domains
Mailgun is making several changes to our domain verification requirements, which will go into effect in two separate phases. Read more...
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.
Table of content
Table of content
On November 1st, 2016:
Any domain created from this date forward will require verification through the use of a DKIM and SPF record to send and receive messages.
On December 1st, 2016:
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:
Checking for unverified domains
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.
Checking sandbox domains
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.
Build Laravel 10 email authentication with Mailgun and Digital Ocean
When it was first released, Laravel version 5.7 added a new capability to verify user’s emails. If you’ve ever run php artisan make:auth within a Laravel app you’ll know the...
Here’s everything you need to know about DNS blocklists
The word “blocklist” can almost seem like something out of a movie – a little dramatic, silly, and a little unreal. Unfortunately, in the real world, blocklists are definitely something you...