Skip to content

Connecting your domain

The shield attaches at a domain you own. Add the domain on the dashboard’s Domains page, and it will detect your setup and recommend the easiest lane. All four end in the same place: your domain live behind the shield, with HTTPS handled for you.

If your registrar supports Domain Connect, the dashboard sends you to your registrar to approve once — the DNS records write themselves and you come straight back. Nothing to copy. (Registrar support varies; the dashboard offers this lane automatically when your domain qualifies.)

If your DNS is on Cloudflare: create an API token scoped to editing DNS on that one zone, paste it into the dashboard, and the records are written for you. The token is used once and never stored — revoke it afterwards for good hygiene.

Works everywhere: the dashboard shows you two records to add —

  1. a record pointing your domain (or subdomain) at the Superspice edge, and
  2. a _superspice-challenge TXT record that proves you control the domain.

Add them wherever you manage DNS, then hit Verify. DNS propagation can take a little while; verify is safe to retry until it goes green.

If you’d rather not touch DNS at all, run the shield inside your own hosting:

These run inside your own hosting — for these lanes, your traffic doesn’t route through Superspice at all.

Every lane is built so that if Superspice is ever unreachable, your site serves normally. The shield structurally cannot take your site down — the worst failure mode is a moment of the old world, where agents read for free.

The Domains page has a real remove flow, and the manual lane’s exit is exactly what you’d hope: delete the two DNS records and your domain is as it was. No lock-in is the point.