Verify the exit you were sold, against sources you can name.

EDGE: READY
More options
What are you checking?
EXAMPLE Checked static example Cache n/a NOT LIVE
IP

8.8.8.8

EXAMPLERUN A LIVE CHECK
ASN
AS15169 · Google LLCgoogle.com
LOCATION
US · California, Mountain View
IPBot
🇺🇸 US · California, Mountain View
IPinfo
🇺🇸 US · AS15169
GeoLite2
🇺🇸 US
DB-IP
🇺🇸 US · California, Mountain View
Bright Data
🇺🇸 US · California, Mountain View
ROUTE
ANNOUNCED 8.8.8.0/24
IP TYPE
PUBLIC INTERNET INFRASTRUCTURE
Not assessedIPJURY SCOREEXPERIMENTAL · NOT A PROBABILITY IPJURY VERDICT EXAMPLE

Run a live check for an evidence verdict and experimental interpretation.

Why this result · full calculation

Run a live check. The example is not scored.

    Evidence confidence is not prediction accuracy. A provisional range spans policy outcomes for unanswered questions; it is not a probability interval.

    OPEN FULL EVIDENCE REPORT

    JURY READY

    Enter an address, or check your own connection · the example below is replaced in place

    FULL REPORT IDENTITY · SOURCE MATRIX · SIX-AXIS VERDICT · EVIDENCE RECORD
    EVIDENCE SNAPSHOTSEPARATE AXES · NOT A SCORE
    ANONYMITY
    No direct anonymity evidence observed
    ABUSE EVIDENCE
    No abuse evidence in covered sources
    COVERAGE
    6/7 jurors responded
    01

    IDENTITY

    COORDINATES
    not loaded in static example
    ROUTING
    ROUTE ORIGIN OBSERVED
    PREFIX
    8.8.8.0/24
    TIMEZONE
    America/Los_Angeles
    REVERSE DNS
    not loaded in static example
    STACK
    IPv4
    RANGE
    8.8.8.0 – 8.8.8.255
    REGISTRY
    not loaded in static example
    02

    SOURCE MATRIX

    4 location sources agree at country level · — not covered · W/H withheld

    SIGNALIPBotIPinfoGeoLite2DB-IPIPtoASN
    COUNTRYUSUSUSUS
    CITYCalifornia, Mountain ViewCalifornia, Mountain View
    ASNAS15169AS15169AS15169AS15169
    PROXYNO
    VPNW/H
    TORNO
    HOSTINGNO
    ABUSENO
    03

    SIX-AXIS VERDICT

    NETWORK ROLEHIGH
    Public internet infrastructure

    Service role · anycast context · operator identity

    ANONYMITYMEDIUM
    No direct anonymity evidence observed

    No proxy, VPN, or Tor finding in covered fields

    ABUSE EVIDENCEMEDIUM
    No abuse evidence in covered sources

    This means “not observed,” never “clean”

    GEO CONTEXTLOW
    US · single geolocation estimate

    Country-level context; physical location not proven

    ROUTINGHIGH
    Route origin observed · RPKI state withheld by licence

    Origin ASN · announced prefix · route-origin conflict

    COVERAGEMEDIUM
    6/7 jurors responded

    Named jurors · lineage families · abstentions visible

    04

    EVIDENCE RECORD

    JURORAXISCLAIMCONF.STATUS
    Network identityIPBot networknetwork roleAS15169 · Google LLCHIGHRESPONDED
    Operator and role profileIPBot classificationnetwork rolepublic infrastructureHIGHRESPONDED
    Anonymity signalsIPBot classificationanonymityno direct proxy/VPN/Tor evidenceMEDIUMRESPONDED
    Direct threat evidenceIPBot evidenceabuseno direct record in covered evidenceMEDIUMRESPONDED
    REPORT ipjury.com/check/8.8.8.8 EXPERIMENTAL INDEX
    TERMINAL curl ipjury.com/8.8.8.8 irm ipjury.com/8.8.8.8
    IPJURY.COM · EVIDENCE, NOT AN ENTERTAINMENT SCORE

    IPJury uses the IP2Location LITE database for IP geolocation. This product includes GeoLite Data created by MaxMind, available from https://www.maxmind.com. IP Geolocation by DB-IP. Full source credits: source register.

    05

    THE PROXY VERIFICATION CHECKLIST

    Does the exit address support the description I bought?

    Check the actual exit rather than the gateway, compare source-reported role and location with the seller’s words, and export the dated differences. An inconsistency supports a specific question, not a certificate of fraud or suitability.

    Evidence scope and register licence-review dates — not live lookup dates
    SourceRegister review
    IPBot Network Identity
    IP2Location LITE DB11 (via IPBot)
    IPBot Classification Evidence

    Source availability depends on the current deployment and each returned record. These review dates do not establish when a particular IP was observed. Method axis-scope-2026-09-15 · Score ipjury-score-v3.

    You paid for an exit described as residential. Compare that description with the named network and location evidence, recording the exact claim you are checking.

    Check the exit, not the endpoint

    The address you connect to is often a gateway. The one that matters is the address traffic leaves from — the exit the destination sees. Route a request through the proxy, check the address it reports, then read the record in this order.

    1. Whose ASN announces it? A consumer ISP or mobile carrier announcing the address is consistent with a residential or mobile sale. A hosting label is a reason to ask for clarification. Neither label alone certifies the exit path or exclusive use.
    2. Does the registration country match the geolocated country? Registry allocation and usage estimate are two separate claims, and IPJury shows them separately. A mismatch is a question to put to the seller, not proof of fraud — allocations legitimately cross borders.
    3. What does the PTR hostname suggest? Operator-controlled naming carrying pool, dsl, cable, or mobile language points one way; naming carrying vps, server, cloud, or a hosting brand points another. PTR is a weak clue and IPJury labels it as one. It corroborates the ASN reading; it does not override it.
    4. Read role, anonymity, and abuse as three answers. A residential role does not mean no anonymity evidence. An anonymity finding does not mean an abuse record exists. An abuse record does not tell you the role. Collapsing the three into "is it good" is exactly how a seller's claim survives a check it should have failed.
    5. Read coverage and abstentions before you conclude anything. If half the jurors abstained, a quiet record is a thin record. "No evidence in covered sources" is not "clean" — it means the sources that answered returned no finding.

    When sources disagree, that is the finding

    Different network descriptions can reflect different scopes or collection methods; the report names its own returned claims. A network can lease space to a hosting tenant while remaining a consumer ISP on paper. A residential-proxy operator can sit inside genuine subscriber space. One dataset weights the allocation record, another weights observed service behavior, and they arrive at different labels from the same address.

    IPJury does not average that away. It shows which juror said what, and on what basis. For a purchase decision, split evidence beats false unanimity: an exit described as hosting by a covered source gives you a specific question, but does not establish how a destination will classify it.

    Turn the check into an artifact

    A screenshot of a number proves nothing to a seller, and they know it. A record that names its sources, states each source's basis, and can be re-run by the other side is a different kind of message. Export the verdict as text, Markdown, or BBCode for a ticket or forum thread, or as a PNG evidence card for a chat window. Include the address and checked time so the seller can investigate. A new lookup may return newer evidence and is not guaranteed to reproduce the earlier result.

    Two caveats worth stating when you send it. IP data moves, so a check is evidence about a moment rather than a permanent property. And no record obliges a seller or a platform to agree with it.

    Why a neutral record carries weight

    Evaluate the record by its sources, dates, scope and exclusions, rather than by who gives the most reassuring number. This lookup does not purchase a proxy or certify the seller’s claims. It reports what named sources returned — including when they contradict each other, and when they say nothing at all.

    06

    A NUMBER NEEDS ITS EVIDENCE

    IPJury keeps network type, anonymity, abuse, location, routing and coverage separate. Its optional experimental index explains a published policy over those facts; it never replaces the named evidence verdict or conceals missing information.

    MYSTERY SCORE MODEL
    83/100

    What does 83 measure? Who supplied it? Is hosting being treated as abuse? Did one heuristic outweigh a direct record? A number cannot tell you that two of its sources flatly contradicted each other.

    • Cross-axis averaging
    • Hidden source lineage
    • Missing source treated as “false”
    • Disagreement averaged away
    • Platform outcome implied
    EVIDENCE + EXPLAINED INTERPRETATION
    BANDDISPUTED RULEsource-conflict ROLEhosting ANONYMITYno direct evidence ABUSEno record observed GEOcountry disputed ROUTINGorigin observed COVERAGE6/7 responded

    One rule read one axis and named the state. The axes it did not read stay beside it. “Disputed” and “too little coverage to say” are answers a single number cannot express.

    07

    THE FIVE RULES OF EVIDENCE

    [ READ FULL METHOD ]
    1. 01

      Vote only on the same axis

      A proxy flag, an abuse report, a hosting role, and a city estimate are not interchangeable votes.

    2. 02

      Direct evidence outranks a prior

      An exact-IP record is different from an inference based on the ASN, prefix, or network category.

    3. 03

      Deduplicate source lineage

      Three websites backed by one upstream database do not become three independent evidence families.

    4. 04

      Let jurors abstain

      Timeout, no IPv6 coverage, disabled license, or missing record is shown—not silently converted to “no.”

    5. 05

      Explain dissent

      CGNAT, anycast, reassignment, data age, and route context can all produce legitimate disagreement.

    09

    QUESTIONS THE SCORE CANNOT ANSWER

    How do I check whether the residential proxy I bought is really residential?

    Check the exit address, not just the gateway. Compare the returned network role and location sources with the seller's claim. Those records can raise a specific question, but do not certify a household exit, exclusive use or every proxy class.

    The seller advertised one country and the check shows another. Who is wrong?

    Possibly neither. Registry allocation country and geolocation estimate are separate claims and can legitimately differ, so the mismatch is the question to put to the seller rather than proof of anything.

    Can I send the evidence record back to the seller?

    Yes. Copy text, Markdown or BBCode, or download a PNG with the sources and checked time. A fresh lookup may return newer evidence; the current lookup link is not a permanent copy of the original result.

    Does IPJury sell proxies or earn a commission on the ones it checks?

    No. IPJury sells nothing, carries no affiliate links, and has no pool to steer you toward, which is the whole point of using it to check a seller's claim.

    IPJURY // RECORD

    Methodology