When a Salesforce Site (Force.com Sites) is configured with a custom domain, a CNAME record is typically created for the subdomain that includes www (for example, www.example.com). However, users who navigate to the root or "naked" domain — the domain without www (for example, example.com) — may find that the URL does not resolve correctly. Instead of loading the Salesforce Site, the naked domain redirects users to the Salesforce login page (e.g., `<REDACTED>).
This behavior occurs because most DNS registrars and the CNAME protocol do not natively support CNAME records for root (naked) domains. A separate DNS configuration is required to handle naked domain requests.
Note: The information in this article applies to non-secure (HTTP) domains only. For HTTPS custom domains, refer to the Naked Domains documentation.
Option 1: Create a Separate CNAME Record for the Naked Domain
Some DNS registrars support a separate CNAME or ALIAS record for the root domain (without www). If your registrar supports this, create an additional CNAME or ALIAS record pointing the naked domain (e.g., example.com) to the same Salesforce Sites CNAME target as the www subdomain. Contact your DNS registrar to confirm support for this configuration. read our Documentation about Naked Domains.
Option 2: Use a DNS Forwarder or a Second Force.com Site
If your DNS registrar does not support CNAME records for naked domains:
Alternatively, create a second Force.com Site that uses the same pages as the primary site, or that simply redirects incoming requests from the naked domain to the correct www URL.
000385794

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.