This article explains how to configure a custom domain so that users can access the platform using an address of their own organization, instead of the standard domain assigned by SMARTFENSE.
Prerequisite
Before registering a custom domain, the organization must have at least one validated corporate domain. This step is mandatory and is performed on the same screen, in the Corporate Domains section.
If you have no validated corporate domains available, pressing New custom domain shows the platform's notice: "Important: You have no validated corporate domains available. Add and validate a corporate domain before registering a custom domain."
See the guide: How to validate a domain in SMARTFENSE.
Definitions
-
Standard domain: the address SMARTFENSE assigns by default (for example,
instancia.takesecurity.com). It remains always available, even after configuring your own domain. - Custom domain: a domain of your own organization that you add to access the platform with your own address.
- Primary domain: the domain the platform uses at any given time for access and for the links it sends (emails, campaigns). Only one can be active at a time, and it can be changed at any time.
Where to configure it
Go to Settings > Organization > Corporate Domains. At the bottom of the screen you will find the Custom domains section.
How to register a custom domain
- Press the New custom domain button.
- In the Domain field, select the already validated corporate domain you want to use to browse the platform. The dropdown only lists validated domains that have not yet been registered as custom.
- Press Register.
Once registered, the platform generates a DNS target for that domain and adds it to the Custom domains table, with status Registered.
- In your DNS provider, create a CNAME record pointing your domain to the DNS target shown in the table.
If you are using a root domain (for example,
mycompany.com), your DNS provider must support ALIAS or ANAME records, since CNAME records cannot be created on a root domain. For a subdomain, a CNAME record is enough.
- Once the DNS change has propagated, mark the domain as primary by pressing the Mark as primary button in the Custom domains table.
When you press Mark as primary, the platform asks for confirmation through the Mark domain as primary dialog:
Note: before applying the change, the platform will verify that the domain already points correctly to your instance. Links generated by the platform will start using the new primary domain.
Warning: your instance has authentication methods or integrations whose redirect addresses are built from the primary domain. When you change the primary domain, the platform will use the new domain in those addresses. You must register them in the corresponding provider's configuration; otherwise, login or those integrations may stop working.
Confirm by pressing Accept only after you have updated the redirect addresses in every relevant authentication provider and integration (for example, SSO, phishing report button).
If you do not manage your organization's DNS, request the record creation from your IT/systems team.
Custom domains table
The table shows, for each domain, the columns Domain, DNS target, Status (Registered or Primary) and Actions (Mark as primary, Delete). The standard domain always appears in the table, with no DNS target and no available actions: it cannot be deleted.
Frequently asked questions
What are the DNS target and the CNAME record, and where are they configured? When you register your domain, the platform shows you a DNS target. You must go to your DNS provider's panel and create a CNAME record pointing your domain to that DNS target.
How long does it take to become available? It depends on the propagation of the DNS change, which can take anywhere from a few minutes to several hours. The security certificate (HTTPS) is issued automatically once the domain points to the platform.
How do I go back to using the standard domain? Mark the standard domain as primary from the table. If you also want to stop using a custom domain, delete it; it must first stop being the primary domain.
Why can't I delete the primary domain? To prevent the platform from being left without a valid access address. Mark another domain as primary, and you will then be able to delete the previous one.
💡 Best practices
- Validate the corporate domain first, before trying to register the custom domain, to avoid the blocking notice.
- Confirm with the customer's IT/systems team whether the domain to be used is a root domain or a subdomain, since that determines whether a CNAME or an ALIAS/ANAME record is needed.
- Wait for full DNS propagation before marking the domain as primary, to avoid access interruptions.
- Keep the standard domain available as a backup in case of any DNS issue with the custom domain.
- Inform users of the access address change before marking the new domain as primary.
- Update the redirect addresses in every SSO provider and integration before confirming the primary domain change, to avoid login or those integrations stopping working.