# Spam filtering

> Spam filtering is on for every form, with no CAPTCHA. Here is what each rule does and how to tune it.

Last updated 2026-11-17. Web version: https://wrenform.com/docs/spam

```html
<input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off">
```

Keep this field in every form. People never see it; bots fill it in.

## How a submission is judged

The rules run in this order. Every rule that fires is recorded, and you can see the reasons on the submission in your dashboard.

1. **Honeypot.** Any value in `_honey` (or `_gotcha`) marks the submission as spam.
2. **Timing.** If the form tells us when it was rendered, a submission sent less than 3 seconds later is spam. See [the timing field](#the-timing-field).
3. **Turnstile.** Only if you added your own Cloudflare Turnstile keys. See [Turnstile](#turnstile).
4. **Content score.** Points for signals common in spam. At or over your threshold, the submission is spam.

| Signal | Points |
|---|---|
| Each link beyond the first 2, across all fields | +2 |
| A link on a known URL shortener | +3 |
| Each match on our keyword list (crypto, SEO services, loans, adult, casino, "guest post"), up to 3 | +3 |
| HTML tags or BBCode links in a value | +2 |
| Gibberish: a long value with no spaces and few vowels, or a body that is mostly symbols | +2 |
| The same data from the same visitor within 24 hours | +3 |

Rate limits apply before any of this: 10 submissions a minute and 50 an hour per visitor and form, 120 an hour per visitor across all forms, and 60 a minute per form. Requests over a limit get `429 rate_limited` and aren't stored.

## Sensitivity

Set it in the form's settings under **Spam**:

| Setting | Spam at | Use it when |
|---|---|---|
| Low | 8 points | Real messages land in Spam, for example forms that ask for links |
| Normal (default) | 5 points | Most forms |
| High | 3 points | You get a lot of spam; check the Spam tab now and then |

## What happens to spam

- It's stored in the form's **Spam** tab. No email, no webhook, and it doesn't count toward your monthly quota.
- The sender sees the usual success response, so bots learn nothing.
- It's deleted after 30 days (or sooner, if the form keeps data for less). An account keeps at most 10,000 spam submissions; beyond that, the oldest go first.
- You can move a submission between Inbox and Spam. Moving one to Inbox counts it toward the quota, but doesn't send the email or webhook it missed.

Missing a submission? Check the form's **Spam** tab. For `origin_not_allowed`, add your domain under **Allowed origins** in its settings.

## The timing field

Two hidden fields catch bots that post the instant a page loads:

- `_te`: milliseconds since the form rendered, measured in the visitor's browser. Under 3,000 is spam. It wins over `_t`, so a visitor with a wrong clock isn't misjudged.
- `_t`: the render time as a Unix time in milliseconds. Use it when your server renders the page per request. We ignore values more than 60 seconds in the future or older than 24 hours.

Our helper script fills both, adds the honeypot if your form has none, and can submit without leaving the page:

```html
<script src="https://wrenform.com/js/v1/form.js" defer></script>
```

It's under 2 KB, has no dependencies, and only touches Wrenform forms, including ones added later. Forms work without it.

To submit in place, add `data-ajax` to the form. The result shows in a `role="status"` paragraph inside the form, `data-success="…"` sets your own thanks message, and the form fires a `wrenform:success` or `wrenform:error` event.

Strict Content-Security-Policy? Allow `script-src https://wrenform.com`, or serve this smaller script from your own domain instead; see the [HTML guide](/docs/frameworks/html#strict-content-security-policy-sites).

```html
<script>
  for (const form of document.querySelectorAll('form[action^="https://wrenform.com/f/"]')) {
    const field = Object.assign(document.createElement("input"), { type: "hidden", name: "_te" });
    form.append(field);
    form.addEventListener("submit", () => {
      field.value = String(Math.round(performance.now()));
    });
  }
</script>
```

## Turnstile

Cloudflare Turnstile adds a bot check, usually invisible. It's optional, and you use your own free keys.

1. Create a Turnstile widget in your Cloudflare dashboard for your site's domain. Copy the site key and the secret key.
2. In the form's settings, under **Security**, paste both keys. The secret key is stored encrypted.
3. Add the widget to your form:

```html
<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>

<form action="https://wrenform.com/f/YOUR_FORM_ID" method="POST">
  <!-- your fields -->
  <div class="cf-turnstile" data-sitekey="YOUR_SITE_KEY"></div>
  <button type="submit">Send</button>
</form>
```

The widget adds a `cf-turnstile-response` field. Once the keys are saved, a submission without a valid token is marked as spam. If Cloudflare can't be reached, we skip this check rather than lose the message.

## Test it

Send the form once normally: it should arrive in Inbox. Then fill the hidden `_honey` field with your browser's developer tools and send again: it should land in Spam, with the reason `honeypot`.

## Common problems

- **Real messages in Spam.** Open one and read its reasons. Lower the sensitivity, or move it to Inbox.
- **Everything is spam after adding Turnstile.** The widget isn't inside the `<form>`, or the site key and secret key belong to different widgets.
- **Autofill fills the honeypot.** Keep `autocomplete="off"` and a name that doesn't look like a real field.

## Next steps

- [Fields](/docs/fields): every reserved field.
- [Errors](/docs/errors): what `rate_limited` and the other codes mean.
- [Notifications](/docs/notifications): keep our emails out of your own spam folder.
