Site terms
Terms of use
Last updated: July 5, 2026. These terms explain how PageMine.xyz may be used and what limitations apply. By using the site, you agree to use it only as a lawful browser diagnostics and utility service.
Purpose of the site
PageMine.xyz helps you inspect the public IP, approximate network metadata, browser/device signals, local fingerprint signals, WebRTC behavior, request headers, approximate speed to the current deployment and local generator outputs for the browser session you are using.
The tools are informational and educational. They are not designed to identify a person, prove a legal identity, certify VPN/proxy/Tor status, detect fraud, provide security certification or replace professional advice.
Use only for your own session
You may use the site to understand your own browser, your own connection, your own VPN/proxy setup, your own development environment or a device/session you are authorized to test. Do not use the site to mislead people, impersonate others, collect data from others without permission, attack systems or violate laws.
Accuracy limits
IP, ISP, ASN, geolocation, timezone comparison, WebRTC and fingerprint results are signals. They can be incomplete, stale, randomized, blocked, approximated or affected by browser settings, privacy extensions, VPNs, proxies, mobile carriers, CDN routing, NAT, corporate gateways and hosting-provider headers.
Speed-test results are approximate and depend on many conditions, including browser load, Wi-Fi, device performance, VPN/proxy use, Vercel region, cache/CDN behavior, network congestion and endpoint availability.
How the tools operate
Browser and fingerprint values are read in the browser through standard web APIs. The IP endpoint reads request metadata available to the deployment. Speed test endpoints exchange test payloads with this deployment. Generators run locally in the browser in the intended workflow. The removed browser-side ISP fallback is not part of this build. More detail is available in the Privacy policy and Data transparency page.
Acceptable use
You may use the site for personal diagnostics, browser comparison, proxy/VPN comparison, development testing, accessibility review, privacy education and troubleshooting. You must not abuse the speed endpoints, automate excessive requests, bypass rate limits, attack the deployment, overload lookup providers, scrape at scale or use the site to violate another person's rights or systems.
Generated content and secrets
Generated passwords, QR content and TOTP codes are your responsibility. The site does not guarantee that generated values satisfy every account policy, compliance standard or security requirement. Do not paste secrets into any website unless you understand the risk and trust the device, browser, page context and extensions installed in that browser.
The local-generator design is a privacy measure, not a guarantee against every device-level or browser-level risk. Malware, malicious extensions, screen recording, shared computers, browser autofill, clipboard history and future third-party scripts can create risks outside this project's intended workflow.
No account, no custom user database
This build does not provide user accounts and the project code is designed not to write IPs, fingerprints, generated passwords, QR text, TOTP secrets or speed-test results into a custom project database. Normal hosting, CDN, DNS, security and function logs may still exist as part of infrastructure operations.
Third-party services
The deployment platform may process access, edge, security and function logs as part of hosting. Server-side external network lookup, if enabled in the IP endpoint, is limited to ipinfo.io first and ipwho.is as fallback. Those providers operate under their own policies and may receive request metadata from the backend request made by the deployment. This build does not include a browser-side toggle that directly calls third-party IP lookup providers from the visitor's browser.
If advertising, analytics, consent-management tools, monitoring tools or other third-party scripts are added later, the operator should update the Privacy policy before enabling them.
Public deployments of this code
If you deploy or modify this code publicly, you are responsible for reviewing the Privacy policy, these Terms, endpoint behavior, provider terms, CSP, rate limits, logs, consent requirements, advertising rules and any local laws that apply to your deployment. Do not claim that no data is processed if your hosting provider, API routes or third-party providers receive technical request data.
Availability and changes
The site may change, break, return partial data, be rate limited, lose provider headers, become unavailable or update lookup providers without notice. Layouts, copy, endpoints, API behavior and provider dependencies may change as the project is improved.
No warranty
The site is provided as is and as available, without warranties of accuracy, availability, uninterrupted operation, security, fitness for a particular purpose or non-infringement. Use the results as diagnostic hints, not as the sole basis for critical decisions.
Limitation of responsibility
To the maximum extent allowed by applicable law, the operator is not responsible for losses caused by reliance on approximate diagnostics, unavailable endpoints, third-party provider behavior, hosting logs, browser bugs, extension behavior, clipboard behavior, generated values, incorrect geolocation, incorrect VPN/proxy assumptions or your misuse of the site.
Privacy policy controls
The Privacy policy is part of the user-facing explanation of how the site works. If these Terms and the Privacy policy conflict on a data-handling detail, the more specific privacy explanation should be used for that data-flow question.
Contact and review
If you operate a deployment of this code, add a real contact channel before public launch. Users should contact the operator of the specific deployment they are using for privacy or legal questions.