Geolocation readout
{{ displayFields.IP || '—' }}
{{ summaryLocationLine }}
{{ displayFields.Country }} {{ displayFields.City }} {{ displayFields.Type }} {{ displayFields.ASN }} {{ displayFields.Timezone }} {{ summaryConfidenceLabel }}
Examples: 8.8.8.8, 2001:4860::8888, example.com, or https://example.com/path.
Choose IPv4 first for common A-record checks, IPv6 first when investigating AAAA reachability.
Leave on when documenting support tickets; off skips the extra reverse-DNS query.
{{ include_ptrBool ? 'On' : 'Off' }}
Regional is broadest, City centers the pin, Close is for reviewing returned coordinates.
Accepted range: 2500-15000 ms in 500 ms steps; raise it on slow networks.
ms
Field Value Copy
{{ row.label }} {{ row.value }}
Signal Value Copy
{{ row.label }} {{ row.value }}
Open OSM Open Google
Check Recommendation Copy
{{ row.label }} {{ row.value }} 

                    

                


            


        

    

                

                

                    

                        

                            Tags: DNS, IP Addressing, Networking
                        

                        

                            
                            
                        

                    

                

            

        

    


                    
        

        

        

            

            
        

        


                    

                

                

                    

                                                                                

                                
                                    
                                        What Is My Internet Protocol (IP) Address?
                                                                                    Check your public IP address with IPv4/IPv6 visibility, ASN, reverse-DNS, location, and source agreement clues for support tickets.
                                                                            
                                    
                                
                            

                                                                                

                                
                                    
                                        IPv6 Address and Subnet Calculator
                                                                                    Plan an IPv6 subnet from an address or CIDR, with canonical ranges, child-prefix counts, reverse-DNS alignment, and EUI-64 samples.
                                                                            
                                    
                                
                            

                                                                                

                                
                                    
                                        IPv6 Address Compressor / Expander
                                                                                    Convert one IPv6 value between compressed and expanded forms, with hextet, binary, reverse-DNS, prefix, zone, and dotted-tail checks.
                                                                            
                                    
                                
                            

                                                                                

                                
                                    
                                        EDNS Client Subnet (ECS) Tester
                                                                                    Check EDNS Client Subnet behavior for a DNS name by comparing hinted and control DoH lookups, echoed cache scope, answer drift, and resolver evidence.
                                                                            
                                    
                                
                            

                                            

                

            

        
                                                                                                                                                                                                                                                        
        

        

            
            

                Customize

                

                    

                        

                            
                            
                        


                        

                            
                            
                        


                        

                            
                            
                        

                    


                    

                        Advanced

                        

                            

                                
                                

                                    
                                    
                                

                            


                            

                                
                                

                                    
                                    
                                

                            


                            

                                
                                

                                    
                                    :
                                    
                                

                            


                            

                                
                                

                                    
                                    
                                

                            


                            

                                

                                    
                                    
                                

                            


                            

                                

                                    
                                    
                                

                            


                            

                                
                                
                            


                            

                                
                                
                            

                        

                    

                

            

            
        


        

            
            
            
        


        
        

    

    

        

  

  
IP geolocation connects a public internet address to the network and place data currently associated with that address. It is useful for adding context to logs, sign-in alerts, support tickets, firewall events, and domain checks, but it is not the same as GPS location. A public IP can represent a household connection, a mobile carrier gateway, a cloud server, a content delivery node, a VPN exit, or a public resolver.


  
The practical value comes from reading several weak signals together. Country, region, city, coordinates, and timezone describe approximate network geography. ISP, ASN, organization, and reverse DNS describe ownership or infrastructure clues. A tidy city name without the operator context can be misleading, especially when shared hosting, anycast, mobile networks, or privacy services are involved.


  

    
      IP geolocation evidence path
      A public IP or resolved host is reduced to one address, then read through approximate location, network ownership, reverse DNS, and map evidence.
      
      
        
        Public target
        IP address
        or resolved host
        
        
        
        Lookup signals
        place, timezone
        ASN, ISP, PTR
        
        
        
        Context
        coarse evidence,
        not device location
        
        A map pin supports the table; it does not turn IP data into street-level location.
      
    
    
IP geolocation is strongest when place clues and network-owner clues are kept together.

  


  
A lookup is most helpful when it answers a first-pass question: does this address look like the network I expected, and what should I check next? The answer can guide triage, annotation, and escalation, but high-stakes attribution still needs timestamps, account activity, logs, and provider-side evidence.


  
The safest reading is approximate network context at one moment in time. DNS can change, geolocation databases can disagree, and the same address can be shared by many users or services.






  
How to Use This Tool:


  
Run one lookup at a time so the snapshot, evidence rows, map, and exports all describe the same target.


  
    
    
  1. Enter one public IPv4 address, public IPv6 address, domain, or full URL in IP address, domain, or URL. Use Use my IP only when you want the public address your browser currently presents to the internet.
    2. 
    
  2. Open Advanced before the run if the starting value is a domain or URL and the address family matters. Domain address preference controls whether IPv4 or IPv6 records are tried first for that host.
    3. 
    
  3. Leave Reverse DNS evidence on when the result may be copied into a ticket or investigation note. Turn it off only when you want to skip the extra PTR check.
    4. 
    
  4. Click Lookup. A blank input shows Enter an IP address or domain., and a name that cannot resolve shows Could not resolve domain to an IP.
    5. 
    
  5. Start with Location Snapshot. Confirm IP, Type, Country, Region, City, Timezone, ISP, ASN, and AS Org before trusting the map.
    6. 
    
  6. Use Network Evidence and Next Checks to separate the original input, resolved address, PTR signal, timeout, ownership clue, and follow-up recommendations.
    7. 
    
  7. Open Location Map only after the table looks plausible. Map zoom changes framing, not accuracy. JSON is the structured view when you need a machine-readable record.
    8. 
  


  
If a lookup fails, switch to a known public address or resolvable hostname. Private addresses, local-only names, and stale hostnames do not produce meaningful public geolocation evidence.






  
Interpreting Results:


  
Read the result in two passes. First confirm the address and network operator. Then read the place fields as approximate geography. This order helps prevent a precise-looking map pin from outweighing stronger routing clues such as ASN, ISP, organization, and reverse DNS.


  

    

      
      
        

          Result field
          What it helps with
          Common mistake
        

      
      
        

          IP and Type
          Confirming the exact IPv4 or IPv6 address that was geolocated.
          Assuming a hostname always resolves to the same address later.
        

        

          Country, Region, City, Postal
          Coarse location checks and timezone sanity checks.
          Treating city or postal data as a street-level endpoint location.
        

        

          Latitude, Longitude, and map marker
          Visual orientation and coordinate copying.
          Reading the marker as independent confirmation. It plots the same returned coordinates.
        

        

          Timezone and Local Time
          Comparing activity time against the approximate network location.
          Using timezone alone to identify a user or city.
        

        

          ISP, ASN, AS Org
          Identifying the operator, carrier, hosting network, or public service behind the address.
          Assuming the operator is the same as the person or organization using the address at a given time.
        

        

          Reverse DNS
          Spotting router, resolver, CDN, or provider naming clues when a PTR record exists.
          Treating a blank PTR as suspicious. PTR records are optional and often absent.
        

        

          Source Host
          Remembering which host or URL was reduced to the displayed IP.
          Assuming every address behind that host has the same geolocation.
        

      
    

  


  
When signals disagree, prefer the network evidence over the map. A city result paired with a hosting ASN, anycast public service, mobile gateway, or generic PTR usually describes infrastructure location, not a person or device.






  
Technical Details:


  
IP geolocation is a lookup problem, not a mathematical calculation. The same input can produce a different result later if DNS answers change, address ownership moves, routing changes, or the geolocation provider updates its data. A domain or URL adds one more step because it must be reduced to one public address before place data can be requested.


  
Reverse DNS is separate from geolocation. For IPv4, the address octets are reversed under the reverse-DNS tree. For IPv6, the address is expanded into hexadecimal nibbles, reversed, and checked under the IPv6 reverse-DNS tree. The PTR value, when present, is a naming clue published by the address operator or delegate, not a verified identity statement.


  
Lookup Core

  

    

      
      
        

          Stage
          Rule
          Output or boundary
        

      
      
        

          Input classification
          A value that looks like IPv4 or IPv6 is used directly. Other values are treated as a host or URL.
          The lookup target becomes either the entered public IP or one resolved public IP.
        

        

          Host extraction
          For a URL, the hostname is extracted and path fragments are ignored.
          The result can include Source Host so the starting name is not lost.
        

        

          Address resolution
          The selected address-family preference controls which DNS record family is tried first.
          A dual-stack name may be represented by one IPv4 or IPv6 answer for this run.
        

        

          Geolocation lookup
          The chosen public IP is checked against live IP geolocation data.
          The result can include city, region, country, postal code, coordinates, timezone, ISP, ASN, and organization.
        

        

          PTR evidence
          When enabled, a separate reverse-DNS query asks whether the address has a PTR name.
          Returned PTR data is supporting evidence only. Missing PTR data is common.
        

        

          Map framing
          Coordinates are plotted as one marker when latitude and longitude exist.
          Map zoom changes how closely the marker is framed; it does not improve geolocation precision.
        

      
    

  


  
IPinfo-style geolocation data commonly includes an address, location fields, timezone, coordinates, and autonomous-system context. Those fields are useful because they combine routing ownership and approximate place data, but they are still database observations. Accuracy varies by country, network type, address pool, and whether the address belongs to an access network, a hosting provider, a privacy service, or an anycast system.


  

    

      
      
        

          Address class
          Meaning for geolocation
          Practical result
        

      
      
        

          Public IPv4 or IPv6
          Can be routed on the public internet and may appear in geolocation data.
          Use the full result, then verify with logs and ownership evidence.
        

        

          Private IPv4 ranges
          Reserved for private networks and not globally unique on the public internet.
          They are not meaningful public geolocation targets.
        

        

          Unique local IPv6
          Designed for local communication and not expected to be globally routed.
          Use local network documentation instead of public geolocation.
        

        

          Domain or URL
          Must resolve to one public address before location can be checked.
          Repeatable comparisons require the same name, address family preference, and run time.
        

      
    

  


  
Because there is no formula, fair comparisons depend on consistent inputs. Record the original input, resolved IP, address family, timestamp, and PTR state when the finding may be reviewed later.






  
Limitations, Privacy, and Accuracy Notes:


  
This is a networked lookup. Address detection, host resolution, geolocation, reverse DNS, and map display all involve external services. The file exports are created after the lookup, but the lookup itself is not offline.


  
Accuracy is uneven. Country-level results are often more reliable than city or postal-level results, and mobile gateways, VPNs, hosting networks, carrier-grade NAT, and anycast services can point to infrastructure rather than the actual end user. A public IP can also be reassigned, shared, or represented differently by different data providers.


  
Use the result as context for investigation, not as proof of identity, address ownership at a legal standard, or exact physical location. For abuse reports, security incidents, or account disputes, pair the geolocation snapshot with timestamps, server logs, account records, and provider contacts.






  
Worked Examples:


  
Reviewing a public resolver address

  
Enter 8.8.8.8 and run the lookup. A result that shows a Google ASN, public resolver-style PTR evidence, and a broad California location should be read as public infrastructure context. It does not identify the person who used a service that happened to query through that resolver.


  
Checking a hostname snapshot

  
Paste a hostname or URL and keep the default address-family preference. The lookup resolves one address, then geolocates that address. If the result matters, copy the Source Host and Resolved IP evidence because the hostname may return a different address on another network or at another time.


  
Testing a private address by mistake

  
An address such as 192.168.1.10 belongs to private IPv4 space. It can be useful inside a local network, but it has no unique public location. Use your router, DHCP, VPN, or internal inventory data for that kind of address instead of expecting a public geolocation result.






  
FAQ:


  

    Can I enter a domain instead of an IP address?
    
Yes. The host is resolved to one public IP first, and the result describes that resolved address. DNS changes over time, so keep the resolved IP with any saved evidence.

  


  

    Why does the map pin look precise?
    
The map plots returned coordinates, but those coordinates are still IP geolocation data. They may represent a network, provider facility, city centroid, or routing point rather than a device.

  


  

    What does Use my IP reveal?
    
It detects the public address your browser presents to the internet. It does not show the private address assigned inside your home, office, phone, or router network.

  


  

    Why is reverse DNS missing?
    
PTR records are optional. Many valid public addresses have no PTR record, and many PTR records use generic provider naming that only adds a small clue.

  


  

    Does this prove where a user is located?
    
No. It gives approximate network evidence for a public address. Use it with logs and account context, especially when VPNs, mobile carriers, hosting networks, or shared addresses may be involved.

  






  
Glossary:

  

    
ASN

    
Autonomous System Number, identifying a network that originates or operates address space on the internet.


    
PTR record

    
A reverse-DNS record that maps an IP address back to a hostname-like label.


    
DNS-over-HTTPS

    
A way to send DNS queries inside HTTPS connections instead of traditional plaintext DNS transport.


    
Public IP address

    
An address that can be routed on the wider internet, unlike private or local-only address space.


    
Unique local IPv6 address

    
An IPv6 address intended for local communication within a site or private network.

  






  
References: