🇺🇸 Welcome from the USA! We have special plans for you.
View US Hosting Plans →

Configure DMARC to protect your email domain

📅 15/06/2026 ⏱ 5 min de lectura
PlatiniumHost

Escrito por

Luis Contreras · CEO & Fundador · +24 años en hosting

Configure DMARC to Protect Your Email Domain

In today's digital world, email security is paramount. Spoofing and phishing attacks are constant threats that can damage your brand's reputation and compromise the security of your communications. This is where DMARC (Domain-based Message Authentication, Reporting, and Conformance) comes into play. DMARC is an email authentication protocol that relies on SPF and DKIM to provide an additional layer of protection, ensuring that only legitimate emails from your domain reach their destination.

What is DMARC and why is it essential?

DMARC is a standard that allows domain owners to instruct receiving mail servers on how to handle emails that fail SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) authentication checks. Its main objectives are:

  • Prevent spoofing, where attackers send emails that appear to come from your domain, deceiving recipients.
  • Combat phishing, which attempts to trick users into revealing sensitive information or performing malicious actions.
  • Improve the deliverability of your legitimate emails, as receiving mail servers will trust your domain more when verifying its authenticity.
  • Receive reports on the authentication of your emails, allowing you to identify and correct potential problems or unauthorized uses of your domain.
Tip: DMARC does not replace SPF or DKIM; rather, it uses them and adds a layer of control and reporting on top. It is the final piece of the email authentication puzzle for robust security.

Prerequisites: SPF and DKIM

Before configuring DMARC, it is crucial that SPF and DKIM are correctly set up for your domain. If you don't have them, DMARC will not be able to function effectively, as it relies on these two protocols for authentication.

  • SPF (Sender Policy Framework): A DNS record that specifies which mail servers are authorized to send emails on behalf of your domain. This helps prevent spammers from sending forged emails from your domain.
  • DKIM (DomainKeys Identified Mail): Adds a digital signature to outgoing emails, allowing receiving servers to verify that the email has not been altered in transit and that it genuinely originates from the specified domain, ensuring message integrity.

At PlatiniumHost, you can easily manage your SPF and DKIM records through your cPanel or control panel. Ensure that these security foundations are firm and validated before proceeding with DMARC implementation.

Configuring Your DMARC Record

DMARC configuration involves adding a specific TXT record to your domain's DNS. This record will tell receiving mail servers how to act on emails that fail authentication checks and where to send activity reports.

Step 1: Access Your Domain's DNS Management

Generally, this is done through your hosting control panel. If you are a PlatiniumHost client, you can access your domain's DNS zone directly from cPanel, which greatly simplifies the process:

  1. Log in to your cPanel.
  2. Look for the 'Domains' section and click on 'DNS Zone Editor' or 'Zone Editor'.
  3. Select the domain to which you want to add the DMARC record.

Step 2: Create a New TXT Record

Within the DNS zone editor, look for the option to add a new record. You will need to configure the following fields with DMARC information:

  • Type: TXT
  • Name/Host: _dmarc.yourdomain.com (replace yourdomain.com with your actual domain. It is crucial to include the _dmarc prefix).
  • Value/Content: This is where your DMARC policy parameters will go, defined by a text string.

Step 3: Define Your DMARC Policy

The TXT record value is a text string containing several tags, each with a specific function. Here are the most important ones you should include:

  • v=DMARC1: Indicates the DMARC protocol version. It should always be DMARC1.
  • p=policy: Defines the policy that receiving servers should apply to emails that fail DMARC authentication. The options are:
    • none (None): Only monitors and sends reports. Emails that fail are not affected in their deliverability. Ideal for starting and collecting data.
    • quarantine (Quarantine): Emails that fail are marked as suspicious and are often moved

💬 ¿En qué podemos ayudarte?

Selecciona un agente de soporte

¿Hablamos?