Your team wants a hosted docs site, a support portal, or a token-claim page.
So, the vendor sends over a DNS record, and someone asks you to paste it into the control panel.
Before you do, check what you’re connecting. Users will see your project’s domain, even when another company runs the service behind it. That familiar address carries trust, especially when a page asks them to connect a wallet.
Three questions can help you protect that trust without holding up the launch.
1. What does this change authorize?
A verification TXT record, a CNAME alias, and a nameserver delegation do different jobs. A TXT token may prove control to a particular service, while a CNAME points one hostname toward another. Then a nameserver delegation gives a provider authority to answer DNS queries for a domain or subdomain.
Ask the vendor which hostname it needs, why it needs that record, and what the verification enables. If you’re connecting docs.example.com, ask why any request extends beyond that hostname. Your team may be able to add the record without giving the vendor DNS account access.
2. Who controls what users will see?
Once the connection works, someone can publish content behind your address. Find out which vendor account controls it and who can access that account.
Use an account your organization controls, enable MFA, and assign a named owner. Check whether an agency or contractor retains access. For a wallet-facing page, include who can change the interface or scripts that prompt users to sign transactions.
Your smart contracts can remain unchanged while the page leading users to them changes. That’s why the vendor account belongs in your security review.
3. How do we disconnect safely?
Record the original DNS settings and agree on a rollback before launch. Then document what happens when the service is retired.
Deleting a hosted service while leaving its DNS alias behind can create a dangling record. On some platforms, another party may be able to claim the abandoned destination and serve content under your hostname.
Coordinate removal or repointing of DNS with the vendor, allow for cached answers, and verify the change before releasing the old resource. Review verification records and revoke access that’s no longer needed, and make sure you don’t leave cleanup to whoever notices first.
Get Your Connection Checked
DomainSure’s services include multi-user role permissions and DNS change notifications, with monitoring coverage varying by plan. Those controls help you manage changes alongside your vendor review.
Contact DomainSure for a free Domain Threat Assessment. Bring the vendor’s setup instructions and ask us to review what the connection will change before you put your name on it.
Apply for a Domainsure Invite
Get a Free Domain Health Check
Due to high demand: allow up to 24 hours for report delivery.
