Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Why are we enabling Enhanced Domains?

Enhanced domains are the current version of My Domain that meets the latest browser requirements. With enhanced domains, all URLs across your org contain your company-specific My Domain name, including URLs for your Experience Cloud sites, Salesforce Sites, Visualforce pages, and content files. This feature changes domain suffixes (the part after the My Domain name) to meet the latest security standards. With no instance names, enhanced My Domain URLs are easier for users to remember and don’t change when your org is moved to another Salesforce instance. Because enhanced domains meet the latest browser requirements, they’re deployed by default in new orgs and required in all orgs in Winter ’24.

Link to Official Salesforce notes here

My Domain URL Format Changes When You Enable Enhanced Domains

...

If the Stabilize URLs for Visualforce, Experience Builder, Site.com Studio, and content files setting isn’t enabled before you enable and deploy enhanced domains, these production URL formats change.

URL TYPE

FORMAT

URL FORMAT

REMARKS

1

Content (Files) in a non-Hyperforce org

Old

MyDomainName--c.InstanceName.content.force.com

2

New

MyDomainName.file.force.com

3

Content (Files) in a Hyperforce org

Old

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

4

New

MyDomainName.file.force.com

5

Experience Builder in a non-Hyperforce org

Old

MyDomainName--sitestudio.InstanceName.force.com

6

New

MyDomainName.builder.salesforce-experience.com

7

Experience Builder in a Hyperforce org

Old

MyDomainName--sitestudio.InstanceName.sfdc-HyperforceInstanceName.force.com

8

New

MyDomainName.builder.salesforce-experience.com

9

Experience Builder Live Preview in a non-Hyperforce org

Old

MyDomainName--livepreview.InstanceName.force.com

10

New

MyDomainName.live-preview.salesforce-experience.com

11

Experience Builder Live Preview in a Hyperforce org

Old

MyDomainName--livepreview.InstanceName.sfdc-HyperforceInstanceName.force.com

12

New

MyDomainName.live-preview.salesforce-experience.com

13

Experience Builder Preview in a non-Hyperforce org

Old

MyDomainName--sitepreview.InstanceName.force.com

14

New

MyDomainName.preview.salesforce-experience.com

15

Experience Builder Preview in a Hyperforce org

Old

MyDomainName--sitepreview.InstanceName.sfdc-HyperforceInstanceName.force.com

16

New

MyDomainName.preview.salesforce-experience.com

17

Visualforce in a non-Hyperforce org

Old

MyDomainName--PackageName.InstanceName.visual.force.com

18

New

MyDomainName--PackageName.vf.force.com

19

Visualforce in a Hyperforce org in a Hyperforce org

Old

MyDomainName--PackageName.InstanceName.visual.sfdc-HyperforceInstanceName.force.com

20

New

MyDomainName--PackageName.vf.force.com