Who runs GoIPScan

GoIPScan is built and run by Anand Muddi, an independent developer based in the United Kingdom. It is not a company and there is no team — I write the tools, the guides and the tests.

Background

I've worked in IT for more than 20 years across infrastructure, security and solution architecture — designing, securing and troubleshooting the networks that organisations depend on.

Why GoIPScan exists

Most network tools are built for engineers. They assume you know what a port, an ASN or a WebRTC candidate is, and they rarely tell you whether what they found is actually a problem. I built GoIPScan so that anyone — not just IT professionals — can see how their home network looks from the outside, understand what each result means in plain English, and know what, if anything, to do about it.

Most "what is my IP" sites show you a number surrounded by adverts, and most network tools tell you a result without telling you how confident to be in it. That second part is the gap I am trying to fill.

When I tested IP geolocation properly — 15 addresses through three providers — all three agreed on the country every time, but on the exact city only 3 times out of 15, and on four addresses they disagreed by more than 100 km. Almost nothing on the web says that out loud, because "your location, accurate to the city" reads better than "your location, probably the right region". I would rather publish the measurement, including where it is unflattering.

Whether you are checking a VPN is actually working, diagnosing a connection problem, or simply curious what your IP gives away, the aim is the same: a clear answer, and an honest statement of how much to trust it.

How the tools work

Everything runs on request and nothing is stored. When you load a page, an edge function near you performs the lookup and returns the result — there is no database of visitors and no lookup history.

The location data comes from Cloudflare's edge geolocation, the network and ASN details from IPinfo Lite, and the VPN, proxy and Tor flags from ipapi.is. The browser privacy and email header tools do not call anything at all: they read what your browser already exposes, or parse what you paste, entirely on your own machine.

Each tool is checked against inputs with a known correct answer — a port that is definitely open, an address with a stable reverse-DNS record, a live Tor exit node. Those checks found four real bugs in my own tools in late September 2026, including a leak test that was reporting a leak for almost every visitor. I wrote them all up in how we test.