Introduction #

Email deliverability and authentication is crucial for your email services. This ensures recipients securely receive your emails. Incorrect authentication can cause your emails to land in spam folders or to be blocked entirely. In this doc you’ll learn more on how to configure these settings correctly and to your liking.

---

What is Email Deliverability and Authentication #

Email deliverability refers to how reliably your emails are accepted and trusted by receiving mail servers. While no setting can guarantee inbox placement, proper authentication is one of the most important parts of successful delivery.

At ProRedLine, email authentication is managed through cPanel and is based primarily on SPF, DKIM, and DMARC. These standards help receiving mail providers verify that emails sent from your domain are legitimate and have not been altered.

---

Why Email Authentication Matters #

Without proper authentication, emails are more likely to be marked as spam, rejected entirely, or treated as suspicious by receiving systems. Over time, poor authentication can also damage the reputation of your domain.

Modern mail providers increasingly expect domains to use SPF, DKIM, and DMARC correctly. For that reason, proper authentication should be seen as a core part of running email on your domain, not as an optional extra.

---

Where to Manage It in cPanel #

In cPanel, email authentication status can be viewed through Email > Email Deliverability.

This page shows the current authentication status for the domains connected to your account. It is mainly a visibility and status tool, meaning it helps you see whether authentication is configured correctly, but it is not intended for advanced deliverability tuning.

For each domain, cPanel can show the status of:

• SPF
• DKIM
• DMARC

Common statuses include valid, missing, or warning/problem states. If warnings appear, email delivery may be affected until the underlying DNS issue is corrected.

---

SPF Explained #

SPF stands for Sender Policy Framework. It defines which servers are allowed to send email on behalf of your domain.

SPF is published as a DNS TXT record. When a receiving mail server gets a message from your domain, it can compare the sending server against your SPF record to determine whether that source is authorised.

If email is sent from a server that is not allowed by SPF, the message may be marked as suspicious, rejected, or routed to spam.

---

DKIM Explained #

DKIM stands for DomainKeys Identified Mail. It adds a cryptographic signature to outgoing email so receiving servers can verify that the message was sent legitimately and was not modified during delivery.

Once configured correctly, DKIM works automatically in the background. Like SPF, it depends on the correct DNS record being present for the domain.

---

DMARC Explained #

DMARC stands for Domain-based Message Authentication, Reporting and Conformance. It works together with SPF and DKIM and defines what should happen when authentication checks fail.

DMARC can be used to:

• monitor authentication results
• request reports
• define whether failed messages should be monitored, quarantined, or rejected

Because DMARC affects how failed messages are handled, policy changes should be made carefully.

---

Default Configuration at ProRedLine #

For supported domains on ProRedLine:

• SPF is generated automatically
• DKIM is enabled by default
• DMARC is typically set to a safe monitoring-oriented policy

For most customers, this provides a suitable starting point for normal email use.

---

When Warnings or Problems Can Appear #

Warnings in Email Deliverability are usually caused by DNS-related issues rather than mailbox problems. Common causes include:

• external mail services sending on behalf of the domain
• multiple SPF records
• modified or removed DKIM records
• incorrect TXT records
• DMARC records that are missing or misconfigured

If cPanel reports an issue, it is important to review the suggested records carefully and compare them with the current DNS configuration.

---

Applying Fixes #

When authentication problems need to be corrected, the required changes are usually made in the DNS Zone Editor. This may involve adding, updating, or correcting DNS records.

If you are not sure what a suggested change will do, it is best to review it carefully before applying it. Incorrect DNS changes can affect email delivery instead of improving it.

---

Important Note About Deliverability #

Email authentication is essential for reliable delivery, but it does not directly control whether a message goes to the inbox, spam folder, or another location. Inbox placement can still be influenced by other factors such as sender reputation, message content, recipient server policies, and past sending behaviour.

In short, SPF, DKIM, and DMARC help prove that your emails are legitimate. They are a core part of deliverability and should be configured correctly if you want your domain to send email reliably.