Reason Codes
Understeanding Digital Trust and Risk Indicators
This section provides a comprehensive list of reason codes obtained via API.
Each reason code comprises:
- CODE: A unique code to specifically identify an item. The code in alphanumeric format is used to reference the reason code in the API.
- NAME: A name to clarify its primary focus. The name might contain "DEPRECATED" if the reason code is no longer in use. In this case the reason code is still available for historical purposes.
- DESCRIPTION: A description that delves deeper into the details of the reason code.
- WEIGHT: The severity in cas of Risk Signals, or the importance in case of Trust Signals.
RISK SIGNALS
Risk Signals provide warnings and red flags about potential dangers or inconsistencies related to a product or combination of products.
| code | name | description | weight |
|---|---|---|---|
| RB001 | Browser Settings | The browser is requesting to websites not to collect or track browsing data | 2 |
| RB002 | Browser Privacy Related Plugins | The targeted browser comes with some installed plugins that mask user activity while browsing the internet | 2 |
| RB003 | Browser Unusual Number of Devices | The input/output devices count retrieved from the browser is unusual | 1 |
| RB004 | Browser Unusual Name | The browser name is unusual | 2 |
| RB005 | Browser Unusual OS | The OS associated to the browser is unusual | 2 |
| RB006 | Browser Unusual Device Type | The device type associated to the browser is unusual | 1 |
| RD001 | Device Unusual Type | The device type is unusual | 1 |
| RD002 | Device Unusual Browser Name | The browser name associated to the device is unusual | 1 |
| RD003 | Device Unusual OS | The OS associated to the device is unusual | 1 |
| RC001 | Phone Full Name Inconsistency (Public Records) | The first and last name provided by the user does not match with public records | 1 |
| RC002 | DEPRECATED Phone First Name Inconsistency (Public Records) | The first name provided by the user does not match with public records | 1 |
| RC003 | DEPRECATED Phone Last Name Inconsistency (Public Records) | The last name provided by the user does not match with public records | 1 |
| RC004 | Ip Phone Country Inconsistency | The country associated to the ip address does not match with the country of the phone number | 1 |
| RC005 | DEPRECATED Email Last Name Inconsistency (Google) | The last name provided by the user do not correspond to those associated with the google account | 1 |
| RC006 | DEPRECATED Email Full Name Inconsistency (Parsed) | The first and last names provided by the user do not correspond to those associated with the email address | 1 |
| RC007 | Email And Phone Inconsistency | The email address and phone number are not linked to each other | 3 |
| RC008 | Email And Phone Inconsistency | The email address is associated to a different phone number | 1 |
| RC009 | Email Full Name Inconsistency (Skype) | The first and last names provided by the user do not correspond to those associated with the skype account | 1 |
| RC010 | Email Black-list | The identity is linked to an unusual number of requests with different digital signals | 3 |
| RC011 | Browser Ip Language Inconsistency | The language of the IP country does not match the language of the browser | 1 |
| RC012 | DEPRECATED Phone Name Inconsistency | The first and last names provided by the user do not correspond to those associated with the phone number | 1 |
| RC013 | Email And Phone Inconsistency | The phone number is associated to a different email address | 1 |
| RC014 | Phone Full Name Inconsistency (Skype) | The first and last names provided by the user do not correspond to those associated with the skype account | 1 |
| RC015 | Email Full Name Inconsistency (Public Records) | The fist name and the last name provided by the user does not match with the public records | 1 |
| RC016 | Browser Ip Timezone Inconsistency | The timezone of the IP does not matches the timezone of the browser | 1 |
| RC017 | DEPRECATED Email First Name Inconsistency (Google) | The first name provided by the user does not match with the first name linked to the google account | 1 |
| RC018 | Email Full Name Inconsistency (Google) | The first and last names provided by the user do not correspond to those associated with the google account | 1 |
| RC019 | Email Full Name Inconsistency (Parsed) | The first and last names provided by the user do not match to those parsed from the email address | 1 |
| RC020 | Email Phone Faces No Match | All profile pictures obtained from both email and phone sources exhibit faces that do not match, underlying possible inconsistency among them | 2 |
| RC021 | Phone Number with too many emails | Multiple email addresses are linked to the provided phone number, suggesting potential misuse or security concern | 1 |
| RC022 | Email Address with too many phones | Multiple phone numbers are linked to the provided email address, suggesting potential misuse or security concern | 1 |
| RC023 | Phone Number with too many ips | Multiple ip addresses are linked to the provided phone number, suggesting potential misuse or security concern | 1 |
| RC024 | Email Address with too many ips | Multiple ip addresses are linked to the provided email address, suggesting potential misuse or security concern | 1 |
| RC025 | Phone Number with too many devices | Multiple devices are linked to the provided phone number, suggesting potential misuse or security concern | 1 |
| RC026 | Email Address with too many devices | Multiple devices are linked to the provided email address, suggesting potential misuse or security concern | 1 |
| RC027 | Email Address with too many names | Multiple names are linked to the provided email address, suggesting potential misuse or security concern | 1 |
| RC028 | Phone Number with too many names | Multiple names are linked to the provided phone number, suggesting potential misuse or security concern | 1 |
| RC029 | Email Phone Skype Country Consistency | The country retrieved from the skype account associated to the email address does not match with the country retrieved from the skype account associated to the phone number | 1 |
| RC030 | Email Name Inconsistency (Data breaches) | The user's first and last names do not match the names found in the data breach records associated with the provided email address | 1 |
| RC031 | Phone Name Inconsistency (Data breaches) | The user's first and last names do not match the names found in the data breach records associated with the provided phone number | 1 |
| RE001 | Email Low Velocity | Absence or very low number of connected accounts to this email address | 2 |
| RE002 | Email Disposable | Disposable or a temporary email address | 3 |
| RE003 | Email With Stop-Words | This email address contains stop words, namely words which are considered to be insignificant | 3 |
| RE004 | Email Names Inconsistency | The names retrieved from various services associated to the email address (google, skype, parsed, social networks) are not consistent | 1 |
| RE005 | Email Invalid | This email address is undeliverable and has an 'invalid' status | 3 |
| RE006 | Email Without Data Breaches | The lack of any data breaches suggests that it is possibly a newly created email | 1 |
| RE007 | Email Spam Trap | This email is marked as invalid and flagged as a spam-trap by email service providers | 3 |
| RE008 | Email Alias | The email address acts as forwarders/alias and is not a real inbox | 2 |
| RE009 | Email Format | The username of the email address contains suspicious characters or numbers | 1 |
| RE010 | Email Syntax Error | The email address contains syntax errors and is not a valid email | 1 |
| RE011 | Email With Too Many Data Breaches | This email address is present in much more data breach than usual, indicating a shared email | 3 |
| RE012 | Email Typo | There is a possible spelling error in the domain name of the email address | 1 |
| RE013 | Email Business Without Domain | A lack of a public website under a corporate email domain it may be an indication of suspicious email address | 2 |
| RE014 | Email String Analysis (No Consonants) | The absence of consonants in an email indicates a suspicious address | 2 |
| RE015 | Email String Analysis (No Vowels) | The absence of vowels in an email indicates a suspicious address | 2 |
| RE016 | Email String Analysis (Too Short) | The email address appears to be too short, which often suggests a shared email address or a potentially fake one | 2 |
| RE017 | Email Name Invalidity (Google) | The name retrieved from the google account associated to the email address is not valid | 2 |
| RE018 | Email Substatus Quota Exceeded | This substatus flags an address that surpassed its storage limit and is temporarily unable to receive emails | 2 |
| RE019 | Email Substatus Toxic | This substatus flags for abuse, spam, or potential bot creation, these emails should be avoided if labeled with this designation | 2 |
| RE020 | Email Substatus Mx Forward | This substatus flags an address linked to domains forwarding MX records to a single domain, akin to disposable domains | 2 |
| RE021 | Email Substatus Possible Disposable | This substatus flags an address with a non-disposable domain but a format indicating it may be created for such purposes | 2 |
| RE022 | Email Substatus Alternate | This substatus flags a valid secondary email used for account sign-ups with limited engagement | 2 |
| RE023 | Business Email Without Company | The provided email is labeled as a business address but lacks associated company details, making it unusual | 2 |
| RE024 | Email Name Inconsistency | The names retrieved from various services associated to the email address are not consistent with the provided first and last name | 1 |
| RE025 | Email Domain Is Parked | The provided email has a parked domain, indicating potential inactivity or lack of legitimacy | 1 |
| RE026 | Email Image Without Person | None of the images retrieved from the email contain a person or a face | 1 |
| RE027 | Email Images Contain Celebrity | At least one of the images retrieved from the provided email address features notable personalities or celebrities | 1 |
| RE028 | Email Faces No Match | At least one couple of profile pictures obtained from email exhibit faces that do not match, underlying possible intra-signal inconsistency | 1 |
| RE029 | Email Without Profile Picture | There are no profile picture associated to this email address | 1 |
| RE030 | Email With Too Many Phone Partials | The number of phone partials extracted from the provided email address is unusually high, suggesting potential data integrity issues or abnormal patterns | 1 |
| RE031 | Email Business With Suspicious Characters | The provided email is business but contains numbers, indicating a possible suspicious pattern | 1 |
| RI001 | IP Suspicious Connection | The IP address is originating from an unusual source, suggesting a possible attempt to mask the connection type | 2 |
| RI002 | IP Masking (Proxy) | It has been detected that the user is connecting via a proxy, which suggests an attempt to conceal their network activity. | 3 |
| RI003 | IP Masking (TOR) | It has been detected that the user is utilizing a TOR connection, which strongly suggests an attempt to conceal their network activity | 3 |
| RI004 | IP Masking (VPN) | A VPN connection has been detected, which suggests that the user may be attempting to conceal their online activities | 2 |
| RI005 | IP Blacklisted | The ip address has been reported in a blacklist that indicates that it could be the source of some sort of abuse | 1 |
| RI006 | IP Remote Access | The IP address enables connection from the most common remote desktop software, highlighting potential security risks | 1 |
| RI007 | IP Is Valid Format | Indicates if the IP is in an accepted ipv4 or ipv6 format | 2 |
| RN001 | Name Invalid | The first and last name provided by the user is not valid. This could be due to various reasons, such as the name being fake, vulgar, or a placeholder, among other possibilities. | 3 |
| RN002 | Name Too Short | The first and last name provided by the user are too short, underlying suspicious patterns | 3 |
| RP001 | Phone Disposable | The phone number is flagged as disposable and is likely a temporary number | 3 |
| RP002 | Phone Without Profile Picture | There are no profile picture associated to this phone number or the messaging apps are set to private | 1 |
| RP003 | Phone Image Without Person | None of the images retrieved from the phone contain a person or a face | 1 |
| RP004 | Phone Low Kyc MNO | The phone number belongs to a mobile network operator that can be activated without identity checks | 2 |
| RP006 | Phone Invalid Format | Phone number is not correctly formatted | 3 |
| RP007 | Phone Suspicious Format | Phone number contains a suspicious sequence of digits | 3 |
| RP008 | Phone Without Messaging App | If there is no messaging app enabled for a particular phone number, it could indicate that the number is not actively in use | 2 |
| RP009 | Phone Low Velocity | The absence of external account connections for the phone suggests that it may be a newly activated or an invalid number | 2 |
| RP010 | Phone Names Inconsistency | The names retrieved from various services associated to the phone number are not consistent | 1 |
| RP011 | Phone Without Porting History | The phone number does not seem to be ported, suggesting that it may be a newly created number | 1 |
| RP012 | Phone Unusual Number Type | The phone number type is unusual and this might indicate that the phone number is not reliable (Pager, toll-free, voicemail) | 1 |
| RP013 | Phone Unknown Number Type | The phone number type could not be determined | 1 |
| RP014 | Phone Images Contain Celebrity | At least one of the images retrieved from the provided phone number features notable personalities or celebrities | 1 |
| RP015 | Phone Faces No Match | At least one couple of profile pictures obtained from phone exhibit faces that do not match, underlying possible intra-signal inconsistency | 1 |
| RP016 | Whatsapp Business Not Reliable | The phone number have a WhatsApp business account, but the associated information are minimal, underlining a suspicious behaviour | 2 |
| RP017 | Phone With Too Many Email Partials | The number of email partials extracted from the provided phone number is unusually high, suggesting potential data integrity issues or abnormal patterns | 2 |
| RP018 | Phone Country Code Inconsistency | The country codes retrieved from various sources associated to the provided phone number do not match | 1 |
| RP019 | Phone Recently Ported | The phone number has been recently ported to a different carrier, indicating suspicious activities | 1 |
| RP020 | Phone Without Data Breaches | The lack of any data breaches suggests that it is possibly a newly created phone number | 1 |
| RP021 | Phone With Too Many Data Breaches | This phone number is present in much more data breaches than usual, indicating a shared phone number | 1 |
| RP022 | Phone Ported Too Many Times | The phone number has been ported to a different carrier multiple times, suggesting potential fraudulent activity or identity misuse | 1 |
| RT001 | Tax ID Invalid | The tax id provided by the customer contains syntax error and is not valid | 3 |
TRUST SIGNALS
On the other hand, Trust Signals highlight positive aspects and assurances of a product or combination of products.
| code | name | description | weight |
|---|---|---|---|
| TC001 | Browser IP Language Consistency | The language of the IP country does match the language of the browser | 2 |
| TC002 | Browser IP Timezone Consistency | The timezone of the IP does matches the timezone of the browser | 2 |
| TC003 | Email Full Name Consistency (Google) | The first and last names provided by the user correspond to those associated with the google account | 2 |
| TC004 | Email Name Consistency | The first and last names provided by the user correspond to those associated with the email address | 2 |
| TC005 | Email Phone Consistency | The email address and phone number are linked to each other | 3 |
| TC006 | Email Full Name Consistency (Skype) | The first and last names provided by the user correspond to those associated with the skype account | 2 |
| TC007 | Phone Full Name Consistency (Public Records) | The name provided by the user does match with public records | 2 |
| TC008 | Phone Full Name Consistency (All Services) | The first and last names provided by the user correspond to those associated with the phone number | 2 |
| TC009 | Phone Full Name Consistency (Skype) | The first and last names provided by the user correspond to those associated with the skype account | 2 |
| TC010 | Email Phone Faces Match | At least a pair of profile pictures obtained from the provided email and phone exhibit faces that perfectly match, underlying congruence among them | 1 |
| TC011 | Email Phone Skype Country Consistency | The country retrieved from the skype account associated to the email address correspond to the country retrieved from the skype account associated to the phone number | 1 |
| TC012 | Email Phone Consistency | The provided phone number matches with the information retrieved from the provided email address | 1 |
| TC013 | Email Phone Consistency | The provided email address matches with the information retrieved from the provided phone number | 1 |
| TC014 | Email Name Consistency (Public Records) | The first and last names provided by the user match with the public records | 1 |
| TC015 | Email Name Consistency (Parsed) | The first and last names provided by the user match with those parsed with the email address | 1 |
| TC016 | Email Name Consistency (Data breaches) | The user's first and last names match the names found in the data breach records associated with the provided email address | 1 |
| TC017 | Phone Name Consistency (Data breaches) | The user's first and last names match the names found in the data breach records associated with the provided phone number | 1 |
| TC018 | Name Phone Consistency | The initial letters of the provided first or last name match the characters available in the email addresses retrieved from the provided phone number, indicating alignment between user details and associated data. | 1 |
| TE001 | Email Domain Age | The domain associated with this corporate email exists for at least 3 years | 1 |
| TE002 | Email With Data Breaches | The presence of any data breaches suggests that it is a email address not recently created | 1 |
| TE003 | Email Internal Consistency (Names) | The names retrieved from various services associated to the email address are consistent | 1 |
| TE004 | Email Regular Velocity | The presence of accounts connected to the email address suggests that it in use | 1 |
| TE005 | Email With Web Reviews | There is at least one reviews associated with this email account | 3 |
| TE006 | Email With History | The information retrieved from the email address suggest that the provided email is not a newly created email | 2 |
| TE007 | Email With Company | The email address is associated to a company | 2 |
| TE008 | Email Image With Person | At least one of the images retrieved from the email contain a person or a face | 1 |
| TE009 | Email Internal Consistency (Phones) | The phone numbers retrieved from various services associated to the provided email address are consistent with each other | 1 |
| TI001 | IP Regular Connection | The IP address is originating from a trusted source | 1 |
| TP001 | Phone Image With Person | At least one of the images retrieved from the phone contain a person or a face | 1 |
| TP002 | Phone Internal Consistency (Names) | The names retrieved from various services associated to the phone number are consistent | 1 |
| TP003 | Phone Number Is Ported | The phone number has been ported at least once, indicating probable current usage | 1 |
| TP004 | Phone Regular Velocity | The presence of external account connections and messaging apps for the phone suggests that it is in use | 1 |
| TP005 | Phone Country Codes Consistency | The country codes retrieved from various sources associated to the provided phone number match | 1 |
| TP006 | Phone Internal Consistency (Emails) | The email addresses retrieved from various services associated to the provided phone number are consistent with each other | 1 |
For more information about our API you can go Api Reference
Updated 9 days ago