How IP Context works

IP Context at ipcontext.info is an HTTPS service for public IP inspection: the address your connection presents to servers on the internet, enriched with geolocation estimates, registered organization or ASN context, time zone, an inferred connection class, and browser or operating system hints parsed from your User-Agent. The same payload is exposed as JSON for monitoring, coursework, and application integration.

Service scope

IP Context answers a focused question: What does the open internet plausibly know about this public IP and this HTTP client? It does not scan your LAN, install software, or access credentials. It is suitable for network literacy, consent-based checks of addresses you administer or are permitted to analyze, and structured testing of client IP and header behavior behind proxies.

Endpoints

• Interactive lookup — /
• Quick start — /quickstart
• This guide — /docs
• JSON — GET /json (response type application/json)
• Availability — GET /health (minimal process status)
• About — /about · Privacy — /privacy

What you get

• Public IP — the IPv4 or IPv6 address evaluated for the request (or the address supplied for an allowed lookup).
• Regional context — city, region, and country where available, from commercial or community IP geolocation databases.
• Organization — commonly the ISP, mobile operator, university, or cloud provider associated with the network range.
• Network type — a single inferred label (residential, mobile, datacenter, business, VPN-like, Tor-related, bot-like, or unknown) based on database flags and heuristics.
• Client software hints — operating system and browser family parsed from the User-Agent string.

No account is required for the public lookup experience.

Using the site

Open the home page. Results load for your session automatically. Use the search field and Lookup only for public addresses you are entitled to query. When latitude and longitude are returned, the map link reflects the database centroid, not a verified physical visit.

Corporate VPNs, privacy VPNs, and mobile gateways often terminate in a different city or country than where you are sitting. Interpret type, org, and region together.

Field reference

On-page rows and JSON keys follow the same order: ip, type, os, browser, city, region, country, loc, org, postal, timezone, and optionally original. User-Agent parsing is indicative only. Geolocation is an estimate, not evidence of a person’s location.

Network type

Labels summarize how the address is commonly used in routing and threat-intelligence data. They can change as databases are updated and should not be used as the sole basis for high-stakes decisions.

Accuracy and limits

Country-level results are generally reliable. Finer location can drift for carrier-grade NAT, satellite, anycast, or rapidly reassigned pools. Proxies and VPNs deliberately alter the apparent egress point—expect mismatches between “city” and real-world position in those cases.

JSON API

Example requests against this deployment:

https://ipcontext.info/json
https://ipcontext.info/json?ip=1.1.1.1

Use standard HTTP clients or curl. Responses are always UTF-8 JSON with Content-Type: application/json; you do not need to send Accept or Content-Type on GET (an empty GET is enough).

Querying another address

Append ?ip=<address> to /json or use the web form. Restrict use to infrastructure you own, addresses covered by contract or policy, or other situations where lookup is lawful and proportionate.

Original (proxy)

When the service runs behind a reverse proxy or CDN that forwards the visitor’s address in a trusted header (X-Forwarded-For, X-Real-IP, CF-Connecting-IP, True-Client-IP, and similar), an original field may appear if that value differs from the immediate TCP peer. The field is omitted when there is nothing additional to report.

Health check

GET /health returns a small JSON object suitable for synthetic monitoring. It does not echo client IP data.

Appropriate use

Use IP Context to support troubleshooting, security awareness with clear caveats, and authorized operational work. High-volume automated querying may burden any public endpoint; for production-scale needs, run your own infrastructure or contract a commercial geo provider with an SLA.

← Quick start · About · Privacy · Home