New accounts and masked browsers can let restricted users back into your product. ShieldLabs recognizes returning visitors and detects multi-accounting, helping you keep access limits effective.
Help keep restricted users from returning under new account details.
Detect disguised returns
Expose anti-detect browsers and masked connections at re-entry.
Protect genuine customers
Help keep repeated abuse from disrupting legitimate users.
Reduce detection work
Receive linked-user and risk detections without building a detection model.
Returning after a restriction
Make access restrictions stick. Across new accounts.
ShieldLabs detects multi-accounting among accounts registered under different emails to help enforce your access restrictions. Returning visitors remain recognizable across new sessions and IP changes.
Re-entry evidence
Protect access from masked re-entry. Keep legitimate visitors moving.
ShieldLabs detects browser bots and masking around restricted access. Help stop repeat sellers, members and promotion claimants from returning under disguised profiles.
Expose fabricated profiles
Detect anti-detect browsers and device spoofing around restricted access.
Reveal network masking
Detect VPNs and proxies used around re-entry attempts.
Keep legitimate returns open
Use trusted, suspicious and dangerous assessments to handle current access.
More than an IP restriction. The identity behind re-entry.
Combine persistent identity with device and network intelligence, named signals, bot detection, risk assessments and ready-made account abuse detection around access and registration.
Enterprise-level functionality. Without enterprise pricing.
Find returning activity. See the sources behind it.
Get recognized visitors, linked users and ready-made risk results. These detections can be integrated with the restriction and moderation records in your product.
Connect once and start receiving ready-made fraud and abuse detections.
01
Add the snippet or SDK
Connect your product and start identifying visitors and users.
02
Receive ready-made detections
Get detected fraud and account abuse in the dashboard or through API integrations.
03
Prevent fraud and abuse
Protect customer accounts, paid access and signup incentives in your product.
Developers
Integrate in 5 minutes.
A single API to identify, detect and score. Receive risk data through API responses and webhooks. Integrate selected data points into your business logic to prevent fraud and abuse.
Ban evasion is returning to a product after an access restriction, often through another account or a disguised browser or connection.
How does ShieldLabs help prevent ban evasion?
ShieldLabs recognizes returning visitors and detects multi-accounting, bots and masking. These ready-made detections help enforce the access restrictions in your product.
How to detect ban evasion after an IP change?
ShieldLabs recognizes returning browser visitors and detects multi-accounting when restricted participants create another registered account. Your product supplies the restriction record; a changed IP alone does not decide whether someone may return.
Does ShieldLabs store the account ban?
The restriction, reason and moderation decision belong to your product. ShieldLabs provides the identified activity and risk evidence used around the re-entry check.
Is ban evasion the same as multi-accounting?
Ban evasion means returning after a restriction recorded in your product. Multi-accounting is a ready-made detection of linked registered accounts. Recognition results and detected account links support your access enforcement.
Can this protect seller, member and promotion restrictions?
Yes. ShieldLabs detects multi-accounting and recognizes returning visitors around web access. Ready-made bot and masking detections add protection against disguised re-entry.