FAQ

Which DNS providers auto-configure records?

19 providers have a built-in adapter (Cloudflare, Route 53, GoDaddy, Namecheap, and more) plus Domain Connect as a redirect-based, tokenless option. See DNS providers for the full list and Provider setup for per-provider credential steps and eligibility gates.

Does it support apex domains as well as subdomains?

Yes — a connection's kind is apex or subdomain (see the Connection schema in the API reference). Apex support depends on the provider's capabilities (ALIAS/ANAME/CNAME flattening); POST /v1/domains:check returns apex_flattening and www_redirect_recommended so you can steer the customer to the right setup.

Does it support wildcard domains?

POST /v1/domains:check returns a capabilities.wildcard flag per detected provider, reflecting whether that provider's DNS supports wildcard records. Whether wildcard is offered in your product depends on how you use that capability flag in your own onboarding flow.

How long does DNS propagation usually take?

It depends on the TTL of any records being replaced and the customer's resolver/registrar — from minutes (delegated auto-write with fresh records) to longer if a previous record had a long TTL. POST /v1/connections/{id}/records:check reports live propagation state per record; see Troubleshooting.

What happens if I revoke or delete an API key?

Revocation is immediate — a revoked key stops authenticating on its very next request. Keys are never returned by list endpoints after creation; only metadata (last4, scopes, timestamps) is visible.

Can a connection lose its "live" status?

Yes — if a live domain's records stop resolving to their intended values, it transitions to drifted and fires domain.drift. See Connections.

Is there a sandbox / test mode?

Yes — API keys are prefixed sk_test_/sk_live_, and applications have a test/live environment. make dev seeds a demo application and sk_test_demo key for local development (see the Quickstart).