This plugin validates email in realtime using live connections and aggregated data, by leveraging the ThreatPoint email verification API service
This plugin allows administrators include email validation using a real time verification service provided by the ThreatPoint email verification API.
The Plugin uses existing is_email functionality and passes manually entered email addresses to the restAPI service at ThreatPoint.
The response back from the ThreatPoint API provides information related to the email validity(valid email, valid domain, disposable, free, role, risk score).
The plugin calls the rest API (requires an API KEY) at this ThreatPoint api endpoint
The rest API is only passed the email address from the contact form via the is_email function.
This external service is called whenever a form using is_email is used. By default the Contact Form 7 is supported. You can include any form field name (email address field) in the plugin to override the default.
An API key is required to utilise the service, although the plugin will operate without one it will not be able to pass the email address or call any data from the API.
Your email addresses will not be validated without a valid API key.
This plugin only passes the email address information – no other PII is transferred. The email address is analysed across the aggregated data within the ThreatPoint email verification reputation service and a risk score with email properties (valid, free, role, disposable) to the plugin. Simple rules within the plugin dictate whether the email address is considered valid(set through the plugin settings). The email address is stored in the email address aggregated data and used as part of email address consortium for all customers. No other data such as originating website is stored. Only the email address is held, with date, time and risk scores associated with the request.
- Validates email addresses in real time including:
- Valid email
- Valid domain
- Disposable Addresses (One time Use)
- Role/Group Addresses
- Free Email Addresses
- Email Addresses known to be high risk (spam)
- API Documentation is available here: documentation
- Video is here
- Provide real time email validation and decisions through configuration to allow an administrator the correct flow for their site.
- API Key – An API key is required to access the email address validation service as explained above – (firstname.lastname@example.org)
- Blacklisted domains – a list of domains that you would not wish to have entered into your forms
- Email Field Name – the field name to pick the email address values from. Defaults to ‘your-email’ which is the contact form 7 default
- Allow Free Email addresses? – Option to allow or deny free email addresses (gmail, yahoo, hotmail etc.)
- Allow disposable Email addresses? – Option to allow or deny one time use email addresses
- Allows Role/Group Email Addresses? – Option to allow role and group email addresses (email@example.com) for example
- English (default) – only language currently supported
- Many thanks for taking the time to look at the plugin
- Drop the ThreatPoint team a line @threatuk on Twitter
- Email questions or suggestions via (firstname.lastname@example.org)
- Api key requests via email@example.com
- English – default, currently the only language supported
Contributors & Developers
- The ThreatPoint team are often asked to investigate attacks on web sites and other services. More often than not these attacks begin from IP addresses that should be considered before access is granted.
- ThreatPoint UK provide IP reputation, email verification, device reputation, dark web monitoring and password monitoring services as part of the API service layer. Please contact firstname.lastname@example.org to find out more about these additional services.
- The ThreatPoint IP Reputation WordPress plugin is also available from the WordPress official site.
- Many credits go to the fraud and analytics team at ThreatPoint UK and the team behind the API services
- Credits to numerous wordpress tutorials used to understand the plugin creation process. notably this article https://www.sitepoint.com/real-world-example-wordpress-plugin-development/