Try it
Read-only: Cnamio reads public DNS and nothing on the domain is changed. No sign-up; the name you type is not stored. A few tries per minute per visitor.
What each part means
- DNS provider and nameservers. Where the domain's DNS is hosted, which can differ from where it was bought. It decides how the connection goes.
- How it would connect. API token: on Cloudflare, Hostinger and Amazon Route 53 your customer pastes a token and Cnamio creates the records. Provider consent page (Domain Connect): offered for apps whose template the provider has synced, when nothing is in the way. Guided: everywhere, the exact records to copy.
- Records and conflicts. The sample app asks for a CNAME at the name plus an ownership TXT. Cnamio reads what the zone's own nameservers publish at those names; anything in the way is listed and never overwritten.
- Webhook. The
domain.addedbody your backend receives once every record is live on every authoritative nameserver, built by the same code as the real deliveries.
Put it in your app
One script on your page, a session token from your server, and the records your service needs:
<script src="https://connect.cnamio.com/sdk/v1.js"></script>
cnamio.connectDomain({ applicationId: 'app_…', token: SESSION_TOKEN,
dnsRecords: [{ type: 'CNAME', host: '{SUBDOMAIN}', value: 'customers.yourapp.com' }] });
The quickstart walks through the server side and the webhook. The test application you get at sign-up connects any domain against a simulated provider.
What the demo does not do
- It never writes DNS, asks for a provider token or password, or starts a connection.
- It does not check whether the sample target is reachable:
customers.sample-app.exampleis a reserved name that never resolves. - The webhook shown is not signed or sent; real ones carry
Cnamio-TimestampandCnamio-Signature(HMAC-SHA256).