About IPly
A privacy-focused IP address lookup tool built for developers, network administrators, and anyone who wants clear network diagnostics with honest disclosure about analytics, enrichment, and retention.
How It Works
Server-Side Detection
When you visit IPly, our edge servers immediately detect your IP address from the incoming HTTP request. This happens server-side before the page even loads in your browser.
IP Geolocation
We use Vercel request metadata by default, and run ipwho.is enrichment for explicit IP lookups or visitor-requested details when Vercel headers do not already provide the needed network data.
Our Privacy Commitment
Minimal Retention
We minimize retention and do not persist raw visitor IPs in application-controlled storage as part of normal product behavior.
Aggregate Analytics
We use Vercel Analytics and Speed Insights for aggregate product metrics.
Transparent Third Parties
When IP enrichment runs after a visitor requests details or submits an IP lookup, the IP being looked up is sent to ipwho.is to retrieve ISP, ASN, and location metadata unless request headers already provide the needed visitor network details. WHOIS lookups send the queried domain to rdap.org and any RDAP service it redirects to over HTTPS; .bg fallback lookups use whois.register.bg over TCP. When you run the WebRTC leak test, your browser may contact the listed Google and Cloudflare STUN servers to gather ICE candidates.
Some transient operational processing may still occur for security, abuse prevention, hosting, and caching. App-controlled storage can include short-lived hashed rate-limit identifiers, keyed cache identifiers, and cached tool results.
Data Sources
The information displayed by IPly comes from Vercel request metadata, public routing data, gesture-gated ipwho.is enrichment for supported lookup paths, WHOIS/RDAP responses, and browser-provided ICE candidate details during WebRTC tests.
- IP location: Vercel request metadata for the homepage, with ipwho.is enrichment for explicit IP lookups or visitor-requested details. Location is approximate and does not identify a person or street address.
- ISP and ASN: Vercel network headers when available for a visitor lookup, otherwise ipwho.is connection fields. These are provider-reported network details, not an independent ownership verification.
- DNS and reverse DNS: Standard DNS lookups send the queried domain to Cloudflare's 1.1.1.1 DNS-over-HTTPS resolver for TXT, DMARC, and SRV records; other standard DNS and reverse DNS records use the platform resolver. When you enable public resolver comparison, the queried domain is sent to both Cloudflare and Google over DNS over HTTPS for A, AAAA, MX, TXT, and NS records.
- WHOIS/RDAP: WHOIS lookups send the queried domain to rdap.org and any RDAP service it redirects to over HTTPS; .bg fallback lookups use whois.register.bg over TCP.
- WebRTC STUN: The WebRTC leak test can contact Google and Cloudflare STUN servers from your browser.
Questions or feedback? Reach us at admin@iply.dev