Domain verification
Diagnose and fix pending or failed custom domain verification in Nomow.
Custom domains let your forms, pages, and booking pages appear on your own URL instead of app.nomow.ai. Verification confirms to Nomow that you control the domain. If verification is stuck, this article walks through the fix.
What each status means
| Status | Meaning |
|---|---|
| Pending | DNS record added but Nomow has not yet received a valid response |
| Verified | Domain is confirmed and routing is active |
| Failed | Nomow received a response but the record content did not match |
Nomow checks verification on demand (when you click Verify now) rather than on a polling loop. Pending does not mean something is broken — it usually just means DNS has not fully propagated yet.
Fixing a pending or failed domain
Open Domains from the sidebar. Click the domain card showing Pending or Failed. The card shows the CNAME and TXT records Nomow requires. Use the copy button next to each record value — do not retype them by hand.
Log into your DNS provider (Cloudflare, Route 53, GoDaddy, Namecheap, etc.) and add the records:
- CNAME — the hostname and value shown in Nomow (typically
formsorpagesas the subdomain, pointing toproxy.nomow.ai). - TXT — the verification token Nomow generated for your domain. Paste the exact value from the copy button.
Some providers auto-append your root domain to record names — check that the final hostname does not become forms.acme.com.acme.com.
DNS changes can take anywhere from 30 seconds to 48 hours, depending on your provider and the TTL of the previous record. Most modern providers propagate within 5–15 minutes for new records.
Return to Nomow, open the domain card, and click Verify now. Nomow performs a live DNS lookup. If the records are in place, the status moves to Verified. If it stays Pending or switches to Failed, continue to the troubleshooting questions below.
Common reasons verification fails
The CNAME record exists but verification still fails
Check that the CNAME value (the target) is exactly proxy.nomow.ai with no trailing characters. Some DNS providers add a trailing dot (valid) — confirm the displayed resolved value matches what Nomow expects. Also verify the subdomain name matches what Nomow listed (case-insensitive, but no extra hyphens or words).
The TXT record was added but not picked up
TXT records propagate independently of CNAME records. Use a public DNS checker (such as dnschecker.org) to look up the TXT record for your domain and confirm the Nomow token appears in the results before clicking Verify now.
I see "record not found" in the DNS checker
The record has not propagated from your provider yet, or it was entered under the wrong hostname. Double-check the hostname field in your DNS provider — it should be the subdomain only (e.g., forms), not the full domain (e.g., forms.acme.com).
The domain worked before and now shows Failed
An accidental deletion of the CNAME or TXT record is the most common cause. Re-add the records and click Verify now. If your DNS provider rotated your zone (e.g., during a migration), all custom records need to be re-entered.
My DNS provider does not support CNAME on the root domain
Root-domain CNAMEs (CNAME flattening or ALIAS records) are provider-specific. If you need acme.com (not a subdomain) to point to Nomow, use a DNS provider that supports CNAME flattening (Cloudflare, Route 53, DNSimple). Otherwise use a subdomain like forms.acme.com.
After verification
Once verified, Nomow begins routing your domain to the correct surface. It may take 1–2 minutes for the HTTPS certificate to be provisioned. If the page returns a certificate error immediately after verification, wait two minutes and reload.
Next steps
Connect a verified domain to a landing page in Publishing pages, or to a form in Publishing & embedding. General troubleshooting starts at Common issues.
Was this article helpful?