$ curl ip.xila.me 52.54.111.228 $ http -b ip.xila.me 52.54.111.228 $ wget -qO- ip.xila.me 52.54.111.228 $ fetch -qo- https://ip.xila.me 52.54.111.228 $ bat -print=b ip.xila.me/ip 52.54.111.228
$ http ip.xila.me/country United States $ http ip.xila.me/country-iso US
$ http ip.xila.me/city Ashburn
$ http ip.xila.me/asn AS14618
Looks like you're with AMAZON-AES
$ http ip.xila.me/json { "ip": "52.54.111.228", "ip_decimal": 875982820, "country": "United States", "country_eu": false, "country_iso": "US", "city": "Ashburn", "hostname": "ec2-52-54-111-228.compute-1.amazonaws.com", "latitude": 39.0469, "longitude": -77.4903, "asn": "AS14618", "asn_org": "AMAZON-AES" }
Setting the Accept: application/json
header also works as expected.
Always returns the IP address including a trailing newline, regardless of user agent.
$ http ip.xila.me/ip 52.54.111.228
$ http ip.xila.me/port/8080 { "ip": "52.54.111.228", "port": 8080, "reachable": false }
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.