We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
IPv6 Location Lookup
Was this tool helpful to use?
Your feedback helps us make it better
Accurately find the geolocation of any IPv6 address, including country, city, and ISP details.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Enter an IPv6 address to request location and network metadata. Depending on what is returned for that address, the result can include country, region or province, city, ISP, owner, autonomous system number, postal code, time zone, accuracy, radius, and a data-source label. Missing fields appear as a dash. These are provider-supplied associations for an address or network range, not coordinates encoded in the IPv6 number itself.
Network operators can publish geolocation feeds that associate IP prefixes with geographic labels. The IETF describes those feeds as data linked to address ranges, with fields such as country, region, city, and postal code. The returned details therefore depend on available address data and its granularity. Select WGS84 or BD09 if your downstream mapping or data workflow requires one of those coordinate systems; the choice is sent with the lookup, and it does not make an estimate exact.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Enter an IPv6 address, such as 2001:db8::1. The field accepts IPv6 address notation; it is not a domain-name or IPv4 lookup.
Choose WGS84 or BD09 to match the coordinate convention expected by the system where you will use the result. WGS84 is selected by default.
Submit the lookup and review the fields that are populated. Copy the result record if you need to retain it.
When recording or comparing results, keep the original address, lookup date, coordinate-system choice, and field names with the returned values.
A dash for city or postal code means that value was not supplied in the displayed result; it does not by itself show that the address is invalid. Check the address spelling if the lookup fails altogether.
Use cases
See how the tool fits into real work and everyday tasks.
A network administrator can compare an IPv6 address's returned region and network owner with application logs as one lead in troubleshooting. Keep timestamps and other log evidence; a location result alone cannot explain who made a request.
A team maintaining a list of known services or peers can copy available network fields into its notes. Preserve the original address and query date so another person can revisit the association later.
Q&A
Find concise answers to common questions and confusing cases.
No. This lookup accepts IPv6 address notation. Use an IPv6 address as the input.
The lookup may not return every field for every address. A dash is a missing value in the displayed result, not a city-level accuracy guarantee or proof that the address is unusable.
No. It is a coordinate-system option for the lookup request. It does not change the address text, and you should use the convention required by the system receiving any returned location values.
Notes
Review scope, result limitations, and important precautions before use.
An address-level location association does not establish the physical location or identity of a person or device.
Network ranges may represent an ISP, hosting provider, gateway, or shared service. Location detail can be incomplete or approximate, and the page does not document the underlying dataset's publisher, geographic coverage, or update schedule. Do not use a city label as proof of a person's whereabouts or as the sole basis for a security, account, or compliance decision. Corroborate with appropriate network records and other reliable evidence.
Related
Discover related tools, collections, and available API capabilities.