Back to all articles

SPF, DKIM & DMARC Setup for Business Email in India: DNS Records, cPanel & Google Workspace Guide (2026)

SPF, DKIM & DMARC Setup for Business Email in India: DNS Records, cPanel & Google Workspace Guide (2026)

SPF, DKIM & DMARC Setup for Business Email in India: DNS Records, cPanel & Google Workspace Guide (2026)

Have you ever sent an important business email only to discover that it landed in the recipient's spam folder? Or received a message that appeared to come from your company's domain but was actually sent by someone else?

These problems can be related to email authentication.

When a business uses a custom email address such as sales@yourcompany.com, customers expect messages from that address to be genuine. However, without appropriate authentication records, receiving mail servers may find it difficult to verify whether an email was authorised by the domain owner.

This is where SPF, DKIM and DMARC become important.

SPF DKIM DMARC setup helps businesses authenticate their email domains, reduce the risk of domain spoofing, and improve the reliability of legitimate email delivery.

Whether you use cPanel hosting, Google Workspace, Microsoft 365, or another business email provider, this guide explains how these technologies work, how to configure the relevant DNS records, and how to test your email authentication in 2026.

1. What Are SPF, DKIM and DMARC?

SPF, DKIM and DMARC are email authentication mechanisms that work together to help receiving mail servers verify messages sent using your domain.

Each performs a different function.

What is SPF?

SPF stands for Sender Policy Framework.

It is a DNS-based email authentication mechanism that identifies which mail servers and services are authorised to send email on behalf of a domain.

For example, suppose your business uses:

info@example.com

You may send email through:

  • Your cPanel hosting mail server.
  • Google Workspace.
  • Microsoft 365.
  • A third-party email marketing platform.

Your SPF record identifies the authorised sending sources for your domain.

When a receiving mail server checks an incoming email, it can compare the sending server with the SPF policy published in DNS.

Main purpose: Help prevent unauthorised servers from sending email using your domain in the envelope sender identity.

What is DKIM?

DKIM stands for DomainKeys Identified Mail.

It uses cryptographic signatures to help receiving mail servers verify that an email was authorised by the signing domain and that signed message content has not been modified in transit.

DKIM uses two related keys:

  • A private key used by the sending email system to sign messages.
  • A public key published in DNS so receiving servers can verify the signature.

When a message is sent, the sending server adds a DKIM signature to its email headers.

The recipient's mail server retrieves the corresponding public key from DNS and verifies the signature.

Main purpose: Authenticate the signing domain and verify the integrity of signed message content.

What is DMARC?

DMARC stands for Domain-based Message Authentication, Reporting and Conformance.

It builds on SPF and DKIM by checking whether authenticated domains align with the domain shown in the visible From address.

It also lets the domain owner publish a policy describing how receiving servers should handle messages that fail DMARC authentication.

DMARC supports three commonly used policies:

  • p=none — Monitor authentication results without requesting quarantine or rejection.
  • p=quarantine — Request that failing messages be treated as suspicious, commonly by placing them in spam.
  • p=reject — Request rejection of messages that fail DMARC evaluation.

DMARC can also send aggregate authentication reports to a specified reporting address.

Main purpose: Establish domain alignment, communicate handling preferences for authentication failures, and provide visibility into email sources.

2. SPF vs DKIM vs DMARC: What Is the Difference?

Although these three mechanisms work together, they do not perform the same function.

SPF: Checks whether the sending server is authorised by the relevant envelope-sender domain.

DKIM: Checks whether a message has a valid cryptographic signature associated with the signing domain.

DMARC: Checks whether SPF or DKIM passes with the required alignment to the visible From domain and applies the published policy.

Think of them as three parts of an email authentication system:

  • SPF identifies authorised sending infrastructure.
  • DKIM verifies the domain's digital signature.
  • DMARC connects authentication results to the visible sender identity.

A properly configured domain should use all three where supported, even though Gmail's minimum authentication requirements differ between ordinary and bulk senders.

3. Why Does Your Business Need SPF, DKIM and DMARC?

Business email is used for quotations, invoices, customer enquiries, proposals, account notifications, and important communication.

Authentication problems can affect these workflows.

1. Reduce the risk of domain spoofing

Email spoofing occurs when someone sends a message that appears to come from a domain they do not control.

For example, an attacker may attempt to send a fraudulent invoice using an address that resembles:

accounts@yourcompany.com

Email authentication helps receiving servers identify unauthorised messages claiming to originate from your domain.

2. Improve email authentication

Receiving email providers evaluate authentication results when deciding how to handle incoming messages.

Correct SPF, DKIM and DMARC configuration helps establish that legitimate email is authorised and authenticated.

3. Protect your business identity

Your domain is part of your business identity.

If attackers impersonate your domain, they may attempt to deceive customers, employees, vendors, or business partners.

DMARC reporting can help identify unexpected sources sending messages that appear to come from your domain.

4. Support reliable business communication

A missing or incorrect authentication record can contribute to email delivery problems.

Correct configuration reduces avoidable authentication failures, although it cannot guarantee that every message reaches the inbox.

Email reputation, content, sending behaviour, recipient engagement, and other technical factors also influence delivery.

5. Meet major email-provider requirements

Google introduced email authentication requirements for senders delivering messages to personal Gmail accounts in February 2024.

Google requires all senders to use SPF or DKIM. Senders sending more than 5,000 messages per day to personal Gmail accounts must meet additional requirements, including SPF, DKIM and DMARC.

Google recommends using all three more broadly.

Microsoft also documents SPF, DKIM and DMARC configuration for custom email domains.

Read the official Gmail Email Sender Guidelines for the current requirements.

4. How Does SPF, DKIM and DMARC Authentication Work?

Consider a business that sends an invoice to a customer using:

billing@example.com

The receiving email provider performs authentication checks when the message arrives.

Step 1: SPF verification

The recipient's mail server checks the SPF policy for the relevant envelope-sender domain.

It determines whether the sending server is authorised.

Step 2: DKIM verification

The receiving server checks the DKIM signature in the email header.

It retrieves the public key from DNS and verifies the signature.

Step 3: DMARC evaluation

The receiving server checks whether SPF or DKIM authentication passes with the required domain alignment.

It then considers the domain's published DMARC policy.

Step 4: Reporting

If DMARC reporting is configured, aggregate reports can help the domain owner identify legitimate and unauthorised sending sources.

This makes it easier to investigate authentication failures and unexpected email activity.

5. SPF DKIM DMARC Setup: How to Configure DNS Records

Before changing DNS records, identify where your domain's authoritative DNS is managed.

It could be:

  • Your domain registrar.
  • Cloudflare.
  • Your hosting provider.
  • Another DNS management platform.

The DNS provider is not necessarily the same company that hosts your website or email.

This distinction matters because adding records to the wrong DNS dashboard will not change the publicly authoritative records.

Step 1: Identify every service that sends email

Start by listing all legitimate email-sending services connected to your domain.

For example:

Email serviceTypical purpose
Google WorkspaceBusiness communication
cPanel emailHosting-based mailboxes
Microsoft 365Business email
Email marketing platformCampaign emails
Website applicationContact and order notifications

Do not configure SPF based on assumptions.

If your website sends contact-form notifications through a third-party SMTP provider, that provider may also need to be included in your authentication configuration.

Step 2: Add an SPF DNS record

SPF is generally published as a TXT record.

An illustrative SPF record may look like this:

Type: TXT
Host: @
Value: v=spf1 include:mail.example.com ~all

This is only an example. The actual SPF value must come from your email provider and include all legitimate sending sources.

Important SPF rules:

  • Publish only one SPF record for a given domain name.
  • Include every legitimate email-sending service.
  • Avoid adding duplicate SPF records.
  • Do not copy another company's SPF value.
  • Review SPF DNS lookup limits.
  • Avoid changing the policy to -all until you have confirmed that legitimate senders are included.

If your business uses multiple email platforms, their SPF requirements must be combined correctly into a single SPF policy.

Step 3: Configure DKIM

DKIM configuration depends on your email provider.

The provider generates or supplies the relevant DKIM key information.

You then publish the required DNS record, commonly a TXT record or CNAME record, depending on the provider.

A typical TXT-based DKIM record has this structure:

Type: TXT
Host: selector._domainkey
Value: v=DKIM1; k=rsa; p=PUBLIC_KEY_VALUE

The selector and public key are provider-specific.

Do not use this example as a real DKIM record.

After publishing the DNS record, enable DKIM signing in your email provider's administration panel.

For stronger security, Google recommends a 2048-bit DKIM key when supported.

Step 4: Add a DMARC DNS record

DMARC is generally published as a TXT record under _dmarc.

For example:

Type: TXT
Host: _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com

Replace the example domain and reporting address with your own.

This example uses monitoring mode.

It allows you to begin collecting aggregate DMARC reports without immediately requesting that receiving servers quarantine or reject messages that fail DMARC.

Step 5: Monitor authentication results

After publishing the records:

  • Check that DNS records resolve correctly.
  • Send test messages to Gmail and Outlook accounts.
  • Inspect the message headers.
  • Review SPF authentication results.
  • Review DKIM signatures.
  • Review DMARC results and alignment.
  • Check aggregate reports if enabled.

Do not move directly to a strict DMARC policy without understanding which services are sending email for your domain.

A legitimate service that has not been configured correctly could have its messages quarantined or rejected.

6. How to Configure SPF and DKIM in cPanel Hosting

Businesses using cPanel hosting can often manage email authentication through the Email Deliverability interface.

The exact interface and available features depend on the hosting provider and server configuration.

Step 1: Log in to cPanel

Open your hosting control panel and sign in using your cPanel credentials.

Step 2: Open Email Deliverability

Navigate to:

Email → Email Deliverability

You should see the domains associated with your hosting account.

Step 3: Check the authentication status

Select the relevant domain.

The interface may display:

  • SPF status.
  • DKIM status.
  • Suggested DNS records.
  • Problems with existing records.

Step 4: Review the recommended records

If your hosting server manages authoritative DNS for the domain, cPanel may provide an option to install or repair the recommended SPF and DKIM records.

If DNS is managed elsewhere, copy the exact records and publish them at the authoritative DNS provider.

Do not assume that changing a local DNS zone inside cPanel automatically changes public DNS.

Step 5: Configure DMARC

Depending on your cPanel version and hosting configuration, the interface may also provide a suggested DMARC record or a way to manage it.

Review the suggested value before publishing it.

Start with a monitoring policy if you are still identifying legitimate sending services.

For more details, refer to the official cPanel Email Deliverability Documentation.

7. How to Configure Email Authentication for Google Workspace

If your company uses Google Workspace with a custom domain, configure email authentication through Google Admin and your DNS provider.

Step 1: Verify your domain configuration

Make sure your custom domain is correctly connected to Google Workspace.

Check the existing MX records and confirm that incoming mail is routed according to Google's instructions.

Step 2: Configure SPF

Google provides the SPF value for its email service.

A commonly used Google Workspace SPF value for a domain that sends email only through Google Workspace is:

v=spf1 include:_spf.google.com ~all

Do not copy this blindly if you also send email through cPanel, marketing platforms, website applications, or other providers.

All legitimate senders must be accounted for in the final SPF policy.

Step 3: Generate a DKIM record

  1. Open the Google Admin console.
  2. Navigate to the Gmail authentication settings.
  3. Select the relevant domain.
  4. Generate a DKIM key.
  5. Choose the supported key length.
  6. Copy the DNS record details supplied by Google.

Step 4: Publish the DKIM DNS record

Add the record at your authoritative DNS provider.

The hostname and value depend on the selector and key generated by Google.

Step 5: Start DKIM authentication

Return to the Google Admin console and start email authentication for the domain.

Google must be able to find the public DNS record before it can verify the configuration.

Step 6: Configure DMARC

After reviewing SPF and DKIM, publish a DMARC TXT record.

Start with a monitoring policy if you have not yet identified and tested all sending sources.

Google's official guide is available here:

Set Up DMARC for Google Workspace.

8. How to Configure SPF, DKIM and DMARC for Microsoft 365

Microsoft 365 users should also configure authentication for their custom email domains.

The configuration involves publishing DNS records at the provider managing the domain.

SPF configuration

Microsoft provides the SPF record required for the custom domain.

Add the exact value supplied for your Microsoft 365 configuration.

If other services send email from your domain, account for those services in the same SPF policy.

DKIM configuration

Microsoft provides DKIM configuration details for custom domains.

Depending on the service configuration, the required records may be CNAME records.

Publish the records and enable DKIM signing in the Microsoft 365 security or Defender administration interface as instructed.

DMARC configuration

Create a TXT record under:

_dmarc

The record should specify your chosen policy and reporting address.

Microsoft recommends configuring SPF, DKIM and DMARC as part of the overall email authentication strategy.

Official references:

9. Common SPF, DKIM and DMARC Configuration Mistakes

Incorrect DNS configuration can create email authentication failures.

Here are common problems to check.

1. Publishing multiple SPF records

A domain should not have multiple independent SPF records at the same DNS name.

If different services provide separate SPF values, combine the authorised sources into one valid SPF policy.

2. Forgetting third-party email services

Your website, CRM, marketing platform, or transaction system may send emails independently of your primary mailbox provider.

If these services are not properly authenticated, their messages may fail SPF, DKIM, or DMARC checks.

3. Publishing an incorrect DKIM selector

The DKIM selector must match the selector used by the sending provider.

An incorrect hostname or public key can prevent verification.

4. Enforcing DMARC too early

Starting immediately with p=reject can disrupt legitimate email if you have not identified all sending sources.

Begin with monitoring, inspect reports, correct authentication problems, and increase enforcement gradually.

5. Configuring records at the wrong DNS provider

If your nameservers point to Cloudflare, changing records only in cPanel may not update the public DNS zone.

Always confirm where authoritative DNS is managed.

6. Forgetting to update SPF after changing email providers

When moving from cPanel email to Google Workspace or Microsoft 365, review the existing SPF, DKIM, DMARC and MX records.

Do not leave outdated or conflicting authentication configurations.

7. Assuming authentication guarantees inbox delivery

SPF, DKIM and DMARC are important, but they do not guarantee that messages will always reach the inbox.

Other factors include:

  • Sender reputation.
  • Spam complaints.
  • Message content.
  • Sending volume.
  • Recipient engagement.
  • IP reputation.
  • Email-provider filtering policies.

10. How to Test SPF, DKIM and DMARC Records

After configuration, verify the actual DNS records and email authentication results.

1. MXToolbox

MXToolbox provides tools for checking SPF, DKIM, DMARC, MX and other DNS records.

You can use it to investigate missing records and common configuration problems.

2. Google Admin Toolbox

Google Admin Toolbox provides DNS lookup functionality.

It can help you inspect published DNS records.

3. DMARC reports

If your DMARC record contains an aggregate reporting address through the rua tag, participating receiving providers can send reports about authentication results.

These reports can help identify:

  • Legitimate sending sources.
  • SPF failures.
  • DKIM failures.
  • Alignment problems.
  • Unexpected sources using your domain.

DMARC aggregate reports are generally delivered in machine-readable XML format. A reporting tool can make them easier to interpret.

4. Inspect email headers

Send a test email to an external mailbox and inspect its original message headers.

Look for authentication results such as:

spf=pass
dkim=pass
dmarc=pass

These are illustrative results, not a guarantee that every message will produce identical headers.

The important thing is to check the actual authentication results for your message and identify any failures.

11. Email Authentication Checklist for Indian Businesses

Use this checklist before considering your domain's email authentication configuration complete.

Domain and DNS

  • Identify the authoritative DNS provider.
  • Identify every service sending email from your domain.
  • Confirm that the domain's MX records are correct.
  • Check the published SPF record.
  • Confirm there is only one SPF record at the relevant domain name.
  • Configure the correct DKIM record.
  • Enable DKIM signing in the email provider.
  • Publish the DMARC record.

Testing and monitoring

  • Check SPF DNS resolution.
  • Check DKIM DNS resolution.
  • Check DMARC DNS resolution.
  • Send test emails to Gmail and Outlook.
  • Inspect the original message headers.
  • Confirm SPF, DKIM and DMARC results.
  • Review aggregate DMARC reports.
  • Investigate unexpected sending sources.

Ongoing maintenance

  • Review authentication after changing email providers.
  • Update records when adding a new sending platform.
  • Monitor authentication failures.
  • Review DMARC policy before increasing enforcement.
  • Keep access to DNS and email administration accounts secure.

12. Frequently Asked Questions

1. Do I need SPF, DKIM and DMARC for my business email?

Google requires all senders sending to personal Gmail accounts to use SPF or DKIM authentication. Bulk senders exceeding 5,000 messages per day to personal Gmail accounts must meet additional SPF, DKIM and DMARC requirements. Setting up all three is a sensible general security practice for business domains.

2. Can I use SPF, DKIM and DMARC with cPanel hosting?

Yes. cPanel provides an Email Deliverability interface that can help manage SPF and DKIM records and, depending on configuration, DMARC. The authoritative DNS provider must publish the actual records.

3. Can Google Workspace and cPanel email use the same domain?

Yes, but the configuration must be planned carefully.

If both services send email, the SPF policy must account for both. DKIM should be configured for each sending service, and DMARC alignment should be checked.

MX records determine where incoming email is delivered, so the intended mailbox architecture must also be configured correctly.

4. Does SPF alone prevent email spoofing?

No. SPF checks authorised sending sources for the relevant envelope-sender domain. It does not independently provide all the protections offered by DKIM and DMARC.

5. What is the recommended DMARC policy for beginners?

A monitoring policy using p=none is a practical starting point when you are still identifying and testing legitimate email sources.

After reviewing authentication reports and correcting issues, you can consider moving to quarantine and eventually reject.

6. How long does SPF, DKIM and DMARC DNS propagation take?

DNS changes may become visible at different times depending on DNS TTL values, provider caching, and resolver behaviour. Some changes appear quickly, while others take longer.

Verify the records through public DNS lookups rather than assuming they are active immediately.

7. Will SPF, DKIM and DMARC guarantee that my emails reach the inbox?

No. Authentication helps receiving providers verify your domain, but inbox placement also depends on reputation, sending practices, spam complaints, content, and recipient behaviour.

8. Can I configure DMARC without DKIM?

A DMARC record can exist without a valid DKIM configuration, but DMARC passes only when at least one of SPF or DKIM passes with the required alignment.

Using both SPF and DKIM provides a more robust authentication setup.

9. What happens if I publish an incorrect SPF record?

Your legitimate emails may fail SPF authentication, and receiving providers may treat them as suspicious depending on the authentication results and policy. Incorrect SPF configuration can also cause problems when multiple email services send from the same domain.

10. Is DMARC useful for a small business?

Yes. Even a small business can be impersonated through email spoofing. DMARC reporting and policy controls can help protect the domain's identity and identify unexpected email sources.

Final Thoughts

Business email is an important communication channel, and protecting the domain behind it should not be overlooked.

SPF, DKIM and DMARC work together to authenticate email sources, verify message signatures, and communicate how receiving servers should handle authentication failures.

For Indian businesses using cPanel hosting, Google Workspace, Microsoft 365, or third-party email platforms, the first step is to identify every legitimate sending service and configure the correct DNS records.

Do not copy random DNS values or immediately enforce a strict DMARC policy. Configure the records provided by your email service, test the results, review authentication reports, and make changes carefully.

A properly planned SPF DKIM DMARC setup gives your business domain a stronger foundation for secure and reliable email communication.

Need help with your business email and domain configuration?

Arctis Digital provides domain and DNS management, cPanel hosting, website maintenance, and technical support for business websites.

Visit Arctis Digital or contact our team to discuss your requirements.

Official References and Useful Resources

Related Guides from Arctis Digital