FAQ
The questions integrators ask most about DoDomain — providers, apex domains, SSL, SDKs, webhooks, monitoring, limits, testing and AI agents — each answered briefly with a link to the full page.
Short answers to the questions that come up most. Each one links to the page with the full detail.
What does DoDomain do?
DoDomain gives SaaS products a hosted custom-domain setup flow. Your server creates a connect session with the domain and the DNS records your product needs. DoDomain applies or guides those records, verifies them against the domain's authoritative nameservers, and notifies your server with a signed webhook. Start with Getting started.
Which DNS providers support one-click setup?
Cloudflare supports one-click apply through OAuth. Providers that have enabled DoDomain's Domain Connect templates get a signed one-click apply too. Every other provider gets guided setup with the exact records, provider-specific instructions and live verification, so every domain has a working path. See Connect flow.
Does DoDomain proxy traffic or issue SSL certificates?
No. DoDomain writes and verifies DNS, and traffic goes straight to your infrastructure. TLS terminates at your own host, such as Vercel, Cloudflare for SaaS, Render, Fly.io, Caddy or nginx. See SSL for which records to mint per host.
Can my customers connect an apex domain like acme.com?
Yes, with A, AAAA, TXT or MX records at @. A CNAME cannot sit at a zone apex, so ask for a subdomain when your product is reached by hostname, or serve the apex from A/AAAA records. See Apex domains.
Is there an SDK, or do I integrate over raw HTTP?
Both. @dodomain/node and dodomain-sdk are the server SDKs, and @dodomain/connect and @dodomain/react embed the flow in your UI. The plain REST API and the hosted connect link stay fully supported.
How do I know when a customer's domain is connected?
When the records verify against authoritative DNS, DoDomain sends a signed connection.verified webhook to your endpoint. Verify the x-dodomain-signature header before trusting it, then activate the domain in your product. See Webhooks.
How long does a connect session last?
24 hours. After that the session answers 410 and you mint a new one. Sessions are short-lived capabilities, so hand the connectUrl to the user when they are ready to set up DNS. See Connect flow.
What happens if a connected domain's DNS changes later?
DoDomain keeps re-checking every connection on every plan. Drift is confirmed before you are alerted: the connection is marked broken and connection.failed is sent, and connection.verified fires again when the records return. See Webhooks.
Is there a free plan, and what happens at the monthly limit?
Yes, the Free plan needs no card and includes the full product. Each plan has a monthly allowance of verified connections. At the cap, creating a new session returns 402 quota_exceeded, existing connections keep working and keep being monitored, and nothing is billed as overage. See Pricing and dodomain.io/pricing.
What counts as a verified connection?
A connection counts once, on its first successful verification. Re-verifying, a domain breaking and recovering, or reconnecting the same session never count again. See Pricing.
How do I test without a real customer domain?
Drive the hosted page in your tests rather than the widget, and use a test zone you control for the part that needs real DNS. See Testing your integration.
Can AI assistants and coding agents use DoDomain?
Yes. DoDomain runs a remote MCP server at https://app.dodomain.io/api/mcp with OAuth sign-in and seven tools. To set up a coding agent in one step, paste this sentence into Claude Code, Codex, Cursor, OpenCode or GitHub Copilot:
Fetch and execute the appropriate instructions to set me up for DoDomain from https://dodomain.io/agent-setup/prompt.mdPer-agent guides live at dodomain.io/agent-setup, and the MCP details at Connecting AI assistants.
Still stuck?
Email [email protected] or check status.dodomain.io.