--- schema_version: "1" id: fef215d2977507c8b725d533863ff7b80c8c746fbeb5416f269d144b655b5520 title: Use a Temporary Non-HTTPS Domain to Serve Your Custom Domain collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/domain_mgmt_temp_domain.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_temp_domain.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 4cd075c59fb655749e8ff0ace7698b3ff81e8e8de107e2d46f8f94290628f36a description: Salesforce requires that you serve your custom domain via HTTPS. However, some configuration steps can require a temporary non-HTTPS configuration. If your HTTPS certificate isn’t ready to be uploaded to Salesforce, you can use a temporary domain to start configuring your custom URLs. Also, when your domain serves other content, or when you want to move a custom domain to a new production org, you can use a temporary domain to minimize disruption to your domain. products: - Salesforce Platform - Security release: "264" --- # Use a Temporary Non-HTTPS Domain to Serve Your Custom Domain Salesforce requires that you serve your custom domain via HTTPS. However, some configuration steps can require a temporary non-HTTPS configuration. If your HTTPS certificate isn’t ready to be uploaded to Salesforce, you can use a temporary domain to start configuring your custom URLs. Also, when your domain serves other content, or when you want to move a custom domain to a new production org, you can use a temporary domain to minimize disruption to your domain. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, and Unlimited Editions.
Applies to: Salesforce Sites and LWR, Aura, and Visualforce sites
User Permissions Needed
To view a domain:

Manage Custom Domains

OR

View Setup and Configuration
To add a domain:

Manage Custom Domains

OR

View Setup and Configuration plus either a Site.com Publisher license or Create and Set Up Experiences
To edit or delete a domain: Manage Custom Domains
To add, edit, and delete custom URLs:

Manage Custom Domains

OR

View Setup and Configuration AND either Create and Set Up Experiences OR a Site.com Publisher license
![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_tip.png) Tip Unfamiliar with terms like DNS, CNAME, and FQDN? See [Custom Domain Terminology](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_terms.htm&release=264.0.0&type=5 "Review the terms related to setting up a custom domain in Salesforce."). Before you set up a temporary non-HTTPS domain, complete the custom domain [prerequisites](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_prereqs.htm&release=264.0.0&type=5 "Before you serve your site content with a custom domain, register a domain. To get that domain ready to serve your site content, update the Domain Name System (DNS) record to point to your org. Review your site URLs for potential conflicts, and complete the prerequisites for your chosen domain configuration option."). The steps to point your domain to your Salesforce org are included in this topic. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png) Note This option is a temporary configuration. When your custom domain is served via HTTP, users who attempt to access your custom domain via HTTPS can see a certificate mismatch error and experience a connection timeout. 1. Determine how to serve your domain with HTTPS after you complete the steps that require a temporary non-HTTPS domain. See [Determine How to Serve Your Custom Domain](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_determine_configuration.htm&release=264.0.0&type=5 "To determine the recommended domain configuration option to serve your custom domain, answer a few questions about your domain and your Salesforce configuration."). 2. If your fully qualified domain name (FQDN) doesn’t have an existing an A, AAAA, or CNAME record in DNS, add a CNAME record that points to your internal Salesforce CNAME. Work with your DNS provider to complete this step. See [Point Your Custom Domain to Your Salesforce Org](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_update_dns.htm&release=264.0.0&type=5 "Before you add a domain in Salesforce, point your domain to your Salesforce org in Domain Name Service (DNS). If your custom domain uses your HTTPS Certificate or the Salesforce content delivery network (CDN) partner, add a canonical domain name (CNAME) record for your fully qualified domain (FQDN) to DNS. The CNAME record references your Salesforce org ID and your FQDN. Then, if you plan to use the Salesforce CDN to serve your Experience Cloud site on your custom domain, add a second CNAME record that our CDN partner requires."). 3. If an A, AAAA, or CNAME record exists for your FQDN in DNS, add a DNS TXT record to validate your ownership of the domain. When your domain’s DNS record points to a service or server, either through an A or AAAA (address) record that points to an IP address or through an existing CNAME record, removing or updating the existing pointers in DNS can disrupt your website until you set up and activate the custom domain in Salesforce. To avoid unnecessary downtime, add a DNS TXT record to verify ownership. After you activate your custom domain in Salesforce, you can delete the TXT record. The domain for which we add the TXT record in DNS varies based on your current configuration. 1. If an A or AAAA record exists for your FQDN in DNS, add a DNS TXT record for your FQDN that equals your 18-character org ID. Work with your DNS provider to complete this step. The TXT record has no effect on the mapping of the existing A or AAAA record. Here’s an example of a DNS TXT record for www.example.com that contains an org ID. ``` Name TTL CLASS TYPE VALUE -------------------------------------------------------------------- www.example.com. 600 IN TXT "00d000000000000map" ``` 2. If a CNAME record exists for your FQDN in DNS, add a DNS TXT record for the parent domain of your FQDN that equals your 18-character org ID. Work with your DNS provider to complete this step. A domain can't have both a CNAME and a TXT record in DNS. So, to avoid downtime for your FQDN, we're going to add a parent domain as a temporary custom domain in Salesforce. Later, the verification process automatically approves your FQDN as a subdomain of an existing custom domain. To allow Salesforce to verify your ownership of the the parent domain, add a DNS TXT record for the parent domain of your FQDN that points to your 18-digit internal Salesforce CNAME. For example, if the FQDN that you want to serve your site content is www.example.com, add a TXT record for the parent domain example.com in DNS. Here’s an example of a DNS TXT record for example.com that contains an org ID. ``` Name TTL CLASS TYPE VALUE -------------------------------------------------------------------- example.com. 600 IN TXT "00d000000000000map" ``` 4. From Setup, in the Quick Find box, enter Domains, and then select **Domains**. 5. Click **Add a Domain**. 6. For Domain Name, enter the FQDN that matches the TXT record that you added in DNS. Salesforce validates that the domain points to your org via the TXT message. For example, if you added a TXT record in DNS for example.com a parent domain of www.example.com, enter example.com. 7. For Domain Configuration Option, select **Use a temporary non-HTTPS domain**. ![Domain screen with the option to use a temporary domain selected.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/domain_add_temp.png) 8. For Associated Org, select the org from which you want this custom domain to serve site content. For example, to create a temporary custom domain in your production org, select **Production**. Or select a sandbox where you want to test this custom domain. This field only appears in production orgs with associated sandboxes. You can edit this field only from production orgs. For more information, see [Test Your Custom Domains in a Sandbox](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_sandbox_custom_domains.htm&release=264.0.0&type=5 "Develop and test your custom domains that serve content from your Experience Cloud sites and Salesforce Sites in a sandbox before you activate the domain in production."). 9. Save your domain. After you save your new domain, Salesforce provisions the domain or gets it ready to be used. Provisioning can take up to 8 hours. During provisioning, your site can be inaccessible and your site visitors can experience errors. When that process is complete, the domain’s status on the Domains Setup page changes to Awaiting Activation and you receive an email. 10. To configure your domain to serve your sites, [add a custom URL](https://help.salesforce.com/s/articleView?id=platform.custom_url_add.htm&release=264.0.0&type=5 "To specify the site to load when users access your custom domain, add a custom URL. Optionally, you can define additional relationships between your domains and sites by mapping paths for your domain to your sites."). When you add the first custom URL for your domain, Salesforce provisions the domain or gets it ready to be used. The provisioning process can take up to 8 hours. During provisioning, your site can be inaccessible and your site visitors can experience errors. When that process is complete, the domain’s status on the Domains Setup page changes to Awaiting Activation and you receive an email. 11. To activate your domain, on the Domains Setup page, click **Activate** next to your custom domain name. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png) Note Custom domains for a sandbox are edited and activated in production. Your site can be unavailable for 5–10 minutes, so activate your custom domain when your site traffic is low. When your site is active, the status changes from Awaiting Activation to Completed and the Current Domain Configuration Option changes to No HTTPS (Temporary). 12. If you added a parent domain, add another temporary non-HTTPS domain for your FQDN that points to another service or server with a CNAME record. 1. On the Domains Setup page, click **Add a Domain**. 2. For Domain Name, enter the FQDN for your domain. For example, if you added example.com as a temporary non-HTTPS domain so that you can add www.example.com as a custom domain, enter www.example.com. This domain name passes the Salesforce verification check because www.example.com is a subdomain of example.com and example.com is an existing domain in Salesforce. 3. For Domain Configuration Option, select **Use a temporary non-HTTPS domain**. 4. For Associated Org, select the org from which you want this custom domain to serve site content. For example, to create a temporary custom domain in your production org, select **Production**. Or select a sandbox where you want to test this custom domain. This field only appears in production orgs with associated sandboxes. You can edit this field only from production orgs. For more information, see [Test Your Custom Domains in a Sandbox](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_sandbox_custom_domains.htm&release=264.0.0&type=5 "Develop and test your custom domains that serve content from your Experience Cloud sites and Salesforce Sites in a sandbox before you activate the domain in production."). 5. Save your domain. After you save your new domain, Salesforce provisions the domain or gets it ready to be used. Provisioning can take up to 8 hours. During provisioning, your site can be inaccessible and your site visitors can experience errors. When that process is complete, the domain’s status on the Domains Setup page changes to Awaiting Activation and you receive an email. 6. To activate your domain, on the Domains Setup page, click **Activate** next to your custom domain name. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png) Note Custom domains for a sandbox are edited and activated in production. Your site can be unavailable for 5–10 minutes, so activate your custom domain when your site traffic is low. When your site is active, the status changes from Awaiting Activation to Completed, and the Current Domain Configuration Option changes to No HTTPS (Temporary). 7. To configure your domain to serve your sites, [add a custom URL](https://help.salesforce.com/s/articleView?id=platform.custom_url_add.htm&release=264.0.0&type=5 "To specify the site to load when users access your custom domain, add a custom URL. Optionally, you can define additional relationships between your domains and sites by mapping paths for your domain to your sites."). 13. Update your domain to use HTTPS. Until you activate the domain, the configuration uses HTTP. 1. If your domain serves content from another service, see [Change the Domain Configuration Option for Your Custom Domain](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_change_service.htm&release=264.0.0&type=5 "Change the method for serving your domain. For example, switch from a third-party service or content delivery network (CDN) to the Salesforce CDN. Update your domain in Salesforce to use a different third-party service or CDN to serve your site. Or update a temporary non-HTTPS domain to use HTTPS as required by Salesforce."). 2. To move your custom domain to a new production org, see [Move a Domain to Another Production Org](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_move.htm&release=264.0.0&type=5 "If you purchase a new production org, your old org continues to serve your sites with your custom domain. To move the domain to your new org, set up the domain, and then delete the domain in your old org. Or if you have multiple production orgs, you can move an existing domain to an org of your choice."). 14. When your updated domain is live, remove any temporary configuration in Salesforce and in DNS. 1. Delete any temporary non-HTTPS domains that are no longer needed. See [Delete a Domain](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_delete.htm&release=264.0.0&type=5 "To stop serving a site via your custom domain, such as https://www.example.com, first delete the custom URLs for that domain. Then delete the domain in Salesforce. Or to point the domain to a different site, set up new custom URLs."). 2. In DNS, delete the TXT records that you added to set up the temporary domain. Work with your DNS provider to complete this step. This diagram shows the routing of traffic when Salesforce serves your domain as a temporary non-HTTPS domain. Dotted lines (![dotted line](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/arrow_dotted.png)) represent DNS configurations, and the solid line (![solid line](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/arrow_solid.png)) represents user traffic flow through HTTP. The gray line represents traffic that originates outside Salesforce, and the blue lines represent traffic that originates in Salesforce. In this example, the domain name is www.example.com and the 18-digit org ID is 00d000000000000013. ![Connectivity diagram for a custom domain that uses a temporary non-HTTPS domain.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/custom_domain_temp_http.png) To confirm ownership of your custom domain (1), with your DNS provider, you point the domain to the Salesforce internal CNAME (2), which includes your org ID, via a CNAME or TXT record. If a CNAME record routes traffic to Salesforce, Salesforce uses an HTTP-only endpoint that’s served on a secure server (3) to serve the content from your Experience Cloud site (4). However, the hosted certificate (3) supports only HTTP on the custom domain instead of HTTPS. Also, the returned certificate creates a hostname-mismatch error because that certificate doesn't support the custom domain name. #### See Also - [Custom Domains](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt.htm&release=264.0.0&type=5 "Provide a branded experience for users who access your external-facing Salesforce content by serving your Digital Experiences or Salesforce Sites on a domain that you own, such as https://www.example.com.") - [Custom Domain Management](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_dom_detail.htm&release=264.0.0&type=5 "Keep your custom domain up to date with your business needs. Learn how to manage your domain during org migrations and certificate changes. Edit your domain’s configuration option, move to a different domain name, or enable HSTS preloading. And when you no longer need a custom domain, delete the domain and its custom URLs in Salesforce.")