Knowledge base
Put a form on a static website without a form service: answers are e-mailed to a mailbox on your own domain, and we keep no copy.
A static website (plain HTML) has no server code of its own, so a form on it has nowhere to send its answers. We receive them for you: the form posts to us, we check it is a person and not a bot, and we e-mail the answers to a mailbox on your website's own domain. The visitor's e-mail address is set as the reply address, so you just press Reply.
You need a mailbox on the website's own domain (for example hello@yourdomain.com). Create one on the website's Email page if you have none. Forms can only send to an active mailbox on that domain, in your own account, so nobody can use your form to send mail anywhere else.
The card then shows the Form address (action), the Bot check site key and a Starter form. Press the copy button beside Starter form, paste it into a page of your website, and change the questions to your own. Set _to to the part of your mailbox before the @.
name is the question as you want it to read in the e-mail._email is the visitor's address (used to reply), _name their name._next is the page they see after sending (for example /thanks/), _back the page theyreturn to if something was wrong. Both must be pages on your own website.
cf-turnstile box is the bot check. Keep it, with the site key from the card._website field empty and hidden: bots fill it in, and we drop those.The visitor also gets a short confirmation e-mail that does not repeat their answers.
One visitor can send 6 forms an hour. The answers are not stored by us: the e-mail in your mailbox is the only copy. If your form asks about health or other sensitive matters, add a consent checkbox and a short privacy note to the page.
Turn the switch off. From the next visitor on, the form is refused and nothing is sent. The site key stays the same, so switching back on later needs no change to your page.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →