What is my IPv6?
If this connection reaches us over IPv6, the detected address is IPv6. You can also paste any IPv6 below. Dual-stack networks may still show IPv4 depending on the browser path.
IP locations are approximate network estimates. Queries are processed at Cloudflare's edge and full visitor IP addresses are not retained in application storage.
How to look up an IP
- If your browser reaches Cloudflare over IPv6, homepage detection is IPv6. Dual-stack networks may still show IPv4.
- You can also paste any public IPv6. Fields match IPv4 lookups: location, ISP, ASN and privacy signals.
- curl https://ipkit.dev returns JSON for whichever version connected. Look up /<ipv6> (some shells need URL encoding).
- IPv6 is not automatically more accurate; precision still depends on the registry and ISP.
IPv4 and IPv6 on the same tool
IPKit accepts both families. Homepage detection uses the address Cloudflare sees on the request. An IPv6 lookup of 2001:4860:4860::8888 works the same as an IPv4 lookup. curl https://ipkit.dev returns whichever version connected. This page is for people who specifically want IPv6: seeing whether this connection is IPv6, or looking up an IPv6 literal. Dual-stack users often still land on IPv4 because the browser picked that path. That is expected. Use the same JSON schema; only the address family changes. Quote or encode IPv6 in URLs when your shell treats colons specially.
Geolocation
Approximate country, region, city, coordinates, postal code and local timezone for IPv4 and IPv6.
ASN & network
See the autonomous system, organization, announced route, carrier and connection usage type.
Privacy signals
Understand known VPN, proxy, Tor, relay, cloud and threat signals without an invented fraud score.
ipkit.v1 JSON fields
HTML and curl share the same record. Field names stay in English so scripts can parse one schema. Values are network estimates, not a street address or identity.
- schema
- Always ipkit.v1 so clients can detect breaking changes.
- ip
- The public address that was detected or requested.
- type
- IPv4 or IPv6.
- source
- ipregistry for full intel, or cloudflare when only edge metadata is available.
- location.country
- Registered country for the network, not a street address.
- location.city
- City at network granularity when the provider has one.
- location.timezone
- IANA timezone tied to the geolocation guess.
- network.asn
- Autonomous system number announcing the prefix.
- network.organization
- ISP or organization name for that ASN.
- security.vpn
- Whether the provider flags a VPN.
- security.proxy
- Whether the provider flags a proxy.
- security.tor
- Whether the provider flags a Tor exit.
- security.risk
- low, medium, high or unknown — a signal, not proof for blocking.
FAQ
Why do I only see IPv4?
Your ISP, Wi-Fi, VPN or browser may prefer IPv4. Try a network with IPv6 or look up a known IPv6 address.
Is IPv6 location more accurate?
Not necessarily. Accuracy still depends on the registry and ISP, not the IP version.
JSON for IPv6?
Yes. Quote the address in URLs when needed: curl https://ipkit.dev/2001:4860:4860::8888 may need encoding in some shells.
Is there a JSON API?
Yes. curl https://ipkit.dev for the current connection and curl https://ipkit.dev/<ip> for a specific public address. The schema is ipkit.v1.
Do you create a page for every IP?
No. Lookup stays on /ip-lookup and the JSON API. Thin HTML per address would duplicate content and waste crawl budget.
Why do I still see IPv4 here?
The browser may have connected to Cloudflare over IPv4 even if your LAN has IPv6. Paste an IPv6 or try another network.