The API uses an algorithm that looks at the email address submitted for validation and determines whether there are alternative email addresses that are more likely that the one supplied. If there are, the API can return up to 8 suggested corrections (although, the most common scenario is that one correction is returned).
The table below provides suggested correction examples.
| Email address submitted for validation | Suggested correction |
|---|---|
| jane_doe@yahooo.com | jane_doe@yahoo.com |
| jane,doe@hotmail.com | jane.doe@hotmail.com |
| johndoe2gmail.com | johndoe@gmail.com |
| john.doe@al.com | john.doe@aol.com |
Note that the API validates email addresses before they are supplied as suggested corrections.
Corrections help correct syntax errors or typos in domain names for the email address submitted for validation. However, the API may return correction suggestions even if the email address supplied is valid. The presence of corrections does not relate to the validity of the email address. Corrections are supplied when they are more likely to be the intended email address than the original.
