IP route
Public IP and broad network context appear after the scan.
Live scan ready
Public Exposure Report
One browser-session report for IP route, DNS route, WebRTC, IPv6, browser fingerprint, and a Safe Privacy Receipt.
Use it to review what is visible from this browser/session, then share a reduced receipt instead of raw private details. Results are review signals, not a certification.
6 signals in one readable route map
Safe Receipt removes raw sensitive values
Clear limits for what the report can suggest
Result summary
Your route map in one card
Target: Preview / no live target
Run Public Exposure Report to fill the summary card.
DNS route
Resolver signal review appears after the scan.
WebRTC
Candidate behavior appears after the scan.
IPv6
IPv6 visibility appears after the scan.
Browser fingerprint
Browser signal groups appear after the scan.
Safe Receipt
Safe Copy becomes available after a report is generated.
After the scan, use Safe Receipt from this report.
It keeps the diagnosis, top issues, and fixes while removing raw identifiers that do not belong in tickets or client chat.
Top risks second
Top Issues First
Maximum three issues are shown here.
Choose a scan type to start.
Run a browser scan to check this device/network, or scan a public domain for website, email, domain, and AI/search signals.
Share safely
Safe Privacy Receipt
Status: Not checked
Receipt target
Run a report first
Safe Receipt is prepared after the report has enough visible session or public-target data.
Removed from Safe Copy
- Exact public IP values and exact city-level details
- Full User-Agent strings and fingerprint hash fields
- Raw headers, cookies, tokens, API keys, and authorization values
- Raw DNS payloads and raw WebRTC candidates
Kept for review
- Conservative status labels such as Visible, Review, Limited, and Not checked
- Top issues, recommended next steps, and confidence notes
- Broad route context such as IP version, network summary, and signal counts
- Clear limits that say the report is not a certification
Full report copy can include raw values. Use Safe Receipt for support tickets, public chat, client updates, or screenshots.
Lead magnet
Safe Privacy Receipt for support and client updates
The free report stays browser/session-first. For teams, the natural next step is a reduced Safe Receipt and, later, approved public-domain monitoring beta review.
One-time scans are free. Monitoring beta is optional, requires approved public targets, and does not mean public signup, automatic alerts, billing, or dashboards are live. See How We Make Money and the Affiliate Disclosure.
Clear limits
What this report can and cannot prove
Use it as a review signal, not a final certification.
What it can suggest
- Which browser/session signals are visible right now.
- Whether IP, DNS, WebRTC, IPv6, and fingerprint signals need review together.
- Which focused MyIPScan tools are the next closest checks.
- Which reduced Safe Receipt is safer to share than raw details.
What it cannot prove
- It cannot certify anonymity, VPN behavior, what every provider can see, or total protection.
- It cannot inspect every app, device, browser profile, network, or future connection.
- It cannot guarantee email deliverability, search indexing, AI citation, or crawler behavior.
- It cannot replace formal security testing or provider-side logs.
Advanced result details
Details, fixes, and limitations
Collapsed by default so the report stays readable.
Recommended fixes and report areas
Run a scan to see which report checks are available.
Privacy Exposure
Checks browser and network signals such as IP, DNS leak, WebRTC, IPv6, fingerprint, and user-agent exposure.
Website Exposure
Checks public website signals such as SSL/TLS, redirects, security headers, HSTS, DNS, and CDN/origin exposure.
Email and AI/Search
Advanced public-target scans can include email authentication and AI/search visibility signals when supplied.
Technical details
Limitations
Exposure estimate, not a guarantee
This report is an exposure estimate. It cannot certify security, privacy, deliverability, or search visibility.
Signals can change
Some signals depend on browser behavior, DNS propagation, network position, crawler behavior, and third-party services.
Safe sharing matters
Use Safe Copy before sharing results. Safe reports should remove raw sensitive values such as exact IPs, raw user-agent strings, fingerprint hashes, tokens, cookies, and raw headers.
Check my browser/privacy
What this checks
Visible browser-session signals across IP route, DNS route, WebRTC, IPv6, fingerprint traits, user-agent, and Safe Receipt readiness.
Limits
What this cannot check
It cannot certify anonymity, inspect every app, audit every VPN route, prove account safety, or guarantee that future sessions stay the same.
Read results
How to interpret results
A good result means the main signal groups align with the route and browser behavior you expected, and the report shows no high-priority unexpected exposure flags.
Warnings
What a warning means
A warning means one signal deserves review. It should be compared with related checks before making security, account, or VPN decisions.
Fix path
What to do next
Open the focused test for the flagged signal, change one setting, then rerun the report to compare IP, DNS, WebRTC, IPv6, and fingerprint changes.
Retest
When to retest
Retest after VPN, DNS, browser, extension, network, profile, OS, or router changes, and use Safe Copy when sharing the reduced result.