Preventing spam submitted through forms
Clone or download
freekmurze Merge pull request #9 from mercuryseries/patch-1
Fix small typo in SpamResponder interface name
Latest commit 68cd31c Jan 4, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
config Merge pull request #7 from larsjanssen6/random-field-name Jan 3, 2019
resources/views Fix encryped typo Dec 27, 2018
src wip Jan 3, 2019
tests Rename random to randomize Jan 2, 2019
.editorconfig add skeleton Dec 20, 2018
.gitattributes add skeleton Dec 20, 2018
.gitignore wip Jan 3, 2019
.scrutinizer.yml add skeleton Dec 20, 2018
.styleci.yml add skeleton Dec 20, 2018
.travis.yml add skeleton Dec 20, 2018 wip Jan 3, 2019 add skeleton Dec 20, 2018 add skeleton Dec 20, 2018 Fix small typo in SpamResponder interface name Jan 4, 2019
composer.json wip Dec 27, 2018
phpunit.xml.dist add skeleton Dec 20, 2018

Preventing spam submitted through forms

Latest Version on Packagist Build Status Quality Score StyleCI Total Downloads

When adding a form to a public site, there's a risk that spam bots will try to submit it with fake values. Luckily, the majority of these bots are pretty dumb. You can thwart most of them by adding an invisible field to your form that should never contain a value when submitted. Such a field is called a honeypot. These spam bots will just fill all fields, including the honeypot.

When a submission comes in with a filled honeypot field, this package will discard that request. On top of that this package also check how long it took to submit the form. This is done using a timestamp in another invisible field. If the form was submitted in a ridiculously short time, the anti spam will also be triggered.

After installing this package, all you need to do is to add a @honeypot Blade directive to your form.

<form method="POST">
    <input name="myField" type="text">


You can install the package via composer:

composer require spatie/laravel-honeypot

Optionally, you can publish the config file of the package.

php artisan vendor:publish --provider="Spatie\Honeypot\HoneypotServiceProvider" --tag=config

This is the content of the config file that will be published at config/honeypot.php:

use Spatie\Honeypot\SpamResponder\BlankPageResponder;

return [

     * Here you can specify name of the honeypot field. Any requests that submit a non-empty
     * value for this name will be discarded. Make sure this name does not
     * collide with a form field that is actually used.
    'name_field_name' => 'my_name',

    * When this is activated there will be a random string added
    * to the name_field_name. This improves the
    * protection against bots.
    'randomize_name_field_name' => true,

     * This field contains the name of a form field that will be use to verify
     * if the form wasn't submitted too quickly. Make sure this name does not
     * collide with a form field that is actually used.
    'valid_from_field_name' => 'valid_from',

     * If the form is submitted faster then this amout of seconds
     * the form submission will be considered invalid.
    'amount_of_seconds' => 1,

     * This class is responsible for sending a response to request that
     * are detected as being spammy. By default a blank page is shown.
     * A valid responder is any class that implements
     * `Spatie\Honeypot\SpamResponder\SpamResponder`
    'respond_to_spam_with' => BlankPageResponder::class,

     * This switch determines if the honeypot protection should be activated.
    'enabled' => true,


First, you must add the @honeypot blade directive to any form you wish to protect.

<form method="POST" action="{{ action(App\Http\Controllers\ContactFormSubmissionController::class, 'create') }}")>
    <input name="myField" type="text">

@honeypot will add two fields: my_name and my_time (you can change the names in the config file).

Next, you must use the Spatie\Honeypot\ProtectAgainstSpam middleware in the route that handles the form submission. This middleware will intercept any request that submits a non empty value for the key named my_name. It will also intercept the request if it is submitted faster than the encrypted timestamp that the package generated in my_time.

use App\Http\Controllers\ContactFormSubmissionController;
use Spatie\Honeypot\ProtectAgainstSpam;

Route::post([ContactFormSubmissionController::class, 'create'])->middleware(ProtectAgainstSpam::class);

If your app has a lot of forms handled by many different controllers, you could opt to register it as global middleware.

// inside app\Http\Kernel.php

protected $middleware = [
   // ...

Disabling in testing

By default, any protected form that is submitted in faster than 1 second will be marked as spammy. When running end to end tests, which should run as fast as possible, you probably don't want this.

To disable all honeypots in code, you can set the enabled config value to false.

config()->set('honeypot.enabled', false)

Customizing the response

When a spammy submission is detected, the package will show a blank page by default. You can customize this behaviour by writing your own SpamResponse and specifying it's fully qualified class name in the respond_to_spam_with key of the honeypot config file.

A valid SpamResponse is any class that implements the Spatie\Honeypot\SpamResponder\SpamResponder interface. This is what that interface looks like:

namespace Spatie\Honeypot\SpamResponder;

use Closure;
use Illuminate\Http\Request;

interface SpamResponder
    public function respond(Request $request, Closure $next);

Even though a spam responders primary purpose is to respond to spammy requests, you could do other stuff there as well. You could for instance use the properties on $request to determine the source of the spam (maybe all requests come from the same IP) and put some logic to block that source altogether.

If the package wrongly determined that the request is spammy, you can generate the default response by passing the $request to the $next closure, like you would in a middleware.

// in your spam responder
$regularResponse = $next($request)

Customizing the generated honeypot fields

To customize output generated by @honeypot, you can publish the honeypot view with:

php artisan vendor:publish --provider="Spatie\Honeypot\HoneypotServiceProvider --tags=views"

The view will be placed in resources/views/vendor/honeypot/honeypotFormFields.blade.php. This is the default content:

    <div id="{{ $nameFieldName }}_wrap" style="display:none;">
        <input name="{{ $nameFieldName }}" type="text" value="" id="my_name">
        <input name="{{ $validFromFieldName }}" type="text" value="{{ $encryptedValidFrom }}">

Events fired

Whenever spam is detected, the Spatie\Honeypot\SpamDetected event is fired. It has the $request as a public property.


composer test


Please see CHANGELOG for more information on what has changed recently.


If you need stronger spam protection, consider using Google ReCaptcha or Akismet.


Please see CONTRIBUTING for details.


If you discover any security related issues, please email instead of using the issue tracker.


You're free to use this package, but if it makes it to your production environment we highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using.

Our address is: Spatie, Samberstraat 69D, 2060 Antwerp, Belgium.

We publish all received postcards on our company website.


This package was inspired by the Honeypot package by Maksim Surguy.

Support us

Spatie is a webdesign agency based in Antwerp, Belgium. You'll find an overview of all our open source projects on our website.

Does your business depend on our contributions? Reach out and support us on Patreon. All pledges will be dedicated to allocating workforce on maintenance and new awesome stuff.


The MIT License (MIT). Please see License File for more information.