IP reputation checker

A source names this exact address in a record against it.

Adverse context was observed; no covered record names this exact IP.

Sources disagree. Review the conflicting location or routing records.

Some evidence is unavailable. LIMITED describes coverage, not an adverse finding.

No source covered here reports anything against this address.

Platforms also weigh account, device, payment and behaviour signals no IP check can see.

is not a public internet address, so no external IP evidence check is made.

This address is in Shared Address Space (100.64.0.0/10), used inside provider networks. It is not a public exit address. This lookup cannot establish how many subscribers share the public connection behind it; no external source was queried.

It is a hosting address, which many platforms treat with more friction than a home connection — that is a role, not a finding.

Sources identify a mobile network role. That alone does not establish whether this exit is shared.

Sources identify a residential network role, not an exclusive household connection.

It answers public infrastructure queries, which is a role rather than a finding.

It is a Tor exit, which is a network role and not an abuse record.

It carries privacy-relay evidence, which is a network role and not an abuse record.

Enter an IP address, a prefix (8.8.8.0/24) or an ASN (AS15169), or choose My IP to check this connection.

Not an IP address, prefix or ASN. Try 8.8.8.8, 8.8.8.0/24 or AS15169.

This connection has made too many lookups and the counter clears shortly.

The lookup counter has cleared. Run the check again.

This deployment has no active source licence profile, so no evidence may be shown. Retrying will not change that.

The request never reached IPJury. Check the connection and run it again.

This page cannot read the record the server sent. Reload the page to update it.

The sources did not answer in time, so no verdict was reached. Nothing is concluded about this address either way.

This juror is not enabled in this deployment, so it was never asked.

No outside request was made for this address.

The source did not answer inside the deliberation window.

This address falls outside the coverage this source claims.

The source could not be reached for this check.

This juror is licence-gated and stays withheld until its permission profile is active.

This juror returned no usable record for this address.

An abstention is missing coverage, not a negative finding. It is shown, never counted as a “no”.

Provenance for this axis only. Axes are never averaged into one score.

No material disagreement among responding jurors.

This does not prove universal accuracy or safety. Read coverage and limitations before relying on the result.

Not covered by this source

Not asserted by this source, which is not a NO

Withheld by the active display profile

Source abstained

No changes recorded in the observation window

Change history not retrieved for this result · refresh to load it

Experimental policy index, not a probability or platform guarantee. Independent evidence band remains unchanged.

Both inputs are one address: one record, not two independent answers.

One side has no record; no axis can be compared.

The network this address sits in, from operator and usage classification. It describes the network's type, not this address's traffic.

This exact address, in the covered proxy, VPN, relay and Tor sources.

Records that name this exact address. Surrounding-prefix context is labelled as such and is never a record about this address.

Estimates the databases publish for the range that holds this address; for your own check, also where Cloudflare's edge saw this connection. Not a device location.

The announced prefix that covers this address and the ASN that originates it.

Which named sources answered for this record. It is not a risk level.

A role is a network type, not a finding. Open the ASN record for the operator's ranges; a wrong role is corrected by the source named here.

For an exit you bought, compare this with the seller's claim. Not being found in covered sources does not prove a direct connection.

If a source names this address, review that source and follow its own removal process. No record here is not a clean bill.

If a service places this address elsewhere, compare which sources disagree; a correction goes to the database that is wrong.

Open the prefix record for the covering range, or the ASN record for the origin network. A routing conflict is not a verdict on user behaviour.

Retry later for a timeout. Licence-withheld and uncovered sources do not change on retry, and an abstention is never a "no".