Connect your custom domain

Publish personalized Pages at a hostname such as pages.example.com. Landit hosts the Pages while visitors see your company’s domain in their browser.

This is often called white label hosting, a branded domain, or a custom subdomain. Your DNS provider points the hostname at Landit’s assigned hosting target.

You configure an existing domain with your DNS provider. You do not need to transfer the domain to Landit or create a new DNS account if your company already manages its DNS.

This guide uses a subdomain, such as pages.example.com. Arrange setup with your Landit contact so you have the exact DNS target assigned to that hostname before changing records.

Before you begin

Have the following ready:

• Access to your workspace’s Integrations → Custom domain screen.
• Permission to change DNS records for your company’s domain, or an administrator who can do it.
• An unused subdomain for your Pages.
• The exact DNS target supplied by Landit for that subdomain.
• A successful Page to use for the final check.

Keep existing website and email records intact. If the chosen hostname already serves another application, arrange the change with its owner before replacing its DNS record.

1. Choose your hostname

For a company using example.com, pages.example.com is a straightforward choice. Choose the hostname you want visitors to see:

pages.example.com

Do not include https://, a trailing slash, or a Page path. The domain setting belongs to the workspace, so coordinate changes with teammates using its Page links.

2. Add the DNS record

Before changing DNS, ask your Landit contact for the exact target assigned to your chosen hostname. The target is a hostname, not a full Page URL.

Keep your requested hostname and assigned target together when handing the task to a DNS administrator. Do not substitute Landit’s homepage, MCP endpoint, documentation domain, an IP address, or a target copied from another customer’s setup.

Open the DNS settings for example.com at the provider hosting its DNS zone. Add a record using the supplied target:

Field	Value
Type	CNAME
Name / Host	pages, or pages.example.com if your provider requires the full hostname.
Target / Value	The exact DNS target supplied by Landit for pages.example.com.
TTL	Your DNS provider’s default value, unless your administrator specifies otherwise.

Before saving, check whether the provider automatically appends example.com to the Name field. The resulting record must be for pages.example.com, not pages.example.com.example.com.

If a conflicting record already exists at that same hostname, ask your DNS administrator to review it. Do not change unrelated records. If the provider offers proxying, CDN, or forwarding options, confirm the intended setting with your Landit contact before enabling them.

Use a CNAME pointing to the exact DNS target supplied by Landit for your chosen subdomain.

3. Verify the DNS record

DNS changes take time to become visible. Before adding the domain in Landit, use your DNS provider’s lookup tool or ask your DNS administrator to confirm that the CNAME for your chosen hostname resolves to the exact target supplied by Landit.

Check the full hostname, such as pages.example.com, and compare the returned target with the assigned target. If the record is missing or points elsewhere, correct it or wait for the DNS change to become visible before continuing.

This check confirms DNS routing. HTTPS and Page loading are validated after you add the domain in Landit.

4. Add the domain in Landit

Once the DNS record is valid, open Integrations → Custom domain, enter only the chosen hostname (for example, pages.example.com), and select Add domain. Do not include https://, a trailing slash, or a Page path.

Adding the domain saves the workspace setting. Next, complete the HTTPS and Page URL validation below to finish connecting your hostname.

Coordinate this step with your Landit contact if you already have an active campaign: the domain setting changes the hostname Landit uses when producing Page URLs.

5. Validate HTTPS and a complete Page URL

Certificate readiness is a separate step from DNS verification. Ask your Landit contact to confirm the hostname is provisioned and its certificate is ready if the Page does not yet load securely.

Do not bypass a browser certificate warning to treat the setup as complete. Do not repeatedly delete and re-add the domain while waiting.

Open a successful Page URL using the configured hostname:

https://pages.example.com/your-page-slug

Replace the illustrative hostname and slug with your real values. Test the full Page path; the hostname’s root path alone is not a sufficient check.

Confirm that the browser shows the intended hostname, HTTPS has no certificate warning, the expected prospect Page loads, and its images and links work. Check from a browser outside your signed-in Landit session before using the URL in outreach.

Change or disconnect a domain

Landit requires you to delete the saved domain before adding a different one. Plan the change with your team and your Landit contact before removing anything.

Previously distributed links contain their original hostname. Changing the workspace setting does not rewrite those messages or establish redirects from the old hostname. Decide how active links will continue working before making the change, and remove obsolete DNS records as part of the coordinated teardown.

Troubleshooting

Problem	Next action
Landit rejects the hostname	Remove the protocol, slashes, and paths. Check for a domain already assigned to another workspace.
Domain is saved but does not load	Check the assigned target and DNS record, then ask your Landit contact to confirm provisioning.
Browser shows a certificate warning	Wait for HTTPS readiness and confirm it with Landit. Do not send the link yet.
Another website appears	Recheck the record at the exact hostname and any forwarding or proxy settings.
Root address fails	Test a real, successful Page’s full URL.
An older Page redirects or is unavailable	Check its age: public Pages expire two calendar months after creation.

For help, provide the requested hostname, DNS provider, record type and target, the affected Page URL, and the visible error. Keep DNS account passwords and access tokens out of support messages.

Next step

Create your first Page, or test a newly generated link under the configured domain before starting your next campaign.