close
Skip to Content

Your customers should never touch DNS.

For platforms whose customers bring their own domain. We find the DNS provider, then write the records or show them.

  • Cloudflare
  • Squarespace
  • Wix
  • Dynadot
How each provider connects
The CustomDomain™ widget’s real screens, on an example domain.

Built for how your customers show up.

All use cases

Your customers fail at the finish line.

A CNAME and a registrar login is where setup dies.

Why DNS onboarding fails

  1. You ship "Connect your domain"Connect your domain
  2. Your customer opens their registrarType ? Host ? Value ?
  3. The setup dies here

Four steps. One API call starts them.

The same four steps run for every domain your customers connect.

How it works

  1. Find the DNS providershop.acme.comDNS at Cloudflaresign in
  2. Write the records, or show themCNAME shop edge.customdomain.ai
  3. Check until livependingpropagatinglive
  4. Check again every hour"every": "hour"

Audit a domain you own.

See the provider, the button your customer would press, and what would change.

Read-only. Your browser asks public DNS and our provider check (answers cached for a day), and opens your site once for the padlock.

Everything a custom domain feature needs.

  • HTTPS, the padlock Growth and up

    Our edge issues the certificate on the first HTTPS request.

  • Drift checks

    Every live domain is checked once an hour. The console shows each domain's drift state.

  • API, widget and MCP

    One REST API, one widget, and an MCP server with 23 tools.

    Read the quickstart
  • Provider detection

    Named from the nameservers, before your customer types a record.

  • Records, written or shown

    Written after a provider sign-in, or shown with that provider's steps.

  • States your app can show

    Every move between them fires a webhook.

Where your customers' DNS is hosted.

If the owner can edit its DNS records, the domain can be connected.

GoDaddy, Namecheap, Hostinger, Spaceship, Alibaba Cloud DNS, NameSilo, OVHcloud, Bluehost, Netlify, Gandi, Hetzner, Amazon Route 53, Google Cloud DNS, Azure DNS, DNSimple and the rest are in the provider directory.

The registrars in our provider census hold 97% of all gTLD domains.1

1 ICANN monthly registry reports, June 2026: 256,876,848 of 263,989,797 domains under management in 1,114 gTLDs are held by a registrar our census names, counted on October 31, 2026. Country-code domains are not included.

Trademark notices

Names and logos belong to their owners. We write the records where the provider allows it and show the exact ones where it does not. A name here does not mean the provider endorses us.

Cloudflare and the Cloudflare logo are trademarks and/or registered trademarks of Cloudflare, Inc. in the United States and other jurisdictions. Vercel, the Vercel design, Next.js and related marks, designs and logos are trademarks or registered trademarks of Vercel, Inc. or its affiliates in the US and other countries. DigitalOcean and all related logos are trademarks of DigitalOcean, LLC or its affiliates. dnsimple is a registered trademark of DNSimple Corporation.

Common questions.

Want to see it on your own product?

Book a call Read the docs
What does my customer see?

A window inside your product. They type their domain, we name their DNS provider (the company that holds the domain's settings), and they sign in there and approve, or get the exact records with its steps. See it in the live demo

Which DNS providers work?

Any provider that lets the owner edit DNS records. Where the provider allows it, the records are written after your customer signs in. Elsewhere we show the exact records and check each one. Provider directory

Do you handle HTTPS?

HTTPS is the padlock in the browser: the site loads securely on your customer's own domain. On Growth and up, our edge issues the certificate on the first HTTPS request and renews it about 30 days before it expires.

How long does a domain take to go live?

Records written for your customer usually check out within seconds. Records added by hand are checked every 5 seconds for the first 5 minutes, then less often, until they appear.

Do you see my customer's registrar password?

No. We never see or keep a registrar password. A provider sign-in is used for the write and dropped, or kept encrypted so missing records can be put back, and it can be revoked at any time.

Root domain or www?

Both work. A subdomain like shop.acme.com needs one CNAME record, a line that points the name at your app. A root like acme.com takes an ALIAS or A records, as its provider allows. On Growth and up, our edge redirects one to the other.