SPF records are used to help prevent email spoofing. They help to ensure that only authorized servers can send emails on behalf of your domain. SPF records can help to improve your email deliverability.
How to Configure SPF for OpenSRS
Two clusters, Cluster A and Cluster B are designated for the email services that OpenSRS offers. If you are a part of one of these clusters, you must add an “include” method in your SPF record.
For Clusters A and B
include:_spf.hostedemail.com
In order for notifications regarding outbound emails sent from OpenSRS to be delivered to registrants on behalf of resellers, you must add the following mechanism , if you have a hosting registration.m: include:registrarmail.net
Please read through OpenSRS’s SPF documentation if you wish to view the list of modified IP addresses for clusters A and B. Alternatively, you can change the IP addresses in your SPF record for clusters A and B to the single inclusion indicated above.
For OpenSRS, an SPF TXT record will have the following syntax:
This record should be published in the DNS records section for the relevant domain.
Worth noting: To activate SPF for outgoing emails using OpenSRS if your domain previously lacked an SPF record, all you need to do is publish the aforementioned record. If your DNS already contains an SPF record, you must update it to include OpenSRS as shown below:
Allow your DNS to process the adjustments for 72 hours.
With Skysnag, you can easily manage OpenSRS’s SPF records without having to go to your DNS. This allows OpenSRS’s SPF record to propagate instantly, and autonomously always pass SPF alignment.
Skysnag helps busy engineers enforce DMARC, responds to any misconfigurations for SPF or DKIM which increases email deliverability, and eliminates email spoofing and identity impersonation.
