Block bots at signup, login, and checkout

Bots flood your funnel with fake signups, fake clicks, and credential-stuffing attempts. Read the email, phone, and IP behind every request and block automated traffic at signup, login, and checkout.

https://phonevalidation.abstractapi.com/v1/
    ? api_key = YOUR_API_KEY
    & phone = 14154582468

{
    "phone": "14154582468",
    "valid": true
    "risk_score": 0.1,
    "registered_location": "San Francisco",
    "carrier": "Verizon USA",
    "line_type": "Mobile",
    "local_format": "4154582468",
    "international_format": "+14154582468",
"country_prefix" : "+1",
    "country_code": "US",
    "country_name":
"United Stated of America"
}

phone number validation api

{ "ip_address": "34.201.13.55", "is_hosting": true, "is_vpn": false, "is_proxy": false, "is_tor": false, "is_abuse": true, "asn_type": "hosting" }

The signals that expose a bot

Data-center and hosting IPs, the infrastructure most bot traffic runs on.
VPN, proxy, Tor, and relay connections that hide a bot's real origin.
Disposable emails and VOIP phone numbers on automated signups.
Known-abuse IP flags, updated continuously. SOC 2 compliant.
Known-abuse IP flags, updated continuously. SOC 2 compliant.
Trusted for bot detection by teams at
stars rating
4.8 from 1,863 votes
Logo compass
Wolters (1)
SalesforceLogo googleLogo pepsicoLogo wellfargo
Logo linkedinLogo paramount
Shadow left.avifShadow right.avif

How to block bots

Score every signup, login, and checkout in real time and get structured signals back in under 300ms.
Score every request
Send the email, phone, and IP from signup, login, or checkout to Abstract.
Read the risk flags
Get hosting IP, VPN, proxy, Tor, abuse, disposable email, and VOIP flags in one call.
Block, challenge, or allow
Set thresholds: block the clear bots, challenge the borderline ones, let real users through.
Phone validation
Flags VOIP and invalid numbers that bots use in bulk, and returns carrier and line type.
IP geolocation and risk
Flags datacenter, VPN, proxy, and Tor IPs, the infrastructure most bot traffic runs on.
Real time, not static
Every signal is checked as the request arrives, so bots are caught on the current attempt, not a stale snapshot.
Score traffic through the API
stars rating
4.8 from 1,863 votes
Read the email, phone, and IP behind every request, and block bots in one call.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
No credit card required

Why teams block bots with Abstract

Data-center and hosting IPs
Flag requests from hosting providers and data-center ASNs, where most bot traffic originates.
Disposable email and VOIP phone
Catch throwaway emails and VOIP numbers on bot-generated signups and OTP flows.
VPN, proxy, and Tor detection
Spot connections hiding behind a VPN, proxy, Tor, or relay before they reach your product.
Flags you can read
Get clear true or false signals, not one black-box score, so you write your own block and challenge rules.
For more information check our

The best build
on Abstract

Spammy signs up were an issue for us for a while, and we struggled to come up with the best way to identify all the variations in bad emails we were getting. Thankfully we found and quickly integrated with Abstract's email validation API, which saved us a bunch of time and gave us peace of mind.
Chris Stanley, Scope

Frequently asked questions

What is bot detection?

Bot detection is the practice of identifying automated traffic before it acts in your product. At signup, login, or checkout, you score the email, phone, and IP behind a request and flag the ones that look automated, so you can block or challenge them instead of treating a bot like a real user.

How can you tell if traffic is coming from bots?

The clearest tells are infrastructure signals: a data-center or hosting IP instead of a residential one, a VPN, proxy, or Tor connection, a disposable email, and a VOIP phone number. Bursts of signups from the same network or a sudden spike with no matching engagement are strong hints too.

What is the difference between bot detection and bot mitigation?

Detection is figuring out that a request is a bot. Mitigation is what you do about it: block, rate-limit, challenge, or send to review. You need both. Abstract sits on the detection side, returning the signals you feed into whatever mitigation rules fit your product.

Can bots bypass CAPTCHA?

Yes. Modern bots solve or bypass many CAPTCHAs, so CAPTCHA alone is not enough. Layering identity signals underneath, like data-center IP, VPN or proxy flags, and disposable email, catches automated traffic that sails through a CAPTCHA, without adding friction for real users.

Does bot detection add latency to signup?

No meaningful latency. Each check is a single request that returns in well under a second, so you can score traffic inline at signup or login. Only requests that cross your risk threshold get extra verification, so real users pass straight through.

What signals expose a bot?

The strongest signals are the IP (hosting or data-center ASN, VPN, proxy, Tor, and known abuse), the email (disposable or throwaway), and the phone (VOIP line type). Together they expose the infrastructure most bots run on. Sophisticated bots on residential proxies need a behavioral layer on top.

How does Abstract detect bots?

Call Abstract's IP Intelligence, Email Validation, and Phone Validation APIs when a request hits signup, login, or checkout. You get clear true or false flags for hosting IPs, VPN, proxy, Tor, disposable email, and VOIP numbers, so you can block or challenge automated traffic. Start free, no credit card.

Start blocking bots for free
stars rating
4.8 from 1,863 votes
Free to start. No credit card required.
get free api key
No credit card required