Honeypot Field Element

The Honeypot Field Element is a simple trap for spam bots. It adds an invisible field to a Tirenoa Form (Tirenoa > Forms) that real visitors never see or fill in. Automated scripts that fill in every field they find give themselves away, and their submission is stopped.

It costs visitors nothing: there is no puzzle to solve, no extra click and no outside service involved. That makes it a good first line of defense for every contact form, alone or together with a reCAPTCHA or Turnstile check.

In this article: How To Use · Element Options · Tips · Related Elements

How To Use The Honeypot Field Element

Add the Honeypot Field Element anywhere in your form. The Field Name is filled in with hypot_field by default; you can change it to something less obvious, using only lowercase letters, numbers, dashes and underscores.

There is nothing else to set up. The field has no label, no design options and no required setting. CSS Class and CSS ID are added to its wrapper if you need them for custom styling or scripts.

When the form is sent, the field is checked first. If it contains any value, the form is not sent and the visitor sees the form’s error message instead. The honeypot is left out of the notification email. The field is hidden from keyboard navigation and screen readers, so it does not get in the way of visitors who use assistive technology.

Element Options

The tables below list every option of the element, grouped by the tabs you see when you edit it in the Builder. Many options depend on others, so the edit screen only shows the options that apply to your current choices.

General

Heading Description
Field Name Enter the field name. Please use only lowercase alphanumeric characters, dashes, and underscores.
CSS Class Add a class for the form field.
CSS ID Add an ID for the form field.

Tips

  • Use one Honeypot Field per form. More than one adds nothing.
  • The check runs in the visitor’s browser and only for forms with the AJAX Submission Type. Add a reCAPTCHA or Turnstile field as well when a form receives a lot of spam.
  • Give each form’s honeypot a Field Name that does not clash with a real field of the same form.
  • Add a Notice Element to the form so that a blocked submission shows a clear error message.