Custom Domain
Register and verify sending domains. Forms attach to verified domains individually.
Custom Domain in Workspace is where you register the domains your forms can send from. You set up DNS once per domain — then any form in the workspace can attach to it from its own Custom domain tab.
Two pages, one workflow
Register here (workspace-level DNS verification). Attach there (per-form). The separation lets one verified domain power many forms with different sender names.
Adding a domain
Click Add domain
example.com. The default sender becomes forms@example.com, and the default mailed-by domain becomesmail.example.com.Customize only if you need to
forms and mail.Copy the DNS records
Let Static Forms check the setup
Attach the domain to a form
Already verified a domain?
Open its domain card and choose Set up mailed-by. Your existing From address keeps working while the two new MX and SPF records propagate; there is no need to remove or re-verify the domain from scratch.
View states
- Upsell — visible to Free/Trial tiers. Shows what custom domains do and links to pricing.
- Read-only — visible to team members who aren't the workspace owner. Lists domains and statuses, no edit actions.
- Manage — visible to the workspace owner on Pro and above. Add, verify, and remove domains.
Verifying DNS records
Each domain card lists every required record with a copy button and a status pill (Pending / Verified / Failed). DKIM authenticates the visible From address. The mailed-by MX and SPF records authenticate the envelope sender and keep it on your domain. If verification fails:
- Confirm the host/name field is correct (some providers want the leaf, others want the full FQDN).
- Wait — DNS can take time to propagate.
- Click Recheck to force a fresh poll.
Keep SPF as one record
Never add a second SPF record at the same hostname. When Static Forms finds one existing SPF policy, replace it with the combined value shown in the domain card. If it finds multiple SPF records or existing mail routing, setup pauses and suggests a different mailed-by prefix instead of risking your current email service.
Recommended DMARC monitoring
Static Forms checks your From domain and its parent domains for an existing DMARC policy. Existing policies are left unchanged. If none is found, the domain card recommends the optional monitoring policy v=DMARC1; p=none. DMARC does not block Static Forms verification. Add a reporting address only when you have a mailbox or DMARC service that will process the reports.
Removing a domain
Removing a domain immediately stops any form attached to it from using it — those forms fall back to the default no-reply@staticforms.dev sender until you attach a different domain. Forms aren't broken, just defaulted.