logo
logo
Sign in

DMARC: How to Prevent Email Spoofing

avatar
Alex Benjamin
DMARC: How to Prevent Email Spoofing

SPF, DKIM, and DMARC are three techniques used in modern email authentication. These techniques verify that a message was sent by the sender specified in the from header.

Email senders can protect their brand and subscribers' personal data by using DMARC to prevent spoofed spam and phishing emails from reaching their email subscribers and customers.

This Blog covers the fundamentals of SPF, DKIM, and DMARC, as well as how to properly deploy DMARC and read DMARC reports.

What is Email Spoofing?

Sending an email with a fake email address is known as email spoofing. The sender forges an email header to make the recipient believe the letter came from a different source than it really did, with the goal of getting the recipient to open or re-send the email to someone else.

The common reasons for spoofing are:

  • Hiding the real name of a sender;
  • Avoiding blacklisting;
  • Identity theft;
  • Impersonating someone who the recipient knows;
  • Impersonating a business that the recipient works with.

Because SMTP (Simple Mail Transfer Protocol) does not provide email authentication in today's world, spoofing is possible. However, there are protocols in order to protect emails from malicious activity.

So, how to prevent email from spoofing?

In order to protect oneself, all incoming messages should be authenticated properly. SPF, DKIM, and DMARC are three most globally used protocols which help achieve this goal.

What is DMARC?

The DMARC protocol (Domain-Based Message Authentication, Reporting, and Conformance) ensures that an email was received from a specific sender. Phishing, spoofing, and other malicious activity are no longer a possibility. DMARC also improves delivery rates by controlling the delivery process and ensuring that emails are sent to the inbox of the intended recipient instead of the spam folder.

DMARC is built on the two widely used protocols SPF and DKIM.

DMARC Policy

DMARC requires email domain owners to add a policy (p=) tag in their DMARC record. This policy tells email receivers how they should treat an email that appears to come from the domain in the from header, but does not pass DMARC alignment.

There are three DMARC policies:

  • None: no action will be taken regarding the delivery of messages. This policy is used for monitoring and collecting data about email authentication of the messages sent from a domain.
  • Quarantine: an email that fails the DMARC check will be treated by email receivers as suspicious. Depending on the email receiver, this can mean “send to spam folder”, “subject to thorough filtering”, and/or “flag as suspicious”.
  • Reject: an email that fails the DMARC check will be rejected during the SMTP transaction.
collect
0
avatar
Alex Benjamin
guide
Zupyak is the world’s largest content marketing community, with over 400 000 members and 3 million articles. Explore and get your content discovered.
Read more