Free ipify Alternative

The translation

The ipify facts are from its own site and the README of its source repository as read on 4 November 2026.

What differs

• One format. ipify answers in text, JSON or JSONP depending on a parameter. This endpoint answers JSON, always the same one field. A shell script takes the address with jq -r .ip, a browser reads it with fetch and the CORS header, and a device parses one short JSON document.
• IPv4. ipify has hosts for IPv6 requests and for either family. This host is reached over IPv4, so a dual-stack client sees its IPv4 egress address and an IPv6-only client has no route to it. If what you need is your IPv6 address, use api6.ipify.org.
• A quota. ipify states no limit. Here every endpoint shares 5,000 requests per address per day. A script that checks its address once a minute spends 1,440 of them; a status page that checks on every load should think about how often.
• Logging. ipify states that it logs no visitor information. This service keeps ordinary request logs, which hold the address, for the period the privacy policy gives. For a one-off check that makes no difference; a privacy-sensitive caller should know it.
• What the address means. On both services it is the public address of whatever the traffic last passed through: a home router, a corporate NAT, a VPN or a cloud egress gateway, not the address on your own interface.
• The next question. Knowing the address, a script often asks where it is or what time it is there. Those answers are free on the same host: country, region and time zone from the IP reverse lookup, and the local time from IP datetime.

From a shell, a browser or a device

In a shell:

curl -s https://aisenseapi.com/services/v1/client_ip
# {"ip":"203.0.113.10"}

curl -s https://aisenseapi.com/services/v1/client_ip | jq -r .ip
# 203.0.113.10

In a browser, without JSONP, because the answer carries a permissive CORS header:

const answer = await fetch("https://aisenseapi.com/services/v1/client_ip");
const { ip } = await answer.json();

On an ESP32 with the Arduino core, the same call over TLS; setInsecure() skips certificate verification, which is fine for reading your own address and not fine for anything you must trust:

#include <WiFiClientSecure.h>
#include <HTTPClient.h>

WiFiClientSecure client;
client.setInsecure();

HTTPClient http;
http.begin(client, "https://aisenseapi.com/services/v1/client_ip");
int code = http.GET();
String body = http.getString();   // {"ip":"203.0.113.10"}
http.end();

To verify a VPN or an egress gateway, call once before connecting and once after; the two addresses should differ.

The field

The answer is sent with cache-control: no-store, so neither the browser nor a proxy on the way answers from a copy.

Errors

Every refusal is JSON with error and fix.

Privacy and limits

Every path shares the service-wide ceiling of 5,000 requests per IP address per day. ipify, for comparison, states no limit and no account, offers text, JSON and JSONP, and runs separate hosts for IPv6; those are its statements as of November 2026 and may change.

Related APIs