What Is My IP Address?
Your public IP as our server sees it, with the country it resolves to, its reverse DNS name, and the request headers your client sent.
- Country
- …
- Reverse DNS
- …
- User agent
- …
Request headers your client sent
Headers appear here once the page has loaded.
Cookies, credentials and the delivery network's own routing headers are never shown or stored. Country comes from the network edge's IP geolocation; when it cannot resolve one, this page says so instead of guessing.
What this page can tell you
Every request you make on the web arrives from an IP address, and the server on the other end sees that address. This page reflects it back: the address itself, the country its geolocation record points to, the reverse-DNS name its owner published for it, and the HTTP headers your browser attached to the request. Geolocation is a database lookup, not a measurement, so the country can lag behind a reassignment or differ between databases.
Checking that a proxy is working
Load this page directly and note your IP; then route your traffic through a proxy and load it again. If the proxy is working, the address shown here is the proxy's exit IP, not yours, and the country should match the proxy's advertised location, allowing for differences between geolocation databases. From the command line, the same check is one request:
curl -x "http://user:pass@proxy-host:port" https://node4.io/api/tools/ip
Need the connection string for that command? The proxy connection string builder generates it for curl, Python and Node.js.
Why headers matter too
Your IP is only part of what a server learns about you. The headers your client sends (user agent, accepted languages, encodings, client hints) identify your browser and platform, and automation tools each have recognizable defaults. If you are debugging why a site treats your script differently from your browser, comparing this page's header table between the two is a fast way to see what differs. To decode the user-agent string itself, use the user-agent parser.
More free tools
Request one URL from a datacenter IP and residential IPs at once, and see which of them gets blocked.
What your HTTP client gives away: header order, missing client hints, and contradictions with your user-agent.
Five questions and a straight answer, including when the answer is that you do not need proxies at all.
Derive how many proxies a job needs from volume, deadline, per-IP rate limit, concurrency and retries.
Check a path against a pasted robots.txt and see the exact rule that allowed or disallowed it.
Paste a curl command and read it back as Python, Node.js, Go or PHP, with the flags translated properly.
Turn a proxy host, port and credentials into working curl, Python, Node.js and Scrapy snippets.
Network address, broadcast, usable range and host counts for any CIDR prefix length.
Decode any user-agent string into browser, engine, OS and device, including bots and HTTP libraries.
Need proxies behind your code?
Node4 sells datacenter, rotating and residential proxies over HTTP(S), with SOCKS5 on paid plans. Datacenter and rotating exits are in the US, Italy and Spain; residential exits cover 170+ countries. Start with free proxies, no card required.