Reputation signals · public data

IP reputation check

Combine public reputation data, proxy and hosting flags, Tor exit lists and shared-egress signals to judge whether an IP fits your workload. The result reflects public signals, not a platform’s final decision.

Abuse historyProxy / hostingTorShared egress

Current IP reputation and risk snapshot

Read the current egress first, then show public reputation, proxy, Tor, hosting, sharing and native-IP signals. If a reputation feed is unavailable, the report says so instead of inventing a clean result.

Waiting for the report…
Current egress IP — — —
Heuristic risk score / 100
— pts
—
Network type—
ASN—
Native IP—
Checked at—

How to read it:—

Reputation:—

Source:—

2Look up any IP

Public IPv4 and IPv6 are supported; private addresses return a not-applicable notice.

Enter an address to see the result
Looked-up address — — —
Heuristic risk score / 100
— pts
—
Network type—
ASN—
Native IP—
Checked at—

How to read it:—

Reputation:—

Source:—

What is IP reputation?

IP reputation is a judgement about an address’s history and network identity. It can include spam, abuse, fraud, proxy, Tor, hosting and shared-egress signals. It is not a platform’s internal blocklist and it is not an official score.

A “not listed” result only means that a particular feed currently has no record. It does not prove the address was never abused, and it does not guarantee that a target platform will accept it.

Which signals are checked?

The report prefers explainable public signals over an untraceable total score. Coverage differs by source, so the page labels sources and uncertainty where possible.

  • Abuse and blocklists: spam, fraud, scanning and proxy samples.
  • Network identity: ASN, ISP and residential/mobile/hosting/enterprise type.
  • Anonymity: proxy, encrypted tunnel, Tor exit and shared egress.
  • Consistency: native IP, DNS location, WebRTC exposure and browser time zone.

How should I use the result?

Treat reputation as a clue, not a verdict. Sign-up, payment, advertising and social platforms also look at account history, device fingerprints, payment methods and request pacing. A low-risk IP can still be restricted because of account behaviour; a hosting IP can be perfectly fine for API calls.

If a signal fires, identify whether the problem is at the network layer or the account layer, then run one low-risk action in the target scenario.

Frequently asked questions

Is this a blocklist lookup?

It includes public blocklist and abuse signals, but also looks at proxy, hosting, Tor and shared-egress signals. It is broader than a single blocklist.

Why does reputation sometimes show as unavailable?

Some upstream feeds need a key or are temporarily unavailable. The page reports that honestly and does not turn missing data into “clean”.

Does a low score guarantee a block?

No. The score is a heuristic. Real platform risk decisions also depend on account, device, payment and behaviour.

How often should I retest?

IP reputation changes. Retest after changing IPs, when verification or rate limits appear, and before sensitive actions; record the time and result.

Read reputation together with purity

Reputation asks whether there is a history problem. Purity asks whether the address fits the current workload. Check both to avoid a single-score conclusion.