IP quality check

How “residential” does your connection look? A transparent score from checks that run entirely in your browser.

Consistency score

What we checked

Score = 100 minus fixed deductions per flag (network −40, WebRTC −25, timezone −15). No databases, no blacklists, no server — every check above runs in your browser and is listed with its result.

What this score means — and what it doesn’t

Fraud filters, streaming services, ticket shops and ad platforms all score incoming IPs. Their models are proprietary, but the public signals they lean on are consistent: does the network look residential or like a datacenter, do the connection’s facets agree with each other, and does the visitor’s environment fit the IP’s registration?

This page reads exactly those public signals from your own connection and combines them into a transparent score. It is not a blacklist lookup and cannot see private reputation data — a clean score here doesn’t guarantee every site will trust you, but a flagged one reliably explains why some sites don’t.

The checks, in plain language

Network type: the organization announcing your IP block. Consumer ISPs and mobile carriers read as “residential”; clouds, hosters and VPS providers read as “datacenter” — the single strongest signal, because normal visitors rarely browse from a server rack.

WebRTC agreement: whether the address WebRTC exposes matches your visible IP. A mismatch is the textbook fingerprint of a proxy or VPN in front of a different network.

Timezone plausibility: whether your device clock fits the country your IP is registered in. Sitting in a Tokyo timezone on a Frankfurt IP is exactly the kind of contradiction scoring systems weigh.

DNS resolver and address family are shown for completeness but not scored — public resolvers and IPv4-only lines are perfectly ordinary.

Why scores differ between checking sites

Commercial IP-reputation services blend abuse-report databases, spam-trap hits and crowd data they don’t publish, then update daily. Two services routinely disagree about the same address, and neither will tell you why.

We deliberately take the opposite approach: fewer signals, all of them public, every one shown with its result. When our score drops, you can see exactly which check caused it — and usually fix it.

If your score is low

On a VPN or proxy: that is the score working as intended — you’re borrowing a datacenter’s address. Choose providers whose exits are residential-typed, or accept the captchas as the cost of privacy.

On your home line with a “datacenter” flag: some smaller ISPs lease address space from hosting companies; registration data catches up slowly. Nothing is wrong with your connection, but strict sites may occasionally challenge you.

With a timezone flag: your device clock or region settings likely disagree with where your IP is registered — worth fixing, since it affects more than this score.

Common questions

Is this the same as the fraud scores other sites show?

No — and that’s the point. Commercial scores mix public signals with private blacklist and abuse data, and they don’t explain themselves. This score uses only signals your own browser can verify, and shows every check with its result.

Why does my VPN lower the score?

Most VPN exits live in datacenters, and the network-type check reads that directly from the address registration. That’s precisely what streaming services and shops detect too — it’s the trade-off of borrowing someone else’s address.

My home connection is flagged as datacenter. Should I worry?

Not for your security — it usually means your ISP announces its blocks under a hosting-flavored organization name, or leased space from one. It can, however, explain extra captchas and occasional geo-blocks on strict sites.

Can I improve my score?

You can fix contradictions: align your device clock and region with where you actually are, and eliminate WebRTC mismatches (see our leak test). The network-type signal belongs to your provider — only changing networks changes it.

Do you log my IP or share results?

No. There is no server: the checks run in your browser against open endpoints, and the score is computed and displayed locally. Reload the page and it’s gone.

Related tools & guides