Prepare for the End of Redirections for Non-Enhanced Domains

After enhanced domains deployment, Salesforce redirected three categories of non-enhanced host names.

• Your previous *.force.com site host names.
• Other previous non-enhanced My Domain host names.
• If your org was created before Summer ’20, some host names that contained your instance name but not your My Domain name.

To see if redirections are in place for a previous My Domain, check the Redirections section of the My Domain Setup page.

Warning My Domain URL redirections help prevent disruption, but they’re not intended as a permanent solution. Not all services work well with redirections, and a redirection adds a step to the process of loading the final web page. Whenever you deploy a new My Domain, we highly recommend that you disable redirections during testing and update all references to your old URLs.

Track the Source of Redirections

After you search the metadata for your org to determine where the impacted URLs are used in Salesforce, discovering all the other places that your URLs are used can be more complex. For example, site URLs and content URLs can be used on your website, Social media pages, marketing materials, and templates, such as email signatures and automated responses. To help you identify these locations outside of Salesforce, the Hostname Redirects event type includes the referrer and origin sent with each request that Salesforce redirects.

Even though Salesforce stopped redirections for legacy (non-enhanced) host names, the Hostname Redirects event type still captures blocked attempts to access the legacy host names. For these events, the REDIRECT_REASON is Redirection was blocked because redirections for the legacy SOURCE_HOSTNAME are no longer supported.

For more information, see Log My Domain Host Name Redirections.

Notify Users During Redirections

To help your users update outdated links and bookmarks, show a brief message during the redirection that provides the current URL. See Manage My Domain Redirections.

Previous *.force.com Site Host Names

When you enabled and deployed enhanced domains, the host name formats changed for your Experience Cloud sites and Salesforce Sites. For the replacement format for each of these host names, see My Domain URL Format Changes with Enhanced Domains Deployment. To understand the purpose of each host name type and whether it applies to you, see My Domain Host Names.

Here are the *.force.com site host names for a production org that are no longer redirected.

• ExperienceCloudSiteSubdomain.force.com
• SitesSubdomainName.force.com
• SitesSubdomainName.secure.force.com

Here are the .*force.com site host names for a sandbox that are no longer redirected.

• SandboxName-ExperienceCloudSiteSubdomain.InstanceName.force.com
• SandboxName-SitesSubdomainName.InstanceName.force.com

Instanced Login Host Name in API Calls

Before all orgs had a My Domain, some customers accessed Salesforce with their instanced URL, such as https://na42.salesforce.com, especially in code and API calls. Salesforce doesn’t recommend using that login URL. First, API calls to a Hyperforce org can’t use that method. Second, when your org is moved to another Salesforce instance, code and API calls that use the instanced URL break.

Although API traffic that uses your correct instanced URL continues to work after these changes, that API traffic stops working if your org’s instance changes. Your org’s instance name can change during regular maintenance, such as an instance refresh, or during a migration to the latest infrastructure, such as Hyperforce. For that reason, we recommend that you use your My Domain login URL in API calls.

API traffic that uses an incorrect instanced URL stops working on a rolling basis shortly after your org gets the Winter ’27 release. To test this change before that change is enforced, enable Block API traffic that uses an incorrect instanced URL in the Redirections section of the My Domain page in Setup after June 18, 2026.

Warning If you enable “Block API traffic that uses an incorrect instanced URL” before the related known issue is resolved, SOAP login URLs via Visualforce pages can return a 400 Bad Request error. Salesforce plans to deploy a fix for that issue June 16–18, 2026, so we recommend that you test this change after June 18, 2026.

For more information, see End-of-Support Schedule for Incorrect Instanced URLs in API Traffic.

Other Non-Enhanced My Domain Host Names

When you enabled and deployed enhanced domains, your other previous non-enhanced My Domain host names were redirected. For the updated formats for each of these host names, see My Domain URL Format Changes with Enhanced Domains Deployment. To better understand the purpose of each host name type and whether it applies to you, see My Domain Host Names.

Here are the non-enhanced host names for a production org that were temporarily redirected after you enabled and deployed enhanced domains.

• MyDomainName--PackageName.container.lightning.com ¹
• MyDomainName--c.documentforce.com
• MyDomainName.builder.salesforce-communities.com
• MyDomainName.livepreview.salesforce-communities.com
• MyDomainName.preview.salesforce-communities.com
• MyDomainName--UniqueID.a.forceusercontent.com
• MyDomainName--UniqueID.c.my.force-user-content.com
• MyDomainName--PackageName.visualforce.com ¹
• MyDomainName--c.InstanceName.content.force.com
• MyDomainName--sitestudio.InstanceName.force.com
• MyDomainName--livepreview.InstanceName.force.com
• MyDomainName--sitepreview.InstanceName.force.com
• MyDomainName--PackageName.InstanceName.visual.force.com ¹
• MyDomainName--sitestudio.InstanceName.sfdc-HyperforceInstanceName.force.com
• MyDomainName--livepreview.InstanceName.sfdc-HyperforceInstanceName.force.com
• MyDomainName--sitepreview.InstanceName.sfdc-HyperforceInstanceName.force.com
• MyDomainName--c.InstanceName.content.sfdc-HyperforceInstanceName.force.com
• MyDomainName--PackageName.InstanceName.visual.sfdc-HyperforceInstanceName.force.com ¹

Here are the non-enhanced host names for a sandbox that were temporarily redirected after you enabled and deployed enhanced domains.

• MyDomainName--SandboxName.my.salesforce.com
• MyDomainName--SandboxName.lightning.force.com
• MyDomainName--SandboxName--PackageName.container.lightning.com ¹
• MyDomainName--SandboxName--UniqueID.b.forceusercontent.com
• MyDomainName--SandboxName--UniqueID.c.forceusercontent.com
• MyDomainName--SandboxName--c.documentforce.com
• MyDomainName--SandboxName.builder.salesforce-communities.com
• MyDomainName--SandboxName.livepreview.salesforce-communities.com
• MyDomainName--SandboxName.preview.salesforce-communities.com
• MyDomainName--SandboxName.InstanceName.my.salesforce.com
• MyDomainName--SandboxName--PackageName.visualforce.com ¹
• MyDomainName--SandboxName--c.InstanceName.content.force.com
• MyDomainName--SandboxName--sitestudio.InstanceName.force.com
• MyDomainName--SandboxName--livepreview.InstanceName.force.com
• MyDomainName--SandboxName--sitepreview.InstanceName.force.com
• MyDomainName--SandboxName--PackageName.InstanceName.visual.force.com ¹
• MyDomainName--SandboxName--c.InstanceName.content.sfdc-HyperforceInstanceName.force.com
• MyDomainName--SandboxName--sitestudio.InstanceName.sfdc-HyperforceInstanceName.force.com
• MyDomainName--SandboxName--livepreview.InstanceName.sfdc-HyperforceInstanceName.force.com
• MyDomainName--SandboxName--sitepreview.InstanceName.sfdc-HyperforceInstanceName.force.com
• MyDomainName--SandboxName--PackageName.InstanceName.visual.sfdc-HyperforceInstanceName.force.com ¹

¹ If your installed package is unmanaged, the package name is c.

Instanced URLs Without My Domain

If your org was created before October 2020, you didn’t get a My Domain by default. In that case, your users accessed Salesforce with these host names that contained your instance name but not your My Domain name. These URLs are no longer valid.

• InstanceName.lightning.force.com
• InstanceName.salesforce.com ¹
• ExperienceCloudSiteSubdomainName--builder.InstanceName.force.com
• ExperienceCloudSiteSubdomainName--preview.InstanceName.force.com
• ExperienceCloudSiteSubdomainName--live.InstanceName.force.com
• sitestudio.InstanceName.force.com
• sitepreview.InstanceName.force.com
• livepreview.InstanceName.force.com
• InstanceName--UniqueID.a.forceusercontent.com
• InstanceName--UniqueID.b.forceusercontent.com
• InstanceName--UniqueID.c.forceusercontent.com
• c.InstanceName.content.force.com
• PackageName.InstanceName.visual.force.com ¹
• Region.scrt.sfdc.sh

¹ The My Domain redirection settings have no impact on redirections for API requests to this host name.

² If your installed package is unmanaged, the package name is c.

Legacy Host Names That Contain an Instance Name

With enhanced domains, your My Domain host names contain no instance names and those host names don’t change when your org moves to another Salesforce instance. For this reason, we recommend that you use your My Domain host names instead of host names that contain an instance.

Notice that some of the legacy host names include your instance name. Here are two examples.

• MyDomainName--c.InstanceName.content.force.com
• MyDomainName--c.InstanceName.visual.sfdc-HyperforceInstanceName.force.com

Those host names are no longer valid, even if they contain the correct instance name.