We don't require any authorization or API key for this service.
It's provided as a best-effort service.
We limit requests in time-range for specific IP addresses if anyone runs too many requests to preserve availability of this service.
For example, to fetch data about your IP in json format:
https://ipleak.net/jsonTo force use of IPv4:
https://ipv4.ipleak.net/jsonTo force use of IPv6:
https://ipv6.ipleak.net/jsonTo fetch data about your DNS in json format (replace <random_long_hash> with a random hash in every request; must be 40 chars length):
https://<random_long_hash>.ipleak.net/jsonTo fetch data about the IP address 220.127.116.11 in xml format:
|query_text||Your query text|
|query_type||Can be myip, mydns, ip or domain|
|query_date||Unix timestamp of server result.|
|level||Level of detail. Can be min or max. Only some IP addresses are fetched for all available data (max levels)|
|cache||Unix timestamp of data accuracy, if the level is max. Data at min level are always in real time. Fields like Tor and reverse are always in real time.|
|ip||The IP address.|
|country_code||Country ISO code|
|tor||If the IP address matches a Tor Exit Node.|
The above fields are always provided. Other fields may be available if we known additional data.
If you query a domain name, every IP address resolved for that is available under an ips data node.
If the address is an IANA special address, data will contain special fields. See as example 127.0.0.1 ( xml, json)
Look IANA IPv4 / ipv6 Special-Purpose Address Registry for more information about the fields.