LinksetGoDEEP LINKS, DONE RIGHT
Custom-domain guide

Verify ownership, TLS and mobile trust before changing a public hostname.

LinksetGo keeps the managed workspace URL alive while a Pro workspace proves control of its own subdomain and ships the required mobile configuration.

DOMAIN OWNERSHIP

LinksetGo issues exact records for one hostname.

A custom hostname such as links.example.com receives a unique TXT ownership challenge and a CNAME target configured by the LinksetGo Cloud ingress.

_linksetgo-verification.links.example.com TXT linksetgo-domain-verification=…
links.example.com CNAME ingress.linksetgo.com

After publishing both records, use Check DNS & TLS in the Domains console. LinksetGo sends only the normalized hostname to its trusted operator adapter, validates returned evidence against the server-issued challenge, and never fetches a customer-supplied URL.

ACTIVATION

Every trust boundary has an explicit state.

01

Pending DNSLinksetGo has issued exact CNAME and TXT records.

02

VerifyingTrusted infrastructure is evaluating DNS evidence.

03

Certificate readyThe managed ingress confirms HTTPS certificate readiness.

04

Association incompleteAASA and Asset Links are published for mobile validation.

05

ActiveNew links may use the custom hostname.

APP RELEASE REQUIRED

A DNS change cannot update an installed app.

The iOS team adds applinks:links.example.com to Associated Domains. The Android team adds the same exact host to an auto-verified intent filter. Test release-signed builds before LinksetGo activates the domain.

Existing app versions that do not trust the custom hostname will use the safe web fallback. The managed workspace URL remains available throughout onboarding.

The final console action is owner-only and requires typing the exact hostname plus an explicit released-build acknowledgement.

FAIL CLOSED

Unknown hosts never inherit another workspace.

LinksetGo exact-matches an active domain to one workspace. Host-scoped AASA and Asset Links responses contain only that workspace’s apps. Forwarded hosts are ignored unless the deployment explicitly trusts a sanitizing ingress.

Compare domain plans