About MyIPKit
Your network, explained. Fast, private network tools without the clutter.
Why this exists
Finding out your own IP address should take one second and one page. In practice, most sites that answer the question bury the answer under advertising, then explain it in copy written for a search engine rather than for you.
MyIPKit puts the answer first. Your address appears at the top of the page before anything else loads. Everything else — your provider, your approximate region, the diagnostic tools — sits below it, and each result comes with a short explanation of what it actually means.
What MyIPKit does
- Shows the public IP address our edge observed for your request, and whether it is IPv4 or IPv6.
- Identifies the network operator behind that address and the approximate region it is registered to.
- Looks up any IP address, domain or AS number in the public registries.
- Reads DNS records, including reverse DNS.
- Calculates subnets and CIDR ranges, entirely in your browser.
- Tests whether your connection has IPv4, IPv6 or both, by contacting each separately.
- Lists the commands that answer, on your own machine, what a browser cannot.
- Builds a diagnostic report you can hand to IT support, with your address masked if you want.
What MyIPKit deliberately does not do
A tool that shows a confident number it cannot actually measure is worse than no tool at all. These are left out on purpose:
- Claim to know both your IPv4 and IPv6 address from one request. One HTTP request reveals one address. The dual-stack test does it properly, by contacting two endpoints and saying so.
- Present IP location as precise. It is approximate, it is often wrong about the city, and it never identifies a street address. Every location on this site says so.
- Declare that you are using a VPN. Detection produces a probability, not a fact. Dressing a guess up as a verdict misleads people.
- Score how unique your browser fingerprint is. Producing that number requires building the fingerprint first. MyIPKit reads browser values for display and never combines them into an identifier.
- Scan your local network. A browser cannot, and a site that tried would be scanning the networks of visitors who never agreed. The local checks page gives you the commands to run yourself instead.
- Scan ports or fetch arbitrary URLs on request. Both are abuse vectors, and neither belongs in a general-purpose diagnostic site.
- Run a download or upload speed test. Doing it properly needs infrastructure this service does not have. The Network Report measures HTTP latency, and says exactly that.
How your data is handled
Serving a web request means the server necessarily sees your IP address — that is how the reply reaches you. MyIPKit uses it to answer your request and does not write it to a database. Diagnostic reports are assembled in your browser and are never uploaded. There are no accounts, and the site works without one.
The full detail is in the privacy policy.
How it is built
MyIPKit is a static site with a small number of edge functions. Most pages ship no JavaScript at all; the two calculators run entirely in your browser and never send your input anywhere. DNS queries go to a public DNS-over-HTTPS resolver, and registration data comes from the official RDAP registries through the IANA bootstrap service. There is no analytics script and no advertising script on the site today.
Accuracy and corrections
If MyIPKit reports something wrong — a misidentified network, a bad location, an explanation that is misleading — please say so. Corrections are welcome and quick to make. See the contact page.