Gravity Perks Blocklist

Forms attract spam, abusive messages and entries that were never meant to come through, such as reserved usernames or invalid promo codes. Gravity Perks Blocklist deals with this by validating form input against the Disallowed Comment Keys list that WordPress already uses. Anything on the list is rejected, which keeps your entries cleaner and easier to work with.

You decide where the check applies: a single field, several fields or the whole form. Blocked entries can show a validation error, or they can be sent straight to spam so the sender is not alerted. Developers can adjust the logic with filter hooks. It suits any Gravity Forms setup, from a simple contact form to a longer registration form.

Features

• Disallowed Comment Keys validation: Form fields are checked against the WordPress Disallowed Comment Keys list, so words, phrases and IP addresses you already block in comments are also blocked in form submissions.
• Flexible field targeting: Apply blocklist validation to one field, multiple fields or every field in the form, so the check matches how each form is built.
• One shared blocklist: Because it uses the comment spam prevention list in WordPress, you can maintain a single blocklist that covers both comments and Gravity Forms submissions.
• Honeypot rejection: Blocked submissions can be rejected silently through honeypot functionality, which stops them without telling spammers that their entry was caught.
• Send blocked entries to spam: Instead of showing a validation error, you can route blocklisted submissions directly to spam, giving you control over what the person filling in the form sees.
• IP blocking with CIDR notation: Block IP addresses using CIDR notation to target network-level spam sources and abusive users with more precision than single addresses allow.
• Custom policy enforcement: Set up rules such as reserved username restrictions, invalid promo code prevention and blocked email filtering to keep unwanted data out of your forms.
• Developer filter hooks: Filter hooks such as gpb_value, gpb_ip and gpb_user_agent let developers customize the validation logic and the way responses are handled.

Best for

• Gravity Forms sites dealing with steady form spam
• Registration forms that need reserved names or blocked emails
• Developers who want filter hooks for custom validation