Veqen uses explicit rules to suggest whether to admit, review or refuse a signup. Each response includes the signals that affected the score. The score is not a measured probability of fraud, and a clean result does not verify a person's identity.
How the score is calculated
Each detected signal has a weight between 0 and 100. Veqen combines them using:
score = round(100 × (1 − product(1 − weight / 100)))
For example, two 50-point signals combine to 75. Related signals may overlap; the formula does not mean that the observations are statistically independent or calibrated against your users.
| Score | Verdict | Suggested response |
|---|---|---|
| 0–29 | admit | Continue with your usual verification |
| 30–69 | review | Ask for another verification step or review the reasons |
| 70–100 | refuse | Apply your signup policy, with a recovery path for legitimate users |
These thresholds are defaults. Evaluate false positives against your own completed signups before automatically blocking users. Travelers, corporate VPN users, privacy-conscious users and people with international phone numbers can produce legitimate mismatches.
What each check observes
| Check | Sources | What it cannot establish |
|---|---|---|
| Syntax, disposable-domain lists, DNS mail records, cached RDAP registration facts | Ownership of an inbox or the identity of its user | |
| IP | DB-IP Lite geolocation and ASN databases, curated network classifications, the Tor exit list | Precise physical location or every residential proxy |
| Phone | Google's libphonenumber numbering metadata | Whether a number is currently active, who owns it, or its current carrier after porting |
| Signup | The checks above, plus phone/IP country mismatch and combined throwaway-email/server-network signals | Intent or definitive fraud |
Optional SMTP mailbox probing is available only when a separate prober is configured. An unconfigured or inconclusive probe reports that it was not checked and does not charge the additional mailbox credits. Email confirmation and SMS verification remain separate steps.
Data sources and freshness
- Disposable-email domain list: community-maintained, CC0. The download page provides JSON, CSV and text copies.
- DB-IP Lite: monthly releases, used under CC BY 4.0. Veqen checks for updates daily and retains an older release when a newer one is unavailable.
- Tor exit list: refreshed hourly when the refresh worker is enabled.
- Google libphonenumber: numbering-plan metadata bundled with the installed library version.
- DNS and RDAP facts are cached to reduce lookup latency. A recent registration or missing record is a signal, not a conclusion about a person.
Feeds and network lookups can be incomplete or temporarily unavailable. Inspect fields such as data_note, accepts_mail, and mailbox.checked; an unknown value does not mean safe. A domain appearing on a community list can also be a false positive. Contact support with the domain and evidence if a listing looks wrong.
Use the reasons in your product
Start with the free signup checker, then integrate the signup API. The reason-code reference explains stable codes for application logic. Avoid storing full checked inputs in logs unless your own privacy policy and retention controls cover them.
Veqen is operated by Keyveve, Inc.. Checks must follow the Acceptable Use Policy; they are not designed for eligibility decisions about employment, housing, credit or insurance.