$ curl aglarannon.valec.net 98.80.143.34 $ http -b aglarannon.valec.net 98.80.143.34 $ wget -qO- aglarannon.valec.net 98.80.143.34 $ fetch -qo- https://aglarannon.valec.net 98.80.143.34 $ bat -print=b aglarannon.valec.net/ip 98.80.143.34
$ http aglarannon.valec.net/country United States $ http aglarannon.valec.net/country-iso US
$ http aglarannon.valec.net/city Seattle
$ http aglarannon.valec.net/json { "ip": "98.80.143.34", "ip_decimal": 1649446690, "country": "United States", "country_eu": false, "country_iso": "US", "city": "Seattle", "hostname": "ec2-98-80-143-34.compute-1.amazonaws.com", "latitude": 47.54, "longitude": -122.3032 }
Setting the Accept: application/json
header also works as expected.
Always returns the IP address including a trailing newline, regardless of user agent.
$ http aglarannon.valec.net/ip 98.80.143.34
As of 2018-07-25 it's no longer possible to force protocol using
the v4 and v6 subdomains. IPv4 or IPv6 still can be forced
by passing the appropiate flag to your client, e.g curl -4
or curl -6
.
Yes, as long as the rate limit is respected. The rate limit is in place to ensure a fair service for all.
Please limit automated requests to 1 request per minute. No guarantee is made for requests that exceed this limit. They may be rate-limited, with a 429 status code, or dropped entirely.
Yes, the source code and documentation is available on GitHub.