Device intelligence you can use in an actual decision

IPCheckHQ gives your backend a compact view of the browser, device and network behind a signup. You get observable signals and their limits, not a mysterious fraud score that forces you to trust someone else's model.

Create a free project Explore the API

Start with the free plan. No card required.

Where device intelligence helps

Email and IP checks miss a common pattern: the same browser returning with a new address, a new inbox or a different account name. A project-scoped device identifier adds continuity without pretending that a browser is a person. Pair it with ASN, network type, proxy indicators and timezone consistency to understand the context around each attempt.

That context is most useful before an expensive action: issuing a trial, applying a promotion, creating a seller account or approving a sensitive login. Your application can allow normal traffic, ask for an additional check when several signals disagree, or send the attempt to review.

What you can build with it

One backend result

Exchange a short-lived browser token for the device ID, component hashes, IP intelligence and consistency checks your rules need.

Project-scoped identity

A device identifier is stable within your project and different in other customers' projects, reducing unnecessary cross-site linkage.

Signals with context

Network classifications and browser observations remain separate, so a VPN flag or shared IP never becomes an unexplained verdict.

A short path from browser to backend

1
Collect at the decision point
Run the browser SDK when a visitor submits the signup, trial or login form—not on every page view.
2
Exchange on your server
Send the single-use token from your backend with a secret key. The readable result never has to pass through the browser.
3
Apply proportionate rules
Combine the result with your own account history, payment signals and rate limits. Add friction only when the evidence warrants it.

Representative exchange response

POST /api/verify/v1/exchange

{
  "device": {
    "id": "dev_7da…",
    "visitor_id": "f8c…",
    "confidence": 0.97,
    "canvas_hash": "sha256:…",
    "webgl_hash": "sha256:…"
  },
  "network": {
    "asn": 13335,
    "network_type": "residential",
    "vpn": false,
    "hosting": false
  },
  "consistency": {
    "timezone_matches_ip": true
  }
}

Limitations worth designing for

A browser fingerprint can change after browser, operating-system, hardware or privacy-setting changes.
Shared computers and managed fleets can legitimately produce the same or very similar observations.
VPN, proxy and hosting classifications are estimates. They should influence a review, not serve as proof of intent.

Privacy is part of the implementation

Collect device intelligence only where it serves a disclosed security or abuse-prevention purpose. IPCheckHQ returns the result to your backend; you decide what to retain and for how long. Keep the data out of marketing profiles, restrict access, and document the lawful basis that applies to your users and region.

Read the IPCheckHQ privacy approach

Practical questions

Is device intelligence the same as a device ID?: No. The device ID is one project-scoped identifier. Device intelligence includes the underlying browser, network and consistency signals used to interpret an event.
Can it replace account and payment checks?: No. It works best as another independent source of context alongside account history, payment data and rate limits.

Test the workflow in your own application

Create a project, allow your development origin and complete the first token exchange before choosing an enforcement rule.

Create a free project