A public route through what we build next

myip is growing from a dependable IP lookup into a broader set of transparent network tools, data-quality controls, and carefully bounded research. This page separates delivered work from active work, plans, and questions that may never become product features.

No dates and no delivery promises. Status describes direction, not a release schedule.

Shipped

The foundation people can use today.

IPv4 and IPv6 lookup with RDAP, ASN, reverse DNS, geolocation, and network classification.
Privacy and threat signals for VPN, proxy, Tor, abuse feeds, and an explainable fraud-risk view.
Static browser and network tools, localized pages, public API documentation, accounts, and bounded usage tiers.

Current

Work focused on making the existing service safer and easier to trust.

Hardening data imports so refreshes are gated, observable, recoverable, and honest about stale or removed upstream records.
Improving frontend quality, locale consistency, navigation, and generated-content checks.
Expanding operator visibility for background imports and source freshness without weakening production isolation.

Planned

Directions we intend to explore after their prerequisites are sound.

A resumable, rate-aware public registry and geofeed pipeline designed around source terms and operational limits.
More transparent source attribution, history handling, and quality evidence for network and geolocation data.
Additional small, local-first tools for understanding addresses, routes, headers, and browser exposure.

Research

Exploratory questions, not promised capabilities. They may change, remain public-data-only, or may not ship.

Whether bounded public routing observations can help explain changes in network registration and route-origin visibility.
How to make temporal joins, missingness, uncertainty, and privacy limits visible instead of hiding them behind a score.
Synthetic and public-data methods that can be reproduced without exposing restricted reports or identifiable case studies.