Privacy Policy

Data we handle

When you use IPLense, we may handle:

• the IP address you submit, lookup type, page language, lookup time, and returned results;
• raw observations returned by data sources, IPLense-generated results, response status, and related version information;
• access and security logs, such as the source IP address, request time, browser or device information, pages visited, response status, rate-limit status, and security-verification result;
• a language-preference cookie and session cookies required for administrator login and website security;
• up to five recent successful lookup IPs stored locally in the current browser for search suggestions;
• a short-lived, one-time result handoff in the current tab's session storage when opening a result page or changing its language; it is deleted after an exact path, locale, and IP match and expires after 60 seconds;
• the email address, message, and follow-up correspondence you send to [email protected] or [email protected]; and
• standard network-request information sent by your browser when it loads OpenStreetMap tiles.

IPLense does not use advertising cookies or cross-site behavioral trackers.

How we use data

• complete Quick Check and Professional Check requests and provide a consistent Chinese or English experience;
• reuse existing IP intelligence, improve result quality, calibrate displayed fields, and assess data-source performance;
• prevent abuse, enforce lookup limits, verify Turnstile, and protect the website and administrator area;
• troubleshoot errors, monitor performance, track provider usage, and operate the service;
• respond to result corrections, data suggestions, support requests, and business inquiries; and
• meet applicable legal obligations and protect the legitimate interests of IPLense, users, and third parties.

Third-party processing

• IP intelligence providers receive the IP address you submit and return location, network-type, or risk-related data;
• Cloudflare Turnstile processes browser, device, and network signals needed for verification, as described in the Cloudflare Privacy Policy;
• Cloudflare Radar provides ASN-level traffic composition;
• OpenStreetMap tiles are loaded directly by your browser. A tile request normally includes the source IP address, browser information, and referring-page information. The map displays attribution linked to OpenStreetMap Copyright and License;
• when you open the home page, your browser requests this site's Cloudflare /cdn-cgi/trace path and contacts the ipify and icanhazip endpoints for the other address family to show your connection's region, Cloudflare data center, protocol, and other public IP;
• after a Quick Check result appears, your browser sends the reverse-lookup name for the IP you looked up to Cloudflare DNS (cloudflare-dns.com) and that IP's ASN to RIPEstat (stat.ripe.net) to show reverse DNS and ASN size;
• when you open the Exit and Split Routing Test, your browser directly contacts this site's /cdn-cgi/trace path, the IPv4 and IPv6 endpoints operated by ipify and icanhazip, the IP echo endpoints of UPYUN at pubstatic.b0.upaiyun.com and the University of Science and Technology of China at test.ustc.edu.cn, plus public trace paths on www.cloudflare.com, chatgpt.com, sora.com, openai.com, grok.com, gitlab.com, nodejs.org, claude.ai, www.perplexity.ai, copilot.microsoft.com, www.ecosia.org, www.crunchyroll.com, x.com, and www.linkedin.com. Each service receives the source IP address and standard network information for its request;
• when you open the DNS Location Check, your browser requests the /cdn-cgi/trace paths of this site and of the websites listed for the Exit and Split Routing Test, compares DNS with the exit most of those sites see, and concurrently contacts randomized subdomain endpoints operated by Surfshark, Fastly, ipleak, and ip-api. ipleak also receives the DNS server addresses found, to return their locations. These services receive the related HTTP and DNS requests and return the DNS resolver details they observe;
• when you open the WebRTC test, your browser concurrently contacts the IPv4 and IPv6 endpoints operated by ipify and icanhazip and connects independently to Google at stun:stun.l.google.com:19302, Cloudflare at stun:stun.cloudflare.com:3478, Twilio at stun:global.stun.twilio.com:3478, FreeSWITCH at stun:stun.freeswitch.org:3478, Nextcloud at stun:stun.nextcloud.com:3478, and BlackBerry at stun:stun.voip.blackberry.com:3478, obtaining the current public addresses and candidate addresses together. Each service receives the IP address and standard connection information for its connection; the page keeps only public server-reflexive candidates returned by STUN;
• when you open or rerun the Browser Fingerprint and Consistency Check, the page reads browser, system, device, time-zone, language, display, storage-capability, and rendering characteristics on the page, requests the /cdn-cgi/trace paths of this site and of the websites listed for the Exit and Split Routing Test (the exit country most of those sites see decides the checks) and the IPv4 and IPv6 endpoints of ipify and icanhazip for the exit country and address, and connects to Google at stun:stun.l.google.com:19302 and Cloudflare at stun:stun.cloudflare.com:3478 for the WebRTC public address, to calculate an environment-consistency score and list the complete fields;
• each time you open or rerun the Claude China User Check, the page sends one request to https://claude.ai/cdn-cgi/trace. Claude receives the source IP address and standard network information and returns a network region;
• when you open the My IP and Dual Stack test, your browser requests this site's /cdn-cgi/trace path and contacts the IPv4 and IPv6 endpoints operated by ipify and icanhazip;
• when you open the Cloudflare Connection check, your browser requests only this site's /cdn-cgi/trace path to read the data center, protocol, TLS version, and WARP status;
• when you open the AI Region Check, your browser requests the public trace paths on chatgpt.com, claude.ai, sora.com, openai.com, copilot.microsoft.com, www.perplexity.ai, and grok.com. Each platform receives the source IP address and standard network information;
• when you open the Reachability and Latency test, your browser keeps sending these sites small requests to time reachability and response (most for headers only, downloading nothing; one per site each round; it stops after the set number of rounds and pauses while the page is in the background): www.baidu.com, www.qq.com, www.163.com, www.taobao.com, www.jd.com, www.mi.com, weixin.qq.com, weibo.com, www.xiaohongshu.com, www.douyin.com, www.bilibili.com, chat.deepseek.com, www.yahoo.co.jp, www.rakuten.co.jp, www.naver.com, line.me, www.kakao.com, www.nicovideo.jp, www.google.com, www.apple.com, www.amazon.com, www.wikipedia.org, www.microsoft.com, github.com, gitlab.com, registry.npmjs.org, pypi.org, hub.docker.com, cdn.sstatic.net, www.cloudflare.com, chatgpt.com, claude.ai, gemini.google.com, www.perplexity.ai, grok.com, copilot.microsoft.com, www.reddit.com, www.instagram.com, x.com, www.linkedin.com, discord.com, www.tiktok.com, www.youtube.com, www.netflix.com, www.twitch.tv, www.disneyplus.com, store.steampowered.com, open.spotify.com, www.bbc.com, telegram.org. These sites receive the source IP address and standard network information;
• after you start the Speed Test, your browser exchanges test data with Cloudflare's speed test server at speed.cloudflare.com, which receives the source IP address and the test requests. Cloudflare collects the speed test results;
• when you open the Global Ping and MTR page, your browser asks Globalping (api.globalping.io) for the test quota your IP has left; after you start a measurement, your browser sends its target, type and region straight to Globalping, whose probes run it, and Globalping receives your IP address and these parameters. Globalping stores measurement targets and results publicly, as described in the Globalping terms and privacy policy;
• when you open the WHOIS and Network Ranges page, your browser looks up your current IP; for each IP, range or ASN you look up, it first reads IANA’s RDAP bootstrap files (data.iana.org) and then sends the object straight to the responsible regional registry (ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC, or a national registry it refers to) and to RIPEstat (stat.ripe.net, for the announced prefix, RPKI status, BGP paths, routing visibility and the names of the ASes on those paths), which receive your IP address and the object; these lookups do not pass through or get stored by this site;
• when you look up a domain on the DNS Lookup Comparison page, your browser sends the name and record type straight to Cloudflare (cloudflare-dns.com), Google (dns.google) and AliDNS (dns.alidns.com), which receive your IP address and the name; the IP and Subnet Calculator works only in your browser and sends nothing;
• when you open or rerun the Network Checkup, your browser makes the requests described above for the My IP and Dual Stack, Exit and Split Routing, DNS Location, WebRTC, AI Region and Claude China User checks, asking each source once per run; the page reads your time zone and language, and sends each of www.baidu.com, www.bilibili.com, www.google.com, www.cloudflare.com, chatgpt.com, claude.ai, github.com, www.youtube.com, weixin.qq.com, chat.deepseek.com, x.com, www.netflix.com a few such requests as the Reachability and Latency test does. For the exit IP most websites see, the checkup also runs one IPLense Quick lookup (as in Quick mode, verified by Cloudflare Turnstile and counted against the lookup limits; a rerun with the same exit in the same page does not look it up again), and, as the WHOIS and Network Ranges page does, sends that IP to IANA (data.iana.org), to the responsible regional registry's RDAP service (ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC, or a national registry it refers to) and to RIPEstat (stat.ripe.net) for its announced prefix, RPKI status, the prefix's BGP paths and routing visibility; with split routing, the other exit is looked up only after you click. As the DNS Lookup Comparison page does, the checkup also sends A-record queries for chatgpt.com, google.com, youtube.com, github.com and baidu.com to Cloudflare (cloudflare-dns.com), Google (dns.google) and AliDNS (dns.alidns.com), which receive your IP address and these names. Of the manual items, the speed test runs only after you start it and is handled as on the Speed Test page; Global Ping runs only after you click it, when your browser sends the exit IP as the target, with the type and region, to Globalping (api.globalping.io), handled as on the Global Ping page; opening the checkup does not read the quota; and
• email service providers process messages you choose to send to our support or sales address.

Your connection details, reverse DNS, ASN size, and results from the network checkup and the public IP, exit, reachability and latency, Cloudflare connection, AI region, speed, DNS, WebRTC, browser fingerprint, Claude region-signal and global ping tests, and WHOIS, DNS comparison and IP calculator results, remain only in the current page's memory. They are not uploaded to IPLense or written to a database, localStorage, sessionStorage, or server logs. Other third parties handle data under their own privacy policies.

Command-line self-check (CLI)

When you run bash <(curl -sL https://iplense.cc/cli) on a server:

• downloading the script, Cloudflare and this site receive the machine's IP address and curl's User-Agent;
• for the self-check, this site receives one request per IP family with the X-IPLense-CLI and X-IPLense-Family (the family used, 4 or 6) headers and the User-Agent IPLense-CLI/version. It looks up only the IP the request comes from, through the IP data providers and with the result kept as for a lookup on the website; one IP's result is reused for an hour. The script sends no host name, system or hardware details;
• the local checks go straight from that machine to the platforms checked: ChatGPT (chatgpt.com), Claude (claude.ai), Gemini (gemini.google.com), Netflix (netflix.com), Disney+ (Disney's bamgrid.com service), YouTube (youtube.com), TikTok (tiktok.com), Prime Video (primevideo.com) and Reddit (reddit.com), one to three ordinary requests each; they receive the machine's IP address and a browser-style User-Agent. The Disney+ check registers an anonymous device with Disney's service, sending only a generic device description. The script does not log in or submit account details;
• the port 25 check opens one connection to Gmail's mail server (gmail-smtp-in.l.google.com), reads its greeting and ends; no mail is sent;
• from version 1.2, the script generates a report by default and sends this site the temporary self-check tokens, client version, language, the status and region for nine platforms, the port 25 status, and whether the platforms see a different exit and its masked IP. The site combines these local checks with its self-check results and stores only masked results: the last two IPv4 octets and the last five IPv6 groups are hidden. Reports are retained for 30 days, become unavailable at expiry and are deleted by the daily cleanup. Anyone with the report link can view it. Use -p or -j to skip report creation; local check results are then not sent to this site.

Retention

• Quick Check and Professional Check results and provider observations saved before this retention policy took effect are retained as fixed historical evidence;
• new Quick Check and Professional Check results created after the policy took effect are usually retained for no more than six calendar months;
• new provider observations created after the policy took effect are usually retained for no more than twelve calendar months;
• access, security, and error logs are retained as needed for operations, security, and troubleshooting;
• Turnstile tokens are used only for the current verification and are not reusable lookup credentials;
• email correspondence is retained as needed to complete support, corrections, business discussions, and necessary recordkeeping; and
• records may be retained for longer where required for legal obligations, disputes, or security investigations.

Data security

IPLense uses access controls, encrypted transport, credential separation, rate limits, and operational auditing to protect data and the service.

Your choices

You can clear local lookup history from the search panel, clear the current result from its result card, and change your language preference from the header menu. To ask about related data we hold, suggest a correction, or request deletion, email [email protected] with enough information to identify the record. We will handle the request in line with applicable requirements and any records legitimately needed to operate the service.

Policy updates

If IPLense makes a material change to its features, data handling, or third-party services, we will update this policy and the effective date shown on this page.

Contact

Data suggestions, result corrections, and support: [email protected]
Quick Check API business inquiries: [email protected]