Set Up DMARC for Enom Email : Enom Customer Support

Beginning February 2024, Google and Yahoo require bulk email senders to implement DMARC. Starting May 5, 2025, Microsoft enforces the same requirement. These providers focus on email validation to prevent unwanted spam and bad actors from reaching their customers' inboxes. This article explains DMARC, the records you need, and how to add them to your Enom-managed domain and account email.

What DMARC is and why it matters

Domain-based Message Authentication, Reporting and Conformance (DMARC) is an email authentication, policy, and reporting protocol. It uses the Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) protocols, adding a connection to the domain name for recipient handling of authentication failures and reporting from receivers to senders. Its purpose is to improve and monitor protection of the domain from fraudulent email.

Sending from a domain with DMARC in place improves inbox placement. A DMARC record helps ISPs identify you as a sender who follows established email standards, reducing your spam liability.

Email records that DMARC requires

Your messages pass SPF using the same domain as your message From: header. This is the Return-Path value within email headers, also called the bounce domain, envelope-from, or MailFrom.

Beginning February 2024, emails must pass DMARC through these requirements:

Authenticating with SPF.
Authenticating with DKIM.
Published DMARC TXT record.

DMARC record

Subdomain	_dmarc
Record Data	v=DMARC1; p=none; (Minimum required)
Suggested to add emails for stat data	v=DMARC1; p=none; rua=mailto:username@example_1.tld; ruf=mailto:username@example_2.tld;fo=1

SPF record

TXT	Root Domain
Record Data	v=spf1 include:_spf.emfwd.name-services.com MX ~all

Understanding a DMARC structure

Tag	Value	Translation
V	DMARC1	The DMARC version should always be DMARC1. An incorrect DMARC tag causes the entire record to be ignored.
P	none	The policy applied to emails that fail the DMARC check. Authorized values: none, quarantine, or reject. None collects feedback and provides visibility into email streams without impacting existing flows.
rua	mailto:dmarc-username@example.tld	The list of URIs for receivers to send XML feedback to.
ruf	mailto:dmarc-username@example.tld	The list of URIs for receivers to send reports to.

Step 1: Add the DMARC record to your domain

Locate the domain you want to manage by clicking Domains followed by My domains.
Search for the domain or choose it from the list.
Choose Host records from the manage domain dropdown.
Enter the records in the text field and click Save.

Note: Replace username@example.tld with your email address.

Host name	Address
_dmarc	v=DMARC1; p=none; rua=mailto:username@example.com; ruf=mailto:username@example.com;fo=1
	v=spf1 include:_spf.hostedemail.com ~all

Step 2: Add validation records to your account email domain

Enom uses your account email to send account and system notifications. Adding the DMARC record to your account email domain ensures notifications are sent properly.

Log in to your Enom account.
Click My account and Account settings.
The domain of your account email needs the DMARC records and this SPF record: v=spf1 include:_spf.hostedemail.com ~all

Warning: If the account email domain cannot pass email validation checks, registrants may not receive system notifications. Remove the quotation marks from the SPF record.