--- schema_version: "1" id: af59822a54d7371aa6ee3bfd28607761c2e4426139a51175dfc3cb4520fd2a50 title: Verify Your Email Domain Ownership collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_general_verify_email_domain.md canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_general_verify_email_domain.htm&release=260&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a281157148ec03f431e4dabd55b813bbdc416ae13b699aee9531b0cc88086d7b description: To avoid disruption in email sent from Salesforce, verify the domains that you own with a DomainKeys Identified Mail (DKIM) key or an authorized email domain. As part of our ongoing efforts to strengthen the security of our email services, email domain verification is now mandatory. Salesforce no longer delivers emails from unverified domains, even if the email addresses are verified. products: - Cross Cloud Packages Solutions release: "260" --- # Verify Your Email Domain Ownership To avoid disruption in email sent from Salesforce, verify the domains that you own with a DomainKeys Identified Mail (DKIM) key or an authorized email domain. As part of our ongoing efforts to strengthen the security of our email services, email domain verification is now mandatory. Salesforce no longer delivers emails from unverified domains, even if the email addresses are verified. **Where:** This change applies to Lightning Experience and Salesforce Classic in all editions except Salesforce Free Suite and Database.com. This change has no impact on trial orgs. This change doesn't affect emails sent through Gmail™ and Office 365® (Outlook) integrations or via Einstein Activity Capture tool (“Inbox”). Emails that end in @gmail.com, @hotmail.com, or @outlook.com are also exempt from the domain-level verification requirement. And domain verification isn’t required for Marketing Cloud or Marketing Cloud Advanced emails. **When:** In existing orgs, Salesforce generated a temporary allowlist of email-sending domains used over several weeks in January and February 2026 For more information, see [Determine Your Temporarily Allowlisted Email-Sending Domains](https://help.salesforce.com/s/articleView?id=005316952&type=1&language=en_US). These changes take effect shortly after your org gets Spring '26, patch 11. - Verification is required for all email-sending domains added after February 25, 2026, regardless of whether you add the domain to a new or existing org. - Verification is required for existing email-sending domains that aren’t allowlisted. - In sandboxes, verification of the allowlisted domains is required starting April 14, 2026. - In all other orgs, including production, verification of the allowlisted domains is required starting May 4, 2026. For more information, see these knowledge articles: [Mandatory Sending-Email Domain Verification Timeline](https://help.salesforce.com/s/articleView?id=005316660&type=1&language=en_US) and [Spring ’26 Email-Sending Domain Verification Requirement](https://help.salesforce.com/s/articleView?id=005316090&type=1&language=en_US). **Why:** This change affects emails sent from Salesforce and related automations with an email-sending domain that Salesforce doesn't own, including system-generated emails. For example, if your users' email addresses are in the format `name@example.com`, verify that you own `example.com`. Similarly, Salesforce can't send system-generated emails from an organization-wide address with an unverified domain, even if the individual email address is verified. **How:** Verify each of your email-sending domains. Each domain and subdomain requires separate verification via an active DKIM key. If you can’t use a DKIM key, configure a verified entry in the Authorized Email Domains list in Setup. To minimize disruption, enable a substitute email address for unverified domains. From Setup, in the Quick Find Box, enter Deliverability, and then select **Deliverability**. Select **Use a substitute email address for unverified domains**, and save your changes. Salesforce plans to make that option available in late April 2026. #### See Also - [Send Email for Users with an Unverified Email Domain](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_productivity_email_substitute_unverified.htm&release=260&type=5 "Enable users whose email domains you can't verify—such as users with public email addresses, consultants, and site users—to send email from Salesforce. With your substitute email address, the user's display name and reply-to address remain unchanged, but the From address uses email@UniqueId.sfcustomeremail.com, where UniqueId is your org ID or Experience Cloud site ID. This option also applies to system-generated emails and emails sent via shared email accounts with an unverified domain.") - [Check Your Domain’s Verification Status](https://help.salesforce.com/s/articleView?id=release-notes.rn_sales_check_domain_verification_status.htm&release=260&type=5 "To avoid email delivery failures for emails sent from Salesforce, check your domain’s verification status. Salesforce now sends emails only from verified domains.") - [_Salesforce Help:_ Requirements to Send Email from Salesforce](https://help.salesforce.com/s/articleView?id=xcloud.security_email_verification_requirements.htm&language=en_US) - [_Salesforce Help:_ Verify a Sending Email Domain](https://help.salesforce.com/s/articleView?id=xcloud.security_user_email_verification_domain_auth.htm&language=en_US) - [_Salesforce Help:_ Set Up Secure DKIM Keys](https://help.salesforce.com/s/articleView?id=sales.emailadmin_setup_dkim_key.htm&language=en_US)