# What is my IP address? See your public IP address and everything a website can read about you: location, ISP, ASN, request headers, TLS, WebRTC leaks, fingerprint and time zone. Nothing about you is logged, no cookies. Works with curl. ## Short answer Your public IP address is the one at the top of this page, and every website you open receives it with each request. An IPv4 address is 32 bits long, about 4.3 billion possible values (RFC 791), and an IPv6 address 128 bits (RFC 4291); the place shown beside it is an IP-geolocation estimate for the network, usually at city or region level and never a street address. ### Method The server reads the address of the connection that reached Cloudflare (the `CF-Connecting-IP` header) and the connection data Cloudflare attaches to each request: country, region and city from its IP database, the network's AS number and name, the data center, and the TLS and HTTP versions. Those values are shown as received. A browser reaches a site over one protocol at a time, usually IPv6 when both work (Happy Eyeballs, RFC 8305), so the IPv4 and IPv6 lines come from two extra requests your browser makes in parallel to `ipv4.icanhazip.com`, which has only an IPv4 address, and `ipv6.icanhazip.com`, which has only IPv6; WebRTC's public addresses are compared with them as a second reference. Under each line is that address's location, labelled with its source: for the address this page's own request came from, Cloudflare's data, the same as the line above; for the other one, our server looks it up in DB-IP's free IP to City Lite and ASN Lite databases (CC BY 4.0, refreshed monthly). The WebRTC, time zone, language and fingerprint checks run as scripts in your browser and are compared with the server's view on the page; their results are never sent back. ### Worked example ``` $ curl iseeu.cc 192.0.2.1 $ curl -6 iseeu.cc 2001:db8::1 $ curl -s "iseeu.cc/geo?format=text" | head -3 ip: 192.0.2.1 country: US countryName: United States ``` 192.0.2.1 and 2001:db8::1 come from blocks reserved for documentation (RFC 5737, RFC 3849); your own request shows your own address, and `curl -4` or `curl -6` picks the protocol. The first answer is the address and a newline, nothing else, so `$(curl -s iseeu.cc)` can be used directly in a shell script. ### Limits - Behind a VPN, a proxy, Tor or carrier-grade NAT (the shared 100.64.0.0/10 range, RFC 6598), the address shown is an exit you share with others, not your device. - IP geolocation estimates where a network is registered or routed; mobile and satellite connections are often placed far from where you are. - IPv6 devices usually rotate temporary addresses (RFC 8981), so the address can change from day to day while the first 64 bits, your network, stay the same. - The IPv6 line needs a working IPv6 route from your device; if the lookup does not answer within 5 seconds, the line says IPv6 was not detected. That is common and not an error. - The two locations come from separately built databases, Cloudflare's and DB-IP's, so they can disagree even for addresses on the same network; each line names its source. ### Sources - [RFC 791: Internet Protocol](https://www.rfc-editor.org/rfc/rfc791): IPv4 addresses are 32 bits. - [RFC 4291: IP Version 6 Addressing Architecture](https://www.rfc-editor.org/rfc/rfc4291): IPv6 addresses are 128-bit identifiers. - [RFC 8305: Happy Eyeballs Version 2](https://www.rfc-editor.org/rfc/rfc8305): why a browser uses one protocol per connection and usually prefers IPv6. - [RFC 5737: IPv4 Address Blocks Reserved for Documentation](https://www.rfc-editor.org/rfc/rfc5737): 192.0.2.0/24 is for examples. - [RFC 3849: IPv6 Address Prefix Reserved for Documentation](https://www.rfc-editor.org/rfc/rfc3849): 2001:db8::/32 is for examples. - [RFC 6598: Shared Address Space](https://www.rfc-editor.org/rfc/rfc6598): 100.64.0.0/10 for carrier-grade NAT. - [RFC 8981: Temporary Address Extensions for IPv6](https://www.rfc-editor.org/rfc/rfc8981): rotating IPv6 interface identifiers. - [DB-IP Lite databases](https://db-ip.com/db/lite.php): IP to City Lite and IP to ASN Lite, monthly, CC BY 4.0; the source of the second address's location. - [Cloudflare Workers: Request](https://developers.cloudflare.com/workers/runtime-apis/request/): the location, network and TLS fields this page reads. - [Major Hayden: A new future for icanhazip](https://major.io/p/a-new-future-for-icanhazip/): icanhazip.com is owned and run by Cloudflare. ## What your IP address tells a website Your public IP address is the return address on every request your device makes. A website cannot send you a page without it, so every site you open receives it automatically — no permission prompt, no cookie, no script. On its own the number looks meaningless, but it is the key to three lookups that any site can do in a millisecond: which network owns the address (your **ISP or organization** and its **ASN**), roughly where that network hands traffic to the internet (**country, region, city**), and what kind of network it is (a home broadband line, a mobile carrier, a university, or a cloud server). That is why streaming services know which country's catalogue to show you, why a bank may ask for extra verification when you log in from abroad, and why a shop can guess your currency before you choose it. None of it requires your name, and none of it is precise: the address identifies a connection, not a person. ## How to use it 1. Open the page. Your public IP address appears at the top in large type, with the IP version, network name and approximate place on the line below. Press **Copy IP** to put the address on your clipboard. 2. Read the three counters underneath: how many details any website can read, how many of them you could change or hide, and how many inconsistencies a site could notice. 3. Go through the cards. Every row carries a chip, *Can change*, *Partly* or *Can't*, so you can see which values follow your network and which are tied to your device. 4. Give the browser checks a few seconds. The WebRTC, fingerprint and time cards are filled in by scripts running in your tab after the page loads. 5. Read **What a website could infer**. Each line compares two signals, such as browser time zone against IP location, and says whether they agree. 6. At the bottom, review **Request headers**. When the extra list is shown, expand it to see the headers Cloudflare added on the way to us. With JavaScript switched off, your IP and network details still appear; only the in-browser checks are skipped. ## Use cases - **Confirming a VPN is on.** Connect, reload, and check that country, ISP and ASN all changed, and that the WebRTC card does not report a second public address. - **Getting added to an allowlist.** An administrator asks for your address before opening a firewall or admin panel to you. Copy it and pass on the IP version too: an IPv6 visitor will not match a rule that only lists IPv4 ranges. - **Explaining a wrong country or currency.** If a shop or streaming service treats you as being somewhere else, the Location card shows what geolocation data says about your address, so you can tell whether the address is the cause rather than your settings. - **Diagnosing rejected two-factor codes.** The Time & language card shows how far your device clock is from our server. Time-based codes start failing when the clock drifts too far. - **Understanding an extra login challenge.** The inference list shows the contradictions a bank or anti-fraud system could act on: a time zone from another region, a language from another country, or an address on a hosting network. ## How accurate is IP location? IP geolocation is a database guess, not GPS. Providers publish where their address blocks are routed, and commercial databases refine that with measurements and user reports. Country is right almost every time. Region is usually right. City is often the nearest large city where your provider has equipment, which can be 20 to 100 miles from where you actually are; mobile networks are the least accurate because many towers share a few gateways. The coordinates above are the centre of that guessed area, rounded — they will never point at your front door. ## What you can change, and what you can't Every row on this page carries a label. Things marked *Can change* follow your network or your settings: connect through a VPN, Tor or a different Wi-Fi network and your IP, location, ISP and ASN all change together. Your time zone and language are settings you control. Things marked *Partly* can be altered only with side effects — a User-Agent switcher edits one header while your browser's other signals keep telling the truth. Things marked *Can't* come from your browser's code or your hardware: the TLS handshake your browser performs, its rendering quirks, your graphics card. A VPN does nothing for those, which is why tracking companies and bot-detection services lean on them. The most useful section is **What a website could infer**. Real detection systems rarely judge one signal on its own; they look for contradictions. A browser set to Pacific time with an IP address in Frankfurt, an English-US language preference with a Brazilian IP, a WebRTC address that differs from the one your page was loaded from, or a Chrome User-Agent that disagrees with Chrome's own Client Hints — each of these is normal in isolation and suspicious in combination. We show you the same comparisons, in plain language, without a scary score. ## Use iseeu.cc from the command line The home page doubles as a plain-text endpoint. Anything that is not a browser gets one line back, which makes it handy in scripts and on servers: ``` curl iseeu.cc # your IP, e.g. 192.0.2.1 (example address) curl iseeu.cc/json # everything on this page, as JSON curl iseeu.cc/geo # location and network only curl "iseeu.cc/ua?format=text" # just your User-Agent Invoke-RestMethod iseeu.cc # PowerShell ``` There is no API key and no sign-up. The limit is 60 requests per minute per IP address, which is plenty for checking a VPN or a CI runner. The full reference, including field descriptions and an OpenAPI file, is on the [API & MCP page](https://iseeu.cc/api/). ## For AI agents iseeu.cc also runs a remote [MCP server](https://iseeu.cc/api/#mcp) at `https://iseeu.cc/mcp` with five read-only tools: `whoami` (the caller's IP, location, network and TLS), `check_headers` (which common bot-detection traits a header set shows), `parse_ua` (a User-Agent parser that knows AI crawlers), `dns_lookup` (DNS records over DNS-over-HTTPS) and `rdap_lookup` (registration data for a domain, IP address or AS number). It needs no authentication. One honest caveat: when an AI assistant runs in the cloud, these tools see the assistant provider's servers, not you. ## How iseeu.cc handles your data Everything on this page is computed for your single request and then discarded. We do not keep request logs, we have no database of visitors, and we set no cookies. Page views are counted with Cloudflare Web Analytics, which is cookieless and only gives us totals. The fingerprint and WebRTC checks run entirely in your browser; their results are never uploaded. When your network has both IPv4 and IPv6, the page sends the second address to our server once, to look up its location in DB-IP's database ([IP Geolocation by DB-IP](https://db-ip.com/)); that lookup is not logged either. To decide whether the site is worth running, we count how many times each endpoint is used — a number per endpoint, with no IP address, no browser details and no headers attached. The [privacy page](https://iseeu.cc/privacy/) lists exactly what our host, Cloudflare, processes on our behalf. ## Frequently asked questions **Is the location shown here my exact address?** No. It is an estimate of where your internet provider's equipment is, taken from an IP geolocation database. It is usually right about the country, often right about the region and frequently off by tens of miles at city level. **Why is my IP address different from yesterday?** Most home and mobile providers assign addresses dynamically, so your public IP changes when your router reconnects, when your phone switches towers, or when your provider rotates its pool. **Does iseeu.cc store my IP address?** No. The page is computed for your request and discarded. We do not run request logs, a database or cookies. We only count how many times each endpoint is used, without any IP address or browser detail, and count page views with a cookieless analytics service run by our host. **How do I get my IP address from the command line?** Run `curl iseeu.cc`. It prints your public IP and nothing else. `curl iseeu.cc/json` returns everything on this page as JSON. **Will a VPN hide everything on this page?** No. A VPN changes your IP address and everything derived from it, such as location and ISP. It does not change your browser, your fonts, your graphics card, your language or your time zone, which websites can still read. **Why does the page say my time zone does not match my IP?** Your browser reports the time zone your device is set to, while your IP address points somewhere else. That happens when you travel or use a VPN in another region, and some websites use the mismatch to detect VPN users. **Is it safe to show my IP address to websites?** Every website you visit already receives it; the internet cannot deliver a response without it. An IP address reveals your provider and rough area, not your name or street address. iseeu.cc is an informational tool. IP-based location and network names come from Cloudflare's IP data and can be wrong; the consistency checks are heuristics, not proof that you are or are not using a VPN. Nothing on this page is security, legal or privacy advice. ## What websites see about you - [What is my IP](https://iseeu.cc/): Your IP address, location, network, request headers, TLS and leak checks on one page. - [WebRTC leak test](https://iseeu.cc/webrtc-leak-test/): Check whether WebRTC exposes an IP address your VPN should be hiding. - [User agent checker](https://iseeu.cc/what-is-my-user-agent/): See and parse the User-Agent and Client Hints your browser sends. - [Browser fingerprint test](https://iseeu.cc/browser-fingerprint-test/): The signals that can recognise your browser without cookies. - [Browser feature detection](https://iseeu.cc/browser-features/): About 60 web platform features, tested live in your browser. - [Find your IP on a phone](https://iseeu.cc/find-ip-address-on-phone/): Where iPhone, Pixel, Samsung, Motorola and Xiaomi show the local IP, and how to see the public one. ## DNS and domains - [DNS lookup](https://iseeu.cc/dns-lookup/): A, AAAA, MX, TXT, NS, CNAME, CAA and SOA records over DNS-over-HTTPS. - [WHOIS / RDAP lookup](https://iseeu.cc/whois/): Registration data for domains, IP addresses and AS numbers. - [Punycode converter](https://iseeu.cc/punycode/): Convert internationalized domain names to and from their xn-- form. ## Network and addressing - [Subnet calculator](https://iseeu.cc/subnet-calculator/): IPv4 and IPv6 CIDR ranges, masks, host counts and subnet splits. - [MAC address lookup](https://iseeu.cc/mac-lookup/): Find the organisation behind a MAC address in the IEEE registry. ## Web and email - [Security headers check](https://iseeu.cc/headers-check/): Fetch a URL's response headers and grade HSTS, CSP and the rest. - [Email header analyzer](https://iseeu.cc/email-header-analyzer/): Trace the Received chain and read SPF, DKIM and DMARC results. ## For developers and agents - [API and MCP server](https://iseeu.cc/api/): Plain text, JSON and MCP tools for scripts and AI agents. ## Related tools - [WebRTC leak test](https://iseeu.cc/webrtc-leak-test/): Check whether WebRTC exposes an IP address your VPN should be hiding. - [User agent checker](https://iseeu.cc/what-is-my-user-agent/): See and parse the User-Agent and Client Hints your browser sends. - [Browser fingerprint test](https://iseeu.cc/browser-fingerprint-test/): The signals that can recognise your browser without cookies. - [DNS lookup](https://iseeu.cc/dns-lookup/): A, AAAA, MX, TXT, NS, CNAME, CAA and SOA records over DNS-over-HTTPS. - [WHOIS / RDAP lookup](https://iseeu.cc/whois/): Registration data for domains, IP addresses and AS numbers. [Browse all tools](https://iseeu.cc/tools/) Last updated: 2026-10-11 Source page: https://iseeu.cc/