Help / Website and booking

Custom domain is stuck on pending

DNS usually takes minutes, but records in the wrong place or a missing TXT token are the two reasons it stalls for hours.

Sign in to open this screen

1. Step 1

   Check both records are saved at your registrar

   You need two records: a CNAME for your hostname (e.g. www.yourfirm.com) pointing at the Inspecta Home 360 target, and a TXT record on _inspecta.yourfirm.com with the token shown in Website → Your domain. If either is missing, status will stay pending.

2. Step 2

   CNAME must be for www, not the root

   Most registrars do not allow a CNAME on the bare root (yourfirm.com without www). Use www.yourfirm.com as your hostname in Inspecta Home, and set the CNAME there. If you need the root, set up an HTTP redirect from yourfirm.com → www.yourfirm.com at your registrar — Inspecta Home does not handle root-domain forwarding.

3. Step 3

   DNS propagation takes up to 48 hours

   Most providers update within 30 minutes, but some TTLs are set to 24–48 hours. You can check propagation at whatsmydns.net — search for your hostname as type CNAME. Once it shows the Inspecta Home target globally, status in the studio will flip to active within a few minutes.

4. Step 4

   HTTPS padlock is automatic

   Inspecta Home 360 provisions an SSL certificate once the CNAME resolves. You do not need to upload a certificate. If the padlock is missing after the domain goes active, wait 15 minutes and reload — certificate issuance runs right after the domain check passes.

5. Step 5

   Your /o/your-firm page stays live

   Until the custom domain is verified, the public site stays at /o/your-firm. Do not remove that page — it is the fallback during transition.