Some services will geolocate you by looking at your DNS server's geolocation, so when you try to resolve their endpoint www.example.com you'll get back an IP ad

Some services will geolocate you by looking at your DNS server's geolocation, so when you try to resolve their endpoint www.example.com you'll get back an IP address pointing to the closest datacenter. How do you know how is your DNS server geolocated? I made a tiny proof of concept of a DNS reflector with a little extra: $ dig +short whoami.fluffcomputing.com txt Or in Windows: nslookup -type=txt whoami.fluffcomputing.com Or in PowerShell: (Resolve-DnsName -Type txt -Name whoami.fluffcomputing.com).strings The DB used is MaxMind's GeoLite2; so the system is as (in)accurate as the DB might be. If you just request an A record you'll get just your DNS server IP address as other services do (e.g. whois.akamai.net).