Skip to main content
Jan 2026Google disrupts IPIDEA — a residential proxy botnet used by 550+ threat groups.Why this matters →
Bot Signals · IP Reputation

Bots can't fake
proxy behaviour.

Modern bots run real browsers on residential IPs and solve their own CAPTCHAs — the bot looks human. The connection doesn't. Reputable reads the network signals traditional defenses miss and hands you a signed report on every request. Your thresholds, your call.

Bot traffic can exceed 50% of web requests — on some sites, 90%+ is crawlers, scrapers, and probing.

signed signal report
ip_typedatacenter
asnAS9009 · M247
ja4t13d1516h2_8daa…
timingrelay_pattern
geo_latencyanomalous
score83 / 100
signals6 attached
evidence
timing:relay_patternip:datacentergeo:latency_mismatch
Detect proxies
The signal traditional defenses miss
Fingerprint TLS
JA4 on every request, no enterprise contract
Flag bad traffic
Label bots, scrapers & fraud in analytics
Ship in minutes
Script tag to first signed report

Live in about a minute.

No sales call, no DNS changes, no reverse proxy. Sign in, paste the script tag, read the signed report.

1 · Sign in & create keys2 · Paste the script tag3 · Read the signed report
<script
  src="https://cdn.reputable.click/verify/v1/reputable.js"
  data-reputable-key="pk_..."
  async></script>
{ "ticket": "eyJ…",
  "report": {
    "proxyScore": 83,
    "ipType": "datacenter",
    "signals": { "timing": "relay_pattern", … }
  } }

Three jobs, one signal report.

Keep bots out of your analytics.

Bot traffic doesn't just scrape — it votes in your metrics. Conversion rates, campaign ROI, A/B tests: all skewed by traffic that was never going to buy. The script tag scores every page view and tells your tag manager which ones to keep out of the data. Your analytics, minus the noise.

Works with GTM and any dataLayer-aware setup.

dataLayer event
event: "reputable_signals"
proxyScore: 83
ipType: "datacenter"
omitAnalytics:true
→ analytics tags suppressed for this view

Require a signed ticket on signups and logins.

Drop the widget into a form. It reads the visitor's network — TLS fingerprint, connection timing, IP type — and attaches a short-lived signed ticket your backend verifies before trusting the request. Like a CAPTCHA box, except it hands you evidence instead of a checkbox, and only escalates to a real challenge when your thresholds ask for one.

Verify offline against our JWKS — no callback required.

email
password
Checked
signals attached
reputable.click
Create account

See the AI scrapers — real and fake.

AI crawlers are a growing share of web traffic, and plenty of scrapers wear their user agents as a disguise. We check claimed crawlers against their operators' published networks: the real ones get labeled, the impostors get caught — datacenter IP, wrong network, timing that says relay.

GPTBot, ClaudeBot, PerplexityBot, Bytespider, CCBot and more.

AI traffic, last 24h
GPTBot✓ verified
PerplexityBot✓ verified
"ClaudeBot"✗ impersonator · datacenter
"GPTBot"✗ impersonator · vpn

Evidence, not a checkbox.

Proxy behaviour leads every report — the tell a bot can't fake — backed by the rest of the network evidence and a 0–100 score. You set the thresholds; the decision stays yours.

Proxy Behaviour

The strongest tell a bot can't fake: how its connection actually behaves. Proxies and relays in the path stand out even when the IP and fingerprint look clean.

IP Classification

Datacenter, VPN, privacy relay, satellite, or residential — with the ASN and operator behind it.

Geo-Latency Consistency

When an IP's network behavior doesn't match its claimed location, that mismatch is a strong relay signal.

JA4 TLS Fingerprint

The client's TLS handshake fingerprint — automation stacks stand out no matter what user agent they claim.

Verified Bot Identity

Claimed crawlers checked against their operators' published networks — verified, unverified, or impersonator.

Score + Detections

A 0–100 proxy score, per-factor breakdown, and stable detection ids you can write rules against.

Signal over noise.

Start with signed signal reports. Grow into company-specific reputation built from your real traffic — the same proxy-behaviour engine, tuned to the actions that matter in your product, not generic global labels.

Deep Integration

Capture high-signal context around meaningful in-app actions — the steps users take, when, and whether sessions behave like real intent. This is where “real browser” bots slip up.

Your Reputation DB

Decide on visitors in your ecosystem. If an IP or session behaves suspiciously in your flows, that matters more than a generic global label.

Clean Decisions

Tag key events with a decision and reasons. Filter analytics and attribution, and drive inline allow / challenge / block at the moments that matter.

Everything in Bot Signals, plus:

  • Per-company IP / session / ASN / JA4 reputation
  • Behavioral & session-trust scoring
  • ASN / JA4 → IP reputation inheritance
  • Inline allow / challenge / block decisions
  • Clean analytics & attribution
Get a traffic review
Get started

Create a free key.

Sign in, create a key pair, paste the script tag. Your first signed signal report lands in about a minute — and the dashboard starts showing you what your traffic is really made of.

Loading auth state...

Real customers never see a CAPTCHA wall.