DNSIPDNSipdns.info
FOR YOUR TERMINAL · 3 MIN READ

Your public IP. One command.

No banner, no markup, no extra fields. A command-line request to IPDNS returns the source IP seen by the service, followed by one newline.

No API keyIPv4 + IPv630 requests / minute

curl

Just the domain. No parameters needed.

Terminal
curl ipdns.info

That bare command uses HTTP. For an encrypted connection, use the HTTPS version below. Both return only your public IP address.

curl · HTTPS
curl -fsS https://ipdns.info

wget

Print the address directly to your terminal.

wget
wget -qO- https://ipdns.info

PowerShell

Use the dedicated plain-text endpoint in Windows PowerShell or PowerShell 7.

PowerShell
Invoke-RestMethod https://ipdns.info/ip

A predictable plain-text endpoint

The /ip path always returns plain text, regardless of user agent. Use it in a script when you want an address, not the browser workbench.

Plain text
curl -fsS https://ipdns.info/ip

JSON

JSON
curl -fsS https://ipdns.info/api/ip

The result contains ip and version. Personalized responses are not cacheable. No API key is required.

IPv4 or IPv6?

Use curl -4 or curl -6 when you want a specific address family and your connection supports it. The response is your public source address, which may belong to a NAT gateway, VPN or proxy—not your device’s private LAN address.

Your IP is not a DNS test

These endpoints report the address of your connection. To compare a domain’s DNS records, use the IPDNS workbench. It asks Cloudflare and Google public DNS through our server; it does not test your device’s configured DNS or measure worldwide propagation. The field guide explains how to read the differences.

SHARED RESOURCES / CLEAR LIMITS

30 requests in any 60 seconds.

IPDNS enforces a hard, rolling limit per source IP across its pages, assets and endpoints. Browser visits and command-line requests share the same allowance. People behind the same public IP, including shared NAT or VPN exits, share that budget.

Live DNS comparisons also have a separate limit of six requests per minute. On HTTP 429, wait for the number of seconds in the Retry-After header before retrying. Cache results where practical and avoid tight polling loops. These free endpoints have no uptime commitment.

← Back to the DNS workbenchRead the field guide →