If you send emails through Salesforce, there’s an important update you need to pay attention to. Starting March 9, 2026, Salesforce has rolled out a new requirement — you must now prove that you own the email domain you’re sending from.
So, What Is Email Domain Verification?
Think of it this way — when Salesforce sends an email on your behalf (say, from yourname@yourcompany.com), it now needs to confirm that your organization actually owns the domain “yourcompany.com”.
Without this verification, Salesforce will simply stop delivering those emails. That means leads, customers, and colleagues might never receive messages you send through Salesforce — without any error message warning you.
Who Does This Affect?
This affects anyone who sends emails through Salesforce using a custom company domain — like @yourcompany.com, @yourbrand.in, etc.
The good news? You’re not affected if you send emails using:
- Personal email addresses like Gmail (@gmail.com) or Outlook (@outlook.com)
- Gmail or Office 365 integrations connected to Salesforce
- Einstein Activity Capture (EAC)
- Free or trial Salesforce orgs
What Are the Deadlines?
Salesforce is giving everyone a little time to get this done, but the clock is ticking:
- New domains → Verification required right now, immediately
- Sandbox orgs (used for testing) → Verify by March 30, 2026
- Production orgs (your live Salesforce environment) → Verify by April 27, 2026
The safest move? Do it as soon as possible — don’t wait until the last day.
How Do You Verify Your Domain?
There are two ways to do this. Your IT team or Salesforce Admin will handle the technical parts, but here’s a plain-English explanation of both:
Option 1: DKIM (Recommended ✅)
DKIM stands for DomainKeys Identified Mail — it’s basically a digital signature that gets attached to your emails, proving they’re genuinely from your domain.
Setting it up involves generating a key inside Salesforce and then adding a small record to your domain’s DNS settings (that’s managed wherever you registered your domain — like GoDaddy, Cloudflare, etc.).
Once it’s active, your domain is considered verified. This is the method Salesforce recommends.
Option 2: Authorized Email Domains
If you’d rather not use DKIM, you can verify your domain through Salesforce’s Authorized Email Domains setup. Here’s how it works, step by step:
In Salesforce:
- Go to Setup and search for Authorized Email Domains in the Quick Find box
- Click Add
- Type in your domain name (e.g., yourcompany.com)
- Click Save
- Salesforce will generate a verification key — copy it
In your DNS settings (done by your IT team):
- Log into wherever your domain is managed (GoDaddy, Cloudflare, Route 53, etc.)
- Add a new TXT record with either
_sfdv.yourcompany.comoryourcompany.comas the name - Paste the verification key Salesforce gave you as the value
- Save the record
Back in Salesforce:
- Go back to Authorized Email Domains in Setup
- Find your domain and click Edit
- Turn on Verify domain ownership
- If everything is set up correctly, it’ll confirm successfully. If not, wait a few minutes for the DNS change to spread across the internet, then try again.
One More Thing — User Email Verification Still Applies
Even after your domain is verified, each individual user’s email address still needs to be verified separately. Domain verification and user verification are two different things — both are required.
crazysfdc.com 