SOLUTIONS

Protect logins from account takeover

Notice when a login comes from a network the account has never used, or from a data center or Tor.

The problem

Stolen passwords are tried in bulk from servers and proxy networks. A hijacked session often shows up from a network the account owner has never used. Asking everyone for a second factor every time annoys the people you are protecting.

What you get for each address

• The network behind the address and its operator, to compare with the account’s usual ones
• Whether the address is hosting, a proxy or a Tor exit
• Fraud scores no older than you choose

A rule to start with

if card.network.asn not in account.known_asns and card.network.type == "hosting":
    require a second factor
if {"list": "tor"} in fraud.known:
    allow passkey sign-in only

An example to adapt, not a threshold we recommend. Every field is in the API reference.

Talk to usPricingAPI docs