Trestle’s email data can be used for verification use cases. Given that every person has multiple emails with varying levels of use, we generally do not encourage using this email data as an additional channel of communication via email campaigns, etc., unless the user has provided the email explicitly to the business.
Identity Verification: #
Our Real Contact API provides a couple of email address checks. This includes an email validity check, which covers the following:
- Syntax-related checks.
- Whether the inbox exists and the email is deliverable.
- Whether it uses a disposable domain.
- Whether it is a tumbled or role-based account.
- Whether the email is junk based on specific words used in the username.
These are just some of the checks that are completed, but they give you an idea of how this can be useful for identity verification. In addition, the email-to-name match confirms if the name provided on the lead/sign-up form matches the name associated with the email in Trestle’s Identity Graph. IP-based intelligence can also help assess the legitimacy of the interaction. For example, a valid email paired with a low trust score or high IP-to-address distance may indicate a bot or fraudulent submission, even if the email checks pass on their own.
Typical rules we see customers use here are: #
is_valid = false OR contact_grade = F, REJECT lead.
name_match = B, additional steps in the workflow (e.g., email verification via a link) to confirm that the email does belong to the person signing up.
Let us know if you have additional questions/suggestions about our email checks via support@trestleiq.com.