Free What Is My IP Online

What Is My IP: See the Public Address and Browser Details Your Request Reveals

Open this tool and it immediately displays your public IP address — the address other computers on the internet see when your connection reaches them — along with whether that address is IPv4 or IPv6, and the browser, operating system, and device type your own request exposes. There's nothing to type and no button to press first: the page loads, asks the server what address the request arrived from, and shows the answer within a moment.

That server round trip is the one genuinely necessary part of this tool, and it's worth understanding why. A device behind a home router or a company network typically only knows its own private, internal address — something like 192.168.1.42 — because a router or carrier network translates that private address to a shared public one before traffic ever reaches the open internet. Your browser has no way to see what that translated, outward-facing address actually is; only something on the other side of that translation, like this site's own server, can see the address your request actually arrived from and report it back to you. This effect is especially pronounced on mobile networks, where carrier-grade NAT commonly places many different customers' phones behind a shared, limited pool of public addresses, making the server-side view the only reliable source for what a given connection's outward-facing address actually is at any moment. That's the entire reason this particular tool needs a server round trip while a purely mathematical tool doesn't: the answer depends on how the network in between routed your specific request, not on a calculation your own device could finish by itself.

How This Tool Reports Your Address

1. The moment the page loads, it sends a request to this site's own reporting endpoint, and a "Detecting…" label appears while that round trip completes.
2. Once the server replies, your public IP address is displayed in large text, along with a note on whether it was read as IPv4 or IPv6.
3. Click the displayed address at any time to copy it to your clipboard — a small confirmation replaces the "click to copy" hint for a couple of seconds afterward.
4. Below the main address, a details panel lists the IP version, whether the address is flagged public or private/internal, your browser name and version, your operating system and version, and a device description.
5. The device field reads "Desktop / laptop (no mobile signature detected)" unless the parsed User-Agent string specifically indicates a phone or tablet, in which case the detected vendor, model, and device type appear instead.
6. Press the Refresh button to run the whole check again — useful after switching networks, reconnecting a VPN, or simply confirming the address hasn't changed since the page first loaded.

Everything shown comes from that single request: the server reads the address the connection arrived from and the User-Agent header the browser sent along with it, hands both values to the reporting logic, and returns the result — nothing about your visit is retained afterward, and nothing beyond that one exchange is required to produce the answer.

Why People Look Up Their Own IP Address

• Configuring remote access or port forwarding. Setting up a home security camera, a game server, or remote desktop access from outside your own network usually starts with knowing the public address that traffic needs to be directed toward.
• Confirming a VPN or proxy is actually active. If a VPN connection is supposed to be routing your traffic through a different address, checking what a site reports before and after connecting is a quick, direct way to confirm it's working rather than trusting the app's own connected indicator.
• Troubleshooting a "your IP has been blocked" message. Support teams and IT departments often need the exact address you're connecting from to look up why access was denied or to add an allow-list entry.
• Verifying that a network change took effect. After restarting a router, switching ISPs, or reconnecting to a different Wi-Fi network, confirming the public address actually changed (or didn't) helps rule out one possible cause of a connectivity issue, before you spend time chasing a more complicated explanation.
• Checking what a server-side script or automation sees. Anything that calls out to external services from a fixed server — a scheduled job, a webhook handler, a small VPS — sometimes needs to confirm exactly which outbound address that traffic is using, particularly when a remote service needs to allow-list it.
• Setting up an IP allow-list for a database or admin panel. Restricting access to an administrative tool or a database console to a specific set of addresses starts with knowing the exact public address a particular connection is currently using, before that address ever gets typed into the allow-list.

What This Tool Does and Doesn't Report

Field	Reported	Notes
Public IP address	Yes	The address your request actually arrived from, as seen by the server
IP version	Yes	Whether the address is IPv4 or IPv6
Public vs. private/internal flag	Yes	Rarely shows private in normal use — mainly relevant if a request arrives through an internal proxy layer
Browser and version	Yes	Parsed from the User-Agent header your browser sent with this specific request
Operating system and version	Yes	Also parsed from that same User-Agent header — subject to the same version-freezing modern browsers apply for privacy
Device type	Yes	Reported only when the User-Agent string itself carries a mobile or tablet signature
City, region, or country	No	This tool performs no IP geolocation lookup of any kind
ISP or network operator name	No	Not looked up or displayed
Map coordinates	No	No coordinate or mapping data is generated

That last group of rows is deliberate and worth stating plainly: this tool reports only what your own request itself exposes to the server handling it — the address it arrived from and the User-Agent header it carried. It does not cross-reference that address against any geolocation database, so it cannot tell you what city, region, or country an address is associated with, cannot name the internet service provider or network operator behind it, and cannot produce map coordinates. Sites that advertise a "city-level" or "ISP name" IP lookup are running a separate geolocation database lookup against the address — a different kind of tool answering a different question than the one this page answers.

A Note on Accuracy and Privacy

The browser and operating system fields carry the same caveat that applies to any User-Agent-based reporting: the value describes what your browser's request claims about itself, and current-generation browsers increasingly cap or generalize some of that detail as a deliberate privacy measure, so an OS version in particular may appear less specific than the device's actual, exact version. The IP address itself, by contrast, is a direct, unmodified read of the connection's actual source address rather than anything parsed or estimated — it's exactly the address a server would use to reply to your request, not a best guess. Nothing this tool reports is written to a database or kept after the response is sent back to your browser; the check exists to answer the question for you in the moment, not to log or track the result, and refreshing the page simply repeats the same one-off check rather than pulling from any stored history.

Checking Your IP This Way vs. Other Methods

• Your router's admin page. Most home routers display the public address they've been assigned on a status page, which is accurate for that device specifically but requires logging into router administration rather than a quick browser check.
• Command-line tools. Commands like curl ifconfig.me or similar services return a bare IP address from a terminal, which is convenient for scripting but doesn't include the browser or OS context this tool adds automatically.
• A search engine's built-in answer. Searching "what is my ip" often surfaces an inline address directly in search results, which is fast for a single glance but doesn't offer the version, address-type, or device detail shown here.
• This tool's API. A server, script, or scheduled job that needs to confirm its own outbound public address without opening a browser can call this site's metered endpoint directly instead; it reads the address and User-Agent header off that very API call, exactly the way the page above reads them off your browser request, and hands the result back as JSON. Request parameters and the current credit cost for this endpoint are covered in the API documentation.

Does this tool show my exact location, city, or ISP?

No. It reports only the public IP address, IP version, and the browser/OS/device details your request itself reveals — there is no geolocation lookup involved, so no city, region, country, ISP name, or map coordinates are produced or displayed at any point.

Why does this tool need a server, unlike a purely mathematical calculator?

Your device generally only knows its own private, internal network address; the public address visible to the rest of the internet is assigned by a router or carrier network during translation, and only something receiving your request on the other side of that translation — this site's server — can see and report what that address actually is.

Will my IP address ever show up as "private" here?

It can, in unusual setups — for instance if a request reaches this tool through an internal proxy layer that hasn't forwarded the original public address correctly. For a typical home or mobile connection, the address reported here should show as public.

Does refreshing the page always show a different IP address?

Not necessarily. Most home and mobile connections keep the same public address for extended stretches of time, so refreshing typically shows an identical result unless your network itself has changed — a new Wi-Fi connection, a VPN toggled on or off, or your provider reassigning your address.

Why does my address look different from a friend's on the same Wi-Fi?

Devices sharing one router or one office network typically go out to the internet behind that same router's single public IPv4 address, so two devices on the identical connection should normally report matching results here. Seeing a different address usually points to one of you being on a separate network, a mobile carrier connection instead of the shared Wi-Fi, or a VPN routing your traffic through its own address.

Related Network Tools

Pair this address check with the user agent parser to inspect a different browser string than your own current one, field by field. If the address reported here belongs to a range you're mapping out, run it through the IP subnet calculator to see the surrounding network and broadcast addresses, or check the bandwidth calculator to estimate transfer times over the connection this address belongs to.