> For the complete documentation index, see [llms.txt](https://docs.ipcheck.ing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipcheck.ing/knowledge-base/connection-tools/ip-information.md). # IP Information Your IP cards and the Query IP tool: geolocation, ASN, and organization data for any address. ## What it does **IP Infos** is the first section of the dashboard. It answers one question: what does the internet see when you connect? It works in two stages. First, MyIP asks several independent servers "what is my address?" — each answer becomes one card. Then it looks up geolocation and network data for every address it found. The **Query IP** tool does the same lookup for any address you type in, not just your own. ## How to run it The IP cards run automatically every time the page loads. You do not need to click anything. * To re-check a single card, click the **Refresh IP Card** button in that card's header. * To save a card as a picture, click **Save as image**. * To copy an address, click the copy icon next to it. For a manual lookup, click the round search button in the bottom-right corner (**Query IP Address**), type a public IPv4 or IPv6 address, and press Enter. Private and reserved addresses — `192.168.1.1`, `10.0.0.1`, `127.0.0.1` — have no geolocation to look up, so the tool says so straight away rather than querying the data sources. Clear the box and the message goes away. The Query IP result carries the same small row buttons as your own cards — the map on the **City** row and the activity button on the **Region** row included. Inside the dialog they expand inline under the fields instead of opening another window, and only one is open at a time: opening the map closes the activity view and vice versa, just like the ASN panels below them. ## Reading your results Each card is headed by its **IP Source** — the server that reported the address. MyIP ships with six: | Card | Reports | | ------------------ | --------------------------------------------------- | | IPCheck.ing IPv4 | Your IPv4 address | | IPCheck.ing IPv6 | Your IPv6 address | | Cloudflare IPv4 | Your IPv4 address, as seen by Cloudflare | | Cloudflare IPv6 | Your IPv6 address, as seen by Cloudflare | | CN Source | Your address, as seen by a server in mainland China | | IPCheck.ing IPv6/4 | Whichever version your browser preferred | By default only the first two cards are shown. You can switch to 4 or 6 under **Preferences → Servers To Check IPs**. Below the address, each card lists: * **Region** — the country or territory, with its flag. Click the small activity icon next to it to see when that country is typically online, hour by hour — see **Online activity pattern** below. * **State** — the province or state, when the data source has one. * **City** — the city. Click the small map icon next to it to open a map view with the **Coordinates**. * **Time Zone** — the zone that city falls in, with its current UTC offset. On a computer, hover the value to see the local time there. Absent when the source could not place the address precisely enough. * **ISP** — the organization that owns the address, usually your provider. * **ASN** — the network number this address belongs to. See [What Is an ASN?](/knowledge-base/concepts/what-is-an-asn.md). The three small buttons on the ASN row open **AS Details**, **ASN History**, and **ASN Connectivity**, covered in [ASN Info & Upstream Topology](/knowledge-base/lookup-privacy/asn-info.md). ### Online activity pattern The small button next to the **Region** value — hover it to see its name, **Show Online Activity Pattern** — opens a dialog titled with the country's flag and name. Inside is a heatmap of a typical week: 7 rows for the days, Monday first, and 24 columns for the hours. The darker a cell, the more internet traffic that country carries at that hour. The data is Cloudflare Radar's HTTP request volume for the country, aggregated by hour over the past 28 days — so every cell averages about four samples, and the picture is the country's routine rather than any single day. A few things to keep in mind: * **It describes the whole country, not you.** Like the AS Details bars, these are aggregate measurements — the daily rhythm of everyone in that country or region, nothing about the person behind the IP. * **Shades are relative within one country.** The scale runs from that country's own quietest hour to its busiest, so you cannot compare darkness across countries — a dark cell in a small country can be less traffic than a pale cell in a large one. * **Human Only** is on by default, so the pattern follows waking hours. Switch it off to include bot and automated traffic — comparing the two views shows which hours belong to machines. * **Hours are shown in the IP's own time zone**, so "morning" on the axis means morning in that country. If the geolocation source reports no time zone, your browser's local zone is used instead; either way, the offset applied is printed in the bottom-right corner as `UTC±HH:MM`. The lookup consumes no account quota and needs no sign-in. And despite the similar name, this is not [Earth Online](/knowledge-base/getting-started/earth-online.md)'s live visitor heatmap — that map shows where this site's current visitors are; this one shows when a whole country tends to be online. {% hint style="info" %} The activity button relies on Cloudflare Radar — the same data, and the same key, as **Show AS Details**. On a self-hosted deployment without a Cloudflare API key configured by the operator, both buttons are hidden. It also needs a country to ask about, so it does not appear when the card has no Region. {% endhint %} ### Extra fields from the IPCheck.ing source When your geolocation source is set to **IPCheck.ing** and you are signed in, four more fields appear: **Type** (Residential, Wireless, Business or Hosting), **Proxy**, **ASN-Geo match**, and **IP Quality** as a score out of 100. Signed out, these show as `***` with the note *"To avoid abuse, sign in to view the following information"*. These fields carry a free monthly quota that counts **unique IP addresses**, not lookups — re-checking an address you have already queried this month is always free and keeps working even past the limit. Once the month's allowance of new addresses is used, the fields show a *"Monthly quota for new IPs used up"* notice with a **View usage** link instead; the rest of the card is unaffected. The **Query IP** tool draws on the same pool, so looking up many unfamiliar addresses is what actually consumes it. See [Free Monthly Quotas](/knowledge-base/getting-started/free-quotas.md). ### When a card fails | What you see | What it means | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | `Fetch Failed or No IPv4 Address` | No IPv4 address was found, or every IPv4 source failed | | `Fetch Failed or No IPv6 Address` | Your network has no IPv6, which is still very common | | Card shows grey placeholder bars | The lookup is still running | | `Unable to fetch information for this IP...` | Query IP only: the address is well-formed and public, but no data source knows it | | `Private, loopback and other reserved addresses...` | Query IP only: the address is not publicly routable, so there is no geolocation for it | | `Failed to load online activity.` | The activity heatmap only: Cloudflare Radar has no usable series for that country, or the request failed | An empty IPv6 card on its own is not a problem. Many home connections are still IPv4-only. See [IPv4 vs IPv6](/knowledge-base/concepts/ipv4-vs-ipv6.md). A card that consistently fails on one particular network usually means that network cannot reach the source's server — a blocked domain or filtering DNS. The other cards cover for it; that is why MyIP queries several sources. More: [Site Troubleshooting](/knowledge-base/faq/site-troubleshooting.md) ## Why the cards disagree Two things can differ between cards, and they mean very different things. {% hint style="info" %} **Different addresses** across cards usually means your traffic takes different paths — a proxy with split rules, an IPv4/IPv6 mismatch, or a VPN that only covers some destinations. See [Why Do Sites See a Different IP?](/knowledge-base/diagnose/why-do-sites-see-a-different-ip.md) **The same address but a different city** means the geolocation databases disagree. That is normal. See [GeoIP: How IP Geolocation Works](/knowledge-base/concepts/geoip-explained.md) {% endhint %} ### Switching geolocation sources Under **Preferences → IP Geolocation Database** you can choose which database supplies the location fields: IPCheck.ing · IPinfo.io · IP-API.com · IPAPI.is · IP2Location.io · IP.sb · MaxMind All cards are queried again against your choice. If the selected source is unavailable, MyIP falls through to the next one automatically — a notice tells you which source answered instead, and your saved choice stays put. Comparing two or three sources is the fastest way to tell whether a wrong city is a database error or a real change in routing. ## What to do next * Location looks wrong? Read [Why Is My IP Location Wrong?](/knowledge-base/diagnose/why-is-my-ip-location-wrong.md) * Address looks like your provider's, not your VPN's? Read [Is My VPN or Proxy Working?](/knowledge-base/diagnose/is-my-vpn-working.md) * Address starts with `100.64`? Read [Am I Behind CGNAT?](/knowledge-base/diagnose/am-i-behind-cgnat.md) * Want a field-by-field walkthrough? Read [Reading Your IP Cards](/knowledge-base/getting-started/reading-your-ip-cards.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ipcheck.ing/knowledge-base/connection-tools/ip-information.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.