Netbait checks an IPv4 address and returns a reputation score for scanners, botnets, proxies, VPNs, datacenter ranges and suspicious automated activity.
An IP address is not just a number. Netbait turns it into a usable risk signal.
The score endpoint returns a plain decimal value. Use it directly in allow, review, throttle or block logic.
The detail endpoint expands the same lookup with source lists, first and last seen dates, company records, abuse contacts, ASN route data, location hints and classification flags.
{{ detailOutput }}
One public endpoint returns a decimal score from 0 to 1 for an IPv4 address. Keep the policy on your side: allow, log, throttle, challenge or block.
Use the detail endpoint when you need ASN, route, organization, location, abuse contact and classification flags.
Standard score and detail lookups work without authentication. Tokens are only needed for higher rate limits.
Every checked address can open a public report page with reputation, network ownership and approximate location when available.
{{ activeCaseDesc }}
{{ activeCaseSignals }}
{{ activeCaseActions }}
An IP scorer assigns a risk value to an address using reputation and network intelligence. Instead of relying on a single blocklist, the score gives your system a compact signal that can be combined with your own logs, users and business rules.
Netbait focuses on practical infrastructure signals: known abuse, scanning behavior, suspicious automation, datacenter ranges, proxy and VPN indicators, ASN context, route data and abuse contacts when available.
A score is not a magic verdict. It is a consistent risk signal your application can act on.
A clean score does not guarantee that an address will stay clean forever. Reputation changes as machines are compromised, cleaned, reassigned or reused.
The API is plain HTTP. Call it from a backend, firewall worker, signup flow, rate limiter, log pipeline or SOC enrichment job.
Use /v1/score/{ip} when you only need the risk number. Use /v1/detail/{ip} when you need the full JSON profile.
Score and detail lookups without authentication for standard usage.
Request a token when the public limit is not enough for your integration.