> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/custom-domain-setup.md).
# Custom Domain Setup
Move your Reach-powered brand from a Reach subdomain to your own custom domain with validated DNS, SSL, CDN, redirects, and integration checks.
### Overview
Custom Domain Setup moves your Reach-powered brand from a Reach-issued subdomain to a domain you own.
For example, `brand.reachmobile.com` becomes `brand.com`. Reach validates the DNS, SSL certificate, CDN, redirects, and domain-dependent integrations before cutover.
This bolt-on helps preserve existing links while establishing your permanent brand domain.
Buy this bolt-on
{% hint style="info" %}
Use Custom Domain Setup when moving from a pilot subdomain, launching publicly, or completing a rebrand.
{% endhint %}
### What is included
| Area | Reach provides |
| --------------------- | ----------------------------------------------------------------------------------------- |
| DNS and CDN | DNS setup or record handoff, plus CDN configuration |
| Domain security | SSL certificate configuration and validation |
| URL continuity | Redirects from the prior Reach subdomain to the custom domain |
| Integration readiness | Re-whitelisting for login, maps, autocomplete, and device store services where applicable |
| Post-launch support | Monitoring and support for 30 days after cutover |
### Benefits of a custom domain
* **Brand continuity:** Use your own domain across customer journeys and marketing.
* **SEO continuity:** Redirect the former subdomain to preserve links and search visibility.
* **Validated launch:** Confirm security, routing, and affected integrations before go-live.
* **Flexible DNS ownership:** Let Reach manage DNS or retain control through your registrar.
### When to use this bolt-on
Custom Domain Setup is suited to these scenarios:
| Scenario | Outcome |
| ----------------------- | ----------------------------------------------------------------------- |
| Public launch | Replace a temporary Reach subdomain with a customer-facing brand domain |
| Rebrand | Move branded web journeys to a new domain with redirects in place |
| Pilot graduation | Establish a permanent domain after a pilot or proof of concept |
| Marketing consolidation | Direct campaigns, backlinks, and customer traffic to one domain |
### Scope and responsibilities
#### Included
* DNS setup or the required DNS record handoff
* SSL certificate and CDN configuration
* Redirect configuration for the former subdomain
* Login, maps, autocomplete, and device store re-whitelisting where applicable
* Coordination for email sender and receiver DNS records
* Brand configuration updates and 30 days of post-cutover support
#### Not included
* Domain registration or purchase, unless explicitly agreed
* Email inbox hosting or management
Your email provider remains customer-managed. This includes providers such as Google Workspace and Microsoft 365. Reach configures only the DNS records needed for the custom domain cutover.
### Information needed from your team
Provide these details before implementation begins:
1. Your custom domain and whether `www` is required.
2. Your DNS ownership model: Reach-managed or customer-managed.
3. Registrar access, or confirmation you can apply supplied DNS records.
4. Your email provider and DNS records that must remain unchanged.
5. Whether the device store is enabled for your brand.
### Custom domain migration process
{% stepper %}
{% step %}
#### Confirm the domain requirements
Reach and your team confirm the domain, DNS owner, email requirements, and dependent services.
{% endstep %}
{% step %}
#### Configure DNS, SSL, and CDN
Reach configures the required services. If you manage DNS, Reach supplies the records for your team to apply.
{% endstep %}
{% step %}
#### Apply and validate DNS records
Your team applies the records when DNS is customer-managed. Reach validates the configuration before cutover.
{% endstep %}
{% step %}
#### Complete the custom domain cutover
Reach enables the SSL certificate and CDN, redirects the prior subdomain, and re-whitelists affected integrations.
{% endstep %}
{% step %}
#### Verify customer journeys
Reach tests the website, login, autocomplete, redirects, and email configuration where applicable.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Configuration takes a few hours after prerequisites are confirmed. DNS propagation can take 24–48 hours.
{% endhint %}
### Cutover validation checklist
Reach confirms the following before closing the cutover:
* The custom domain loads securely with a valid SSL certificate.
* The former Reach subdomain redirects to the custom domain.
* Login, signup, and address autocomplete work as expected.
* Email remains reachable on the new domain, where in scope.
* The device store loads correctly, where enabled.
### Related bolt-ons
* Review the standard process in [Bolt-ons catalog](/customizations-and-bolt-ons/bolt-ons-catalog.md).
* Align domain ownership with [Custom App Hosting](/customizations-and-bolt-ons/bolt-ons-catalog/custom-app-hosting.md).
* Review customer login requirements in [SSO — End Customers](/customizations-and-bolt-ons/bolt-ons-catalog/sso-end-customers.md).
### Pricing
Custom Domain Setup is a one-time onboarding engagement. Scope depends on your domain and email requirements. Contact your Account Manager for a proposal.
### Frequently asked questions
#### Can we keep our current DNS registrar?
Yes. Your team can retain DNS management. Reach provides the required records and validates them after application.
#### Will the old subdomain continue to work?
Yes. Reach configures redirects from the prior subdomain to the custom domain. This helps preserve bookmarks, shared links, and search visibility.
#### Does Reach manage our email inboxes?
No. Your existing email provider continues to manage inboxes. Reach coordinates only the DNS records needed for the domain migration.
Buy this bolt-on
### Questions or support
Questions or need clarification? Reach out to your respective Account Manager or email us at for assistance and support.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.reachplatform.com/customizations-and-bolt-ons/bolt-ons-catalog/custom-domain-setup.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.