MyIP (IPCheck.ing)

jason5ng32’s self-hostable IP toolbox — a web app that runs the whole IP-reconnaissance stack against you and shows what it finds. MIT, ~11.3k★ / 1.2k forks, Node + Vite, Docker image, PWA, four UI languages (English, Chinese, Russian, French), public demo at ipcheck.ing, self-hosted on port 18966 (backend 11966).

It is the spoke’s first subject-side tool. Everything else here points outward at a target (gitsint, swaggerspy, llm-osint); this one points the same primitives back at the operator’s own connection.

What it checks

Grouped by what an outside observer would learn:

• Identity of the connection — local IPv4/IPv6 from several providers, per-IP country, region, ASN, geolocation; lookup for any arbitrary IP; ASN history and upstream topology up to the Tier 1 backbones; WHOIS for domains and IPs; MAC address lookup.
• Leaks that de-anonymize a proxy user — WebRTC detection (the IP that leaks through ICE candidates), DNS leak test (which resolver actually answers), and browser fingerprinting computed several ways.
• Reachability and interference — availability checks against Google, GitHub, YouTube, ChatGPT and others, live service-status pages, global latency and MTR from servers in several regions, speed test, DNS resolution from multiple sources for pollution detection, and a censorship check for whether a site is blocked in particular countries.
• Proxy correctness — a rule-testing harness: the README ships Clash-style rules pinning ptest-1..8.ipcheck.ing to different proxies and 4/6.ipcheck.ing to DIRECT, so you can confirm each rule sends traffic where you think it does.
• A 258-item cybersecurity checklist bolted on beside the diagnostics.

The censorship check, DNS-pollution detection and proxy-rule harness name the user this was built for: someone on a filtered network verifying that their circumvention setup works and doesn’t leak.

The data layer is the interesting part

MyIP has no proprietary intelligence. It composes the same commercial and research datasets an OSINT analyst resolves an IP against: MaxMind GeoLite2 (City + ASN, required, and the databases can’t be redistributed so every deployer brings their own key), CAIDA (as2org for ASN org names, as-rel2 for the AS connectivity graph), RIPEstat for ASN history, and IPInfo / IPAPI.is / IP2Location as optional geolocation vendors, plus Cloudflare for AS data. That stack is worth reading as an inventory of the attribution layer itself — see ip-reconnaissance.

A privacy tool with telemetry

VITE_GOOGLE_ANALYTICS_ID is marked required in the environment table, and the optional Sentry integration ships a first-party route (/api/monitoring) whose stated purpose is relaying Sentry envelopes past ad blockers. Neither is hidden, both are configurable, and self-hosters can leave the Sentry DSN empty (no Sentry code enters the bundle). Still: the hosted demo at ipcheck.ing is a privacy-diagnostic service that measures your exposure while running analytics and blocker-evading error telemetry. Self-host if that matters.

Tier

T3 — a project README, so the feature list is the author’s own and the star count is a dated snapshot (2026-07-27). Nothing here is independently evaluated. Its value is as an artifact: a working, popular, MIT-licensed enumeration of what a network connection discloses.

Related

ip-reconnaissance · osint · gitsint · swaggerspy · synthesis