finds.dev← search

// the find

jason5ng32/MyIP

★ 11,100 · JavaScript · MIT · updated Jul 2026

The best IP Toolbox. Check your IP address & geolocation, test IP for WebRTC and DNS IP leaks, run an IP quality check, browser fingerprint check, website availability check, network speed test, global latency test, MTR test, Whois search, and more.

MyIP is a self-hostable network diagnostic dashboard that aggregates IP geolocation from multiple providers, runs WebRTC/DNS leak tests, checks site availability, measures latency via Globalping, and does MTR traces — all in one Vue 3 frontend backed by a Node.js Express API. It's aimed at developers and privacy-conscious users who want to verify VPN/proxy behavior or debug network routing without bouncing between five different tools.

The multi-provider IP approach is genuinely useful — pulling from IPInfo, IPAPI.is, IP2Location, MaxMind, and Cloudflare simultaneously means you see disagreements between databases rather than trusting one blindly. The shareable diagnostic report feature (snapshotting results to Cloudflare KV) solves a real problem when you need to hand off network debug info to someone else. The ASN connectivity graph with upstream topology to Tier-1 backbones is the kind of thing you'd normally need bgpview.io open in another tab for. Docker deployment is first-class with automatic MaxMind database updates baked in, which is the right call given GeoLite2's license restrictions.

The MaxMind dependency is a meaningful friction point — a fresh Docker container silently degrades (503s, missing country badges) if you don't set three env vars, which is the kind of surprise that wastes an hour. The backend is a single `backend-server.js` monolith with 30+ API route files hanging off it; there's no clear error boundary between a slow RIPE lookup and everything else timing out. The 258-item 'cybersecurity checklist' feels like checkbox padding — it's a static JSON file with no verification, just self-attestation, which undermines the credibility of the diagnostic-tool framing. No authentication means a public deployment is immediately abusable; the rate-limiting env vars exist but default to zero (no limit), so the safe default is actually the unsafe one.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →