Honeypot for Contact Form 7


This simple addon module to the wonderful Contact Form 7 (CF7) plugin adds basic honeypot anti-spam functionality to thwart spambots without the need for an ugly captcha.

The principle of a honeypot is simple — bots are stupid. While some spam is hand-delivered, the vast majority is submitted by bots scripted in a specific (wide-scope) way to submit spam to the largest number of form types. In this way they somewhat blindly fill in fields, regardless of whether the field should be filled in or not. This is how a honeypot catches the bot — it introduces an additional field in the form that if filled out will trigger the honeypot and flag the submission as spam.

Additionally, as of version 2.1, the plugin also features an optional submission time check. This checks how long it takes to submit the form and if under a user-defined threshold, it rejects the submission as spam. This works under the idea (backed up by testing) that spam bots submit forms super fast (usually 1-2 seconds), whereas people take longer.


You will need Contact Form 7 version 3.0+ at a minimum. It is recommended to use version 5.3+ of CF7, for better spam logging. For the best results, we suggest always using the latest versions of WordPress and CF7.

We highly recommend Flamingo with CF7 and this plugin. Using Flamingo allows you to track spam submissions (via inbound messages / spam tab in Flamingo), showing you what got caught in the honeypot and why. Be sure to check your Honeypot settings to turn storing the honeypot on for this.


Support can be found here. Follow us on Twitter and on Facebook for updates and news.

Visit the Honeypot for Contact Form 7 plugin page for additional information or to buy us a coffee to say thanks.


This plugin does not track users, store any user data, send user data to external servers, nor does it use cookies. This is an addon plugin, and requires Contact Form 7. Please review Contact Form 7’s privacy policies for more information.


If you’d like to translate this plugin, please visit the plugin’s translate.wordpress.org page. As of v1.10, all translation is handled there. Version 2.0 brings a bunch of new strings in need of translation, so a huge thank you to the polyglots that contribute!


The latest version of this plugin is designed to work with the latest version of Contact Form 7 and WordPress. If you are using older versions of either, you’re best to find the version of this plugin released around the same time as the version you’re using. You can access older versions of this plugin by clicking Advanced View on the right of the plugin’s page and scrolling to the bottom of the plugin’s page. Use at your own risk. We strongly recommend upgrading to the latest versions whenever possible.


  • Global Honeypot Settings
  • Honeypot CF7 Form Tag Settings


  1. Installiere es mit der WordPress-Funktion „Plugin hinzufügen“ – suche einfach nach „Honeypot for Contact Form 7“.
  2. Stelle sicher, dass Contact Form 7 installiert und aktiviert ist. Dann aktiviere dieses Plugin.
  3. Bearbeite ein Formular in Contact Form 7.
  4. Wähle „Honeypot“ aus dem CF7 Tag Generator. Empfehlung: ändere die ID des Honeypot-Elements.
  5. Füge das generierte Tag irgendwo in deinem Formular ein. Das zusätzliche Feld wird mittels inline CSS vor deinen Besuchern versteckt.

Die Honeypot HTML Ausgabe anpassen [FORTGESCHRITTEN]

Während die Grundeinstellungen für die meisten Leute genügen sollten, haben wir mehrere Filter eingebaut, womit Du die Honeypot-Felder weiter anpassen kannst.
Die drei verfügbaren Filter sind:

  • wpcf7_honeypot_accessibility_message – Adjusts the default text for the (hidden) accessibility message (can now be done on the settings page).
  • wpcf7_honeypot_container_css – Passt das CSS an, das auf den honeypot Container angewendet wird um diesen versteckt zu halten.
  • wpcf7_honeypot_html_output – Passt die vollständige HTML Ausgabe des Honeypot Elements an.

Für passende Beispiele hierzu schaue dir bitte diesen Rezept Gist an.


Wird dieses Plugin allen Spam abhalten, den ich über Kontaktformulare bekomme?

Wahrscheinlich nicht. Aber es soll ihn so weit reduzieren, dass du auf zusätzliche Anti-Spam-Mittel verzichten kannst (CAPTCHA, Mathematikfragen, usw.).

Sind Honeypots besser als CAPTCHAs?

This largely depends on the quality of the CAPTCHA. Unfortunately the more difficult a CAPTCHA is to break, the more unfriendly it is to the end user. This honeypot module was created because I don’t like CAPTCHAs cluttering up my forms. My recommendation is to try this module first, and if you find that it doesn’t stop enough spam, then employ more challenging anti-spam techniques.

Kann ich den HTML Code beeinflussen, den das Plugin erzeugt?

Jawohl! Schau Dir den Abschnitt Installation für mehr Details an und besuche diesen Gist für Beispiele.

Mein Formular wird mit einem W3C-Validierungswerkzeug nicht erfolgreich validiert

As of version 2.0, this shouldn’t be the case any longer. However, if it is for some reason, there is a simple work around. See here for details.

Does this plugin work with Flamingo?

You bet! If the honeypot trap is triggered, an email isn’t sent, but the form submission is added to the spam section of Flamingo so you can review what tripped things up.

Why do you have affiliate ads on your settings page?

I realize not everyone loves ads, but daddy’s gotta pay the bills. I’m extremely grateful to the numerous users that have donated to the plugin’s development over the years, and while that’s awesome, I don’t think donations will ever come remotely close to covering the time and effort it takes to maintain and support a plugin that now has nearly 1.5 million downloads and more than 300,000 active installs.


25. Oktober 2021
To test this, I set the timer to 60s and completed the form within this time, but it was still sent. This needs to be fixed, as it would be unfeasible for any human to complete most forms within 30s, and that is likely to stop most bots. A second test was to use the page Inspect console to unhide the field so I could fill it out before submitting it, and while this stop the message from being sent, the spam that is still getting through is not filling out this field.
20. September 2021
In order to test the plugin, I set "enable time check" to 60 seconds. I reloaded the page, I filled the form quickly (under 60 seconds) and I could send the form and I got the message. I searched for the hidden field in the source code. I was not able to find it. To be sure of that, I compared the source code of the page without the plugin enabled and with the plugin enabled using Total Commander. Files were identical. So this plugin does not work.
31. Juli 2021
Great gob! This is a really perfect alternative for Google reCaptcha with excellent PageSpeed results. I use two fields together with the time check. No spam in result and + 20...25 points in PageSpeed performance results (compared with reCaptcha).
19. Juni 2021
WordPress is very weak and sadly support spam in an extreme way.... Sadly this plugin doesnt impact the spam at all. Installed this together with contact form 7. Still getting couple of spam messages per day.
22. Mai 2021
I'm using upto 4-5 honeypot fields and it works great. No spam in my mailbox. Sometimes you should adjust the honeypot fields but it works.
Alle 93 Rezensionen lesen

Mitwirkende & Entwickler

„Honeypot for Contact Form 7“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:


„Honeypot for Contact Form 7“ wurde in 18 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „Honeypot for Contact Form 7“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.



Added new feature: additional submission time check to improve bot-stopping power! Also, fixed small HTML issue and tidied up shortcode interface.


Improved backwards compatibility. Solves issues when plugin installed on older versions of CF7.


Better error checking for missing config problems.


General code cleanup, better adherence to WP coding standards and fixes for i18n functions.


Replaced text domain constant with plain string for better i18n compatability.


Hotfix for issue with options not being set on upgrade.


A significant update with a bunch of new things. Please see the release notes.


Minor update to change name to comply with CF7 copyright notice.


Added do-not-store for when forms are stored in the DB (i.e. Flamingo). Improved wrapper ID masking and customization.


Zusätzliche Funktionalität für die Verbesserung der Anti-Spam-Wirksamkeit.


Introduces ability to force W3C compliance. See here for details.


Addresses accessibility concerns regarding a missing label and disables autocomplete to prevent browser autocomplete functions from filling in the field.


Aktualisierungen für Funktionen-/Klassenanpassungen in Zusammenhang mit CF7 4.6. Lokaler Sprachsupport entfernt, stattdessen wird translate.wordpress.org verwendet.


I18n support hinzugefügt, Französisches Sprachpaket. Danke chis-kns


wpcf7_honeypot_accessibility_message und wpcf7_honeypot_container_css filters hinzugefügt, i18n Unterstützung


Provides backwards compatibility for pre-CF7 4.2, introduces ability to remove accessibility message.


Quick fix release to fix PHP error introduced in 1.6.3.


Updates to accommodate changes to the CF7 editor user interface.


Small change to accommodate validation changes made in CF7 4.1.


Small change to accommodate changes made in CF7 3.9.


Quite a lot of code clean-up. This shouldn’t result in any changes to the regular output, but it’s worth checking your forms after updating. Also, you’ll note that you now have the ability to add a custom CLASS and ID attributes when generating the Honeypot shortcode (in the CF7 form editor).


Added filter hook for greater extensibility. See installation section for more details.


Update to make compatible with WordPress 3.8 and CF7 3.6. Solves problem of unrendered honeypot shortcode appearing on contact forms.


Update to improve outputted HTML for better standards compliance when the same form appears multiple times on the same page.


Small update to add better i18n and WPML compatibility.


Small update for W3C compliance. Thanks Jeff.


  • Erstveröffentlichung