Scenario 1: You send out emails using a subdomain
If you’re using your subdomain to send out emails, the sending subdomain should have a separate SPF record configured for it.
Option 1. The first option is publishing a separate SPF record for the subdomain in the DNS zone. You can use EasyDMARC’s SPF generator tool to create the SPF record for your subdomain. It will also help you make sure that there are no typos or other human errors in the SPF record.
Simply navigate to the SPF generator tool >> add the domain >> add the SPF mechanisms of your sending sources, and click the “Generate” button:
The system will provide you with a TXT-type SPF record that you can publish in your DNS zone for the subdomain.
Option 2. You can consider adding the subdomain to EasyDMARC, separately from the root domain, and then you’ll be able to activate EasySPF for it.
However, there is no need to add the subdomains to the platform as separate domains unless the subdomains follow different sending practices than the root one.
Please refer to the following article for more comprehensive guidance on when there is a need to add the subdomains to EasyDMARC, separately from the root domains:
Should I add subdomains to the dashboard separately?
Scenario 1: EasySPF Is Activated for the Root Domain, but You Are Sending Emails Using SPF Subdomain-Capable Sources
This happens when EasySPF is activated for your root domain, but you send emails from the root domain through a source that requires SPF to be configured on a subdomain level.
Such sources (e.g., SendGrid, Mailgun) do not support SPF alignment with the root domain directly. To ensure SPF alignment and successful SPF checks for emails sent via these services, you need to set up SPF records specifically on the designated subdomain.
In this case, when using subdomain-capable sources to send emails from the root domain, there is no need to add those sources to EasySPF. This is because EasySPF applies at the root domain level. Therefore, if you add subdomain-capable sources to EasySPF, SPF alignment cannot be achieved, and emails will fail SPF checks.
Examples of such sources:
- SendGrid: For SPF configuration, SendGrid provides a CNAME-type record that you must publish for the subdomain they provide (e.g., em111.example.com) directly in your DNS zone to ensure your SendGrid emails pass SPF checks.
- Mailgun: For SPF configuration, Mailgun provides a TXT-type SPF record that must be published for the subdomain used in the setup (e.g., mg.example.com) directly in your DNS zone to ensure your Mailgun emails pass SPF checks.
In cases like these, SPF return-path checks are performed against the subdomains rather than the root domain.
In case you have any further questions, feel free to reach out to EasyDMARC technical support.