Help Center menu

Custom domains

In this article

Serve your form from your own domain (e.g., forms.yourbrand.com) instead of nodumforms.com. Looks more polished and keeps respondents in your brand experience.

Setting it up

  1. Open the form → Settings → Custom domain.
  2. Enter the domain you want to use (e.g., forms.yourbrand.com).
  3. We give you a CNAME target — usually forms.nodumforms.com or similar.
  4. Go to your DNS provider (Cloudflare, Route 53, Namecheap, GoDaddy, etc.) and add a CNAME record pointing your subdomain to that target.
  5. Save the settings in NodumForms. Verification typically takes a few minutes.

What happens

Once verified, your form is reachable at both URLs:

  • https://forms.yourbrand.com/[slug] — your branded URL
  • https://nodumforms.com/f/[shortId]/[slug] — the original URL keeps working

HTTPS

We provision a free TLS certificate via Let's Encrypt automatically once the CNAME resolves. No certificate management on your end.

Limits

  • One custom domain per form. The same domain can't be used for two forms.
  • The domain you use can't be your apex domain (e.g., yourbrand.com) — only subdomains. Apex / root domain support is on the roadmap.

Troubleshooting

If verification fails:

  • Double-check the CNAME points to the exact target we gave you (no typos, no trailing dots).
  • Wait 5–10 minutes — DNS propagation isn't instant.
  • Make sure no conflicting A / AAAA / CAA record exists for the same subdomain.
  • Contact support@nodumforms.com if it still fails after 30 minutes.

Give feedback

Was this resource helpful?

|

Up next

Social preview (Open Graph)

When someone shares your form link on Slack, Twitter, LinkedIn, iMessage, or any platform that fetches link previews, they see a card pulled from your form's metadata.

Read more
Previous: Prefilling answers via URL

FAQs

Yes — set a custom domain for any form (e.g., forms.yourbrand.com) from the form settings. You'll need to add a CNAME record at your DNS provider pointing to nodumforms.com.

A native embed snippet isn't built yet. As a workaround you can wrap the public form URL in your own iframe, but the form's page-level chrome (header / footer) will be visible. A dedicated embed mode is on the roadmap.

Yes — append query parameters of the form `?prefill_BLOCKID=value` to the form URL. The matching block opens with the value already filled in. Useful for tracking source links and personalising entry points.