When you use a custom domain for professional email, authenticating your messages is an important part of maintaining email deliverability and protecting your business identity.
SPF, DKIM, and DMARC are three email authentication standards that help receiving mail servers evaluate whether messages claiming to come from your domain are legitimate.
Understanding these records can help reduce email spoofing, improve trust in your domain, and make it easier to investigate certain email delivery problems.
What Is SPF?
SPF stands for Sender Policy Framework.
It is a DNS record that identifies which mail servers and services are authorized to send email on behalf of your domain.
When a receiving mail server checks an incoming message, it can compare the sending server with the sources authorized by your domain's SPF record.
An SPF record helps receiving systems identify unauthorized sending sources.
What Is DKIM?
DKIM stands for DomainKeys Identified Mail.
It adds a digital signature to outgoing messages. The receiving mail server can use the public key published in your domain's DNS records to verify the signature.
This helps the receiving system determine whether the message carries a valid signature associated with the sending domain and whether the signed content has been modified.
What Is DMARC?
DMARC stands for Domain-based Message Authentication, Reporting, and Conformance.
It builds on SPF and DKIM by allowing a domain owner to publish a policy that tells receiving mail servers how to handle messages that fail DMARC authentication.
DMARC also supports reporting, helping domain owners understand how their domains are being used to send email.
A DMARC policy can request that messages failing authentication be monitored, quarantined, or rejected.
How Do SPF, DKIM, and DMARC Work Together?
Each standard has a different purpose:
-
SPF identifies authorized sending sources.
-
DKIM verifies a digital signature associated with the sending domain.
-
DMARC evaluates authentication alignment and communicates the domain owner's requested handling policy.
Together, these standards help receiving mail systems evaluate messages that claim to come from your business domain.
They are especially important when your domain sends email through multiple services, such as professional mailboxes, website contact forms, billing platforms, or marketing applications.
Where Are Email Authentication Records Configured?
SPF, DKIM, and DMARC are published through DNS records associated with your domain.
| Standard | DNS record type | Purpose |
|---|---|---|
| SPF | TXT | Identifies authorized email senders |
| DKIM | TXT or, in some configurations, CNAME | Publishes information used to verify email signatures |
| DMARC | TXT | Defines the domain's authentication policy and reporting preferences |
The exact record values depend on the email services authorized to send messages for your domain.
Do not copy record values from another domain or assume every provider uses the same configuration.
How to Configure Email Authentication
Before changing DNS records, identify every service that sends email using your domain.
These may include:
-
Your professional email service.
-
Website contact forms.
-
Customer relationship management (CRM) platforms.
-
Billing and invoicing systems.
-
Newsletter and marketing services.
-
Other applications that send messages using your domain.
Step 1: Obtain the Required DNS Values
Obtain the SPF, DKIM, and DMARC configuration information from the relevant email provider or sending service.
If you are unsure which values apply to your WebDaddy Pro email service, contact WebDaddy Pro Support before adding or changing records.
Step 2: Review Your Existing SPF Record
Check whether your domain already has an SPF record.
A domain should not have multiple separate SPF records for the same hostname. If several services send email for your domain, their authorized sending sources may need to be combined into one valid SPF policy.
Do not simply add a second SPF TXT record. Incorrect SPF configuration can cause authentication failures.
Step 3: Publish the DKIM Record
Use the DKIM record information supplied by the email provider or sending service.
The record may use a provider-specific selector and hostname. Enter the supplied values exactly as instructed.
Step 4: Publish the DMARC Record
DMARC records are commonly published under the _dmarc hostname.
A DMARC policy should be introduced carefully. Domain owners setting up DMARC for the first time often begin with a monitoring policy, review authentication reports, and then determine whether a stricter policy is appropriate.
Do not move directly to quarantine or reject without identifying legitimate services that send email for your domain and confirming that they pass authentication.
Step 5: Allow DNS Changes to Propagate
After publishing DNS changes, allow time for the records to become visible across DNS resolvers.
Propagation time can vary depending on DNS caching and the records' time-to-live (TTL) settings.
Step 6: Test Email Authentication
Send test messages to external email accounts and review the available authentication results in the message headers.
Look for SPF, DKIM, and DMARC results. If a legitimate message fails authentication, review the DNS configuration and the sending service's instructions.
Common Email Authentication Problems
Multiple SPF Records
Publishing multiple SPF records for the same hostname can cause SPF evaluation errors.
Review existing records and consolidate authorized sending sources into one valid SPF policy.
Missing or Incorrect DKIM Records
If a DKIM record is missing or does not match the sending service's configuration, receiving servers may be unable to verify the message signature.
Confirm the selector and DNS record values with the provider.
Incorrect DMARC Alignment
A message may pass SPF or DKIM individually but still fail DMARC if the authenticated domain does not align with the domain shown in the message's From address.
Review the sending service's authentication and alignment requirements.
Third-Party Services Not Included
A website, marketing platform, or billing application may send messages using your domain without being included in the domain's authentication configuration.
Identify all legitimate sending services before tightening your SPF or DMARC policies.
Important: Review DNS Changes Before Applying Them
Email authentication records affect how receiving mail systems evaluate messages from your domain.
Incorrect changes can cause legitimate business email to be rejected, quarantined, or treated as suspicious.
Before changing existing records:
-
Save a copy of the current DNS configuration.
-
Identify all legitimate email-sending services.
-
Obtain the correct values from each provider.
-
Avoid creating duplicate SPF records.
-
Test authentication after making changes.
-
Contact support if you are uncertain about a record's purpose.
Need Help With Email DNS Configuration?
If you need assistance identifying the appropriate email authentication records for your domain, contact WebDaddy Pro Support.
Include your domain name, the email service you are configuring, and a description of the issue. Do not include email passwords or other confidential credentials in your support request.
For additional information about domain records, see the Domains & DNS Knowledgebase.