Confirming a VPN or proxy is actually carrying your traffic
If the address shown is your ISP's rather than the VPN egress, the tunnel is down or split tunnelling is routing this traffic outside it.
Shows your public IP address plus ASN, ISP, city, country and VPN hints.
Shows your public IP address plus ASN, ISP, city, country and VPN hints.
Just open the page
IP 203.0.113.7 · ASN AS12345 · ISP ExampleNet · Bratislava, SK
YAS detects your address from the request.
The IP is the address remote servers see when you connect.
Your input is sent to YAS infrastructure because the tool requires server-side processing or public network queries. Input is not stored.
curl -X POST "https://yas.sh/api/v1/tools/what-is-my-ip" \
-H "Content-Type: application/json" \
-d '{}'const res = await fetch("https://yas.sh/api/v1/tools/what-is-my-ip", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({}),
});
const data = await res.json();import requests
r = requests.post("https://yas.sh/api/v1/tools/what-is-my-ip", json={})
data = r.json()| Field | Type | Required | Description |
|---|---|---|---|
| ip | string | No | Optional specific IP to look up (defaults to your own via X-Real-IP / X-Forwarded-For). Also supported as ?ip= on GET. |
{ "result": { "ip": "1.2.3.4", "ipv4": "1.2.3.4", "asn": "AS13335", "asName": "Cloudflare", "org": "Cloudflare", "city": "Lisbon", "region": "Lisbon", "country": "PT", "loc": "38.7167,-9.1333", "timezone": "Europe/Lisbon", "isVpn": null, "isTor": null } }Your public IP with ASN, ISP, geo and VPN/Tor hints (ipinfo-style). No key needed.
400 VALIDATION_ERROR — invalid input or unsupported option.413 PAYLOAD_TOO_LARGE — input exceeds the 64 KB limit.429 RATE_LIMIT_EXCEEDED — rate limit exceeded (60 req/min).The address shown is the source address of the TCP connection as the server observed it — the public address of whatever NAT device, proxy or VPN egress your traffic last passed through, not the address configured on your machine. Behind home or corporate NAT your device holds an RFC 1918 address that never appears on the internet.
When a request passes through proxies or a CDN, the original client address is carried in headers: the legacy X-Forwarded-For chain or the standardised Forwarded header (RFC 7239). Those headers are trivially spoofable by the client, so they are only trustworthy when appended by an infrastructure layer you control and when everything downstream refuses to accept them from arbitrary sources.
If the address shown is your ISP's rather than the VPN egress, the tunnel is down or split tunnelling is routing this traffic outside it.
Database firewalls, admin panels and SSH bastions are commonly restricted by source address. Residential addresses change, so re-check after a router reboot.
Seeing whether you are presented over IPv4 or IPv6 tells you which stack your traffic actually preferred, which matters when debugging dual-stack issues.
Services that block or localise by address use this same value. Seeing it explains why a site thinks you are in another country.
What this tool deliberately does not do, and where it will disagree with other implementations.