$ curl betaconsult.sk 35.172.165.64 $ http -b betaconsult.sk 35.172.165.64 $ wget -qO- betaconsult.sk 35.172.165.64 $ fetch -qo- https://betaconsult.sk 35.172.165.64 $ bat -print=b betaconsult.sk/ip 35.172.165.64
$ http betaconsult.sk/country United States $ http betaconsult.sk/country-iso US
$ http betaconsult.sk/city Ashburn
$ http betaconsult.sk/json { "ip": "35.172.165.64", "ip_decimal": 598517056, "country": "United States", "country_eu": false, "country_iso": "US", "city": "Ashburn", "hostname": "ec2-35-172-165-64.compute-1.amazonaws.com", "latitude": 39.0481, "longitude": -77.4728 }
Setting the Accept: application/json
header also works as expected.
Always returns the IP address including a trailing newline, regardless of user agent.
$ http betaconsult.sk/ip 35.172.165.64
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.