Registration country and usage country are two different claims.

Do registration country and location estimates agree?

Where both are returned, compare the administrative registration country with each named location estimate. Agreement describes the records; disagreement identifies a question to investigate. Neither determines a device’s physical presence.

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.

"Native IP" is a phrase that arrived through proxy marketing, and it usually goes undefined by the people selling it. In this tool it means comparing two returned records, not applying a universal certification standard.

Two different claims about one address

Country appears more than once in an IP record, and the values come from different places. IPJury keeps them apart because they answer different questions.

Registration country

From the regional internet registry's delegated statistics — the administrative record of which economy a block was allocated to. It is administrative context; the returned field may be absent or may lag an update.

Usage-location estimate

A geolocation dataset's inference about where the address is actually used, built from operator declarations, routing behavior, latency, and observed traffic. It describes deployment, and it can update without any registry change.

Current edge context

What the serving network observed for the request in front of it. Useful, narrow, and relevant only to a live connection.

When registration and usage agree, the axis reports agreement. When they diverge, IPJury shows the divergence with both sources named rather than picking a winner.

Why the distinction is worth checking

Two audiences care intensely. Cross-border sellers and account operators find that a mismatch between where an address is registered and where it presents can add verification friction at signup or review. Streaming audiences encounter the same divergence because regional licensing is enforced against location estimates, and those estimates are exactly the value that a relocated block puts in question.

The useful framing is friction, not access. A mismatch is a fact about records that some systems weigh. It is not a lever, and no result here predicts what any service will do.

Mismatch has legitimate causes

A divergence is a prompt to look closer, not a verdict of deception. Possible explanations include:

• Multinational allocation. A carrier or enterprise registered in one economy routinely deploys blocks across many. The registry records the holder, not the deployment.
• Anycast. One prefix announced from many locations at once has a single registry country and no single usage country. For CDN and resolver infrastructure this is the design, not an anomaly.
• Transfers and re-announcement. Address space is bought, leased, and reassigned. A block that served one country for a decade can serve another the day after a transfer, and datasets carry the old association for a while.
• Geofeed corrections. Operators publish their own location data in the RFC 8805 geofeed format precisely to correct geolocation guesses. A recent geofeed can legitimately move an address away from where the registry sits.
• Dataset lag. Independent geolocation providers refresh on different cycles, so two of them can disagree on a re-deployed block for weeks. Update timing is one possible explanation, not something a mismatch alone proves.

What a mismatch does and does not establish

It establishes that two records about one address point at different countries, sourced and dated. That is genuinely useful: it is the concrete question to ask a seller who advertised a country, and it explains why one tool shows you a flag another does not.

It does not establish physical position, tunnelling, dishonesty, or how a destination will classify the address. Geolocation is an estimate, and each source covers different levels. A country-only source does not confirm a city or postcode. IPJury reports the country comparison and stops there, because that is where the evidence stops.