Forget the days of sending emails without worrying if they'll get delivered. SPAM has been around as long as email itself, making it tough for recipients to tell what's real.

What if legitimate senders could stand out and ensure their emails hit the Inbox? That's where Email Authentication comes in.

It’s important to note that some providers like Gmail and Yahoo now require that users from a domain are authenticated to be allowed to send to their domains.

In this article, we'll guide you on how to make sure your emails land safely where they belong.

Authentication prevents spammers from using your domain to send emails without your permission by employing protocols like SPF, DKIM, and DMARC to validate the legitimacy of your emails and enhance delivery reliability.

It's crucial to note that sending from a non-authenticated domain is known to cause significant delivery issues with all email providers, preventing many recipients from receiving your emails in their Inbox.

If you don't authenticate your domain the following message will appear for Gmail receivers :

To do this, you will need to access the DNS records for your domain with its hosting provider and add the correct DNS settings. You can follow this guide:

Please make sure you have already set up the SPF/DKIM on your From domain before proceeding with DMARC.

Once your SPF/DKIM is done, we recommend you set up an account with DMARCIAN and run through their DMARC RECORD WIZARD to create your DMARC record.

DMARCIAN is a trusted partner with our application and as soon as you set up your DMARC record, you will start to get flooded with XML reports telling you who is using your domain. These reports provide insight into how your email is moving through the ecosystem and allow you to identify if anyone else is using your domain. Making sense of these reports can be tricky and they can be numerous. Not only can DMARCIAN help create your DMARC record with ease, but their platform can also be used to view these XML reports and provide visualization on how your email domains are being used so you can take action. You will need this visibility in order to ensure you do not block legitimate mail before moving your DMARC policy towards p=quarantine or p=reject.

What started with a small list of ISPs like AOL, Yahoo, and Gmail, has grown into a long list around the world with more and more being added every day. Here is a current list of known receivers checking for DMARC:

Sender Policy Framework (SPF) is an authentication standard that has been around since 2003 and works by publishing a list of IP addresses that are allowed to send on your domain’s behalf. Receiving mail servers will use SPF to verify that messages sent from your domain were sent by one of these IP addresses. SPF authenticates the Return-Path: domain with the IP address used to send the email.

SPF helps protect your domain against spoofing and helps prevent your outgoing messages from being marked as spam by receiving servers. Whether the SPF passes (or fails) can be seen in the Authentication-Results: header. However, this only validates the server sending the email; it does not ensure that the content has not been tampered with. For that, we need DKIM (Domain Keys Identified Mail).

DKIM stands for DomainKeys Identified Mail and is a complex method of authentication that encrypts the email in transit by signing it with a digital signature which creates a unique string of characters called a "hash value." When a receiver detects an email has been signed using DKIM, it will authenticate the message using a pair of “keys” :

1st key - “Private Key” is kept safe by the sender and cannot be shared.

2nd key - “Public Key” is stored in the DNS of the client's From domain.

When the email is received, the receiver will use these keys to decrypt the hash value in the header and if both keys match, it shows the email has not been altered and the DKIM signature is then verified. If the keys do not match, the DKIM signature will fail and the recipient’s ISP will be more likely to place the email in the Spam box or block it outright. But how can I see who is using my domain without my permission? Enter DMARC.

DMARC stands for Domain-based Message Authentication, Reporting & Conformance and it’s a standard that mail servers use to determine if an incoming email is coming from sources that the domain sending the email trusts.

DMARC uses SPF or DKIM to verify if the sender is genuine and takes authentication one step further by sending a report of who is using their domain back to the sender. For DMARC to pass, the email must pass either SPF or DKIM, and the domain in the From header must be aligned with the corresponding SPF or DKIM domain.

The main advantage of DMARC is that it’s the sender who controls what happens to spam sent using their domain, not the receiver. So you can tell the receiver to block mail you didn’t send, and better yet, you get a report of mail that is using your domain without your permission - so DMARC is very powerful and is the gold standard in use today.

A quick overview on how SPF works by DMARCIAN.

A quick overview on how DKIM works by DMARCIAN.

A quick overview of how DMARC works by DMARCIAN.