RadarAddress – Fake and Mistyped Email Check for Contact Form 7

A visitor writes to you, you answer, and the reply bounces: the email was mistyped, or it was a throwaway address. The message is lost and so is the contact. RadarAddress checks the email address of every submission of every Contact Form 7 form, with nothing to configure beyond the API token: an unmistakable typo in the domain (gmial.com, hotmal.com…) is corrected and you receive the reply address that works, with the original kept; an address that cannot receive mail (a domain that does not exist, a disposable mailbox) is flagged, and refused with a message under the field only if you switch that on. The visitor who made a typo reads the corrected address in the confirmation message. In the forms where you map the address fields (street, postcode, city, province, country: the «RadarAddress» tab in the form editor), the address completes and corrects itself while the visitor types, from the national address registers of 25 European countries, and is verified on submission: outcome and verified form arrive to you. The visitor's fields are never rewritten and nothing ever blocks the submission. Where the outcomes go: at the end of the notification email (Mail 1), in the mail tags [_radaraddress_email_outcome], [_radaraddress_email_original], [_radaraddress_outcome], [_radaraddress_address] and [_radaraddress_reason] for whoever wants them in a precise place, and in the messages saved by Flamingo if the site uses it. What you get

• Every email field of every form verified: syntax, domain that receives mail, disposable mailbox, role address (info@, office@…), unmistakable typo corrected.
• The corrected address wherever the email is used: notification body, Reply-To, the autoresponder, Flamingo.
• Address autocomplete and correction on the field in the mapped forms, in the countries where the national address register is in service.
• Verification of the address on submission, with the verified form and the reason.
• Verification precision from strict to maximum: how far RadarAddress goes to find an address written badly.
• Typo correction level (1-3) for the email domain, and a «Did you mean …?» question on the field instead of a correction you did not choose.
• Fail-open by design: if RadarAddress does not answer, the submission goes through as usual.
• Data stays in the EU. Sources: the national address registers, published as open data.

How it works

1. Create a free account on radaraddress.com (every month 500 light checks and 50 contact checks are free).
2. Create an API token in your personal area.
3. Contact → Integration → RadarAddress: paste the token and press «Verify and save». The emails are verified from now on; to verify addresses too, map the fields in the «RadarAddress» tab of the form.

One light check is used per email verified; one contact check per address verified (typing is free; a selection from the suggestions and the verification of the same address count once). For most sites the free checks of the month are all they need; beyond that, packs and monthly subscriptions on radaraddress.com. Third-party service This plugin sends the email address and, in the mapped forms, the address typed in the form to the RadarAddress API (https://www.radaraddress.com) to get verification results and suggestions. Terms: https://www.radaraddress.com/en/terms — Privacy: https://www.radaraddress.com/en/privacy-policy.php

1.1.1

• The same email sent again is kept as written: no second question.

1.1.0

• New setting «Typo correction» (levels 1-3, default 3), separate from the address precision: 1 corrects only domains that do not exist (gmail.cob), 2 also domains with no mail server (libreo.it), 3 also domains that receive mail and misspellings by ear (gemail.com).
• «Did you mean …?»: when RadarAddress finds an address the visitor may have meant (a look-alike domain that works, a typo it does not correct at the chosen level, a correction your settings do not apply), the email field is refused with that question. The suggestion is never applied on its own.
• The visitor who sends the same address a third time within an hour gets it kept as written: no question and no correction. The outcome is «kept_as_written» and the suggestion is shown next to it.
• The suggested address is available as the mail tag [_radaraddress_email_suggestion] and in the outcome block of the notification.
• The typo correction level no longer depends on the address precision.

1.0.5

• The help under the API token says where to redeem a prepaid code: Enter a code, in your RadarAddress account.

1.0.4

• The precision setting also applies to email typo correction (levels 1-3; 4 and 5 count as 3): at 1 only domains that do not exist are corrected, at 3 also look-alike domains that receive mail (libera.it for libero.it).

1.0.3

• The "no API token" message names the menu as WordPress shows it: Contact → Integration → RadarAddress.
• "plugin" and the WordPress menu labels as WordPress translates them, in every language.

1.0.2

• Each verification tells the service which form and page it came from (X-RadarAddress-Form-Page and X-RadarAddress-Form headers, the page without its query string), so it shows up in the service log.

1.0.1

• The rate-limit transients use the plugin prefix.

1.0.0

• First release: email verification on every submission (typos corrected, addresses that cannot receive mail flagged or refused), address autocomplete and verification in the mapped forms, outcomes in the notification email, in mail tags and in Flamingo, settings in the Integration page.