Safe output avoids exact IP values, full user-agent strings, fingerprint hashes, raw DNS/WebRTC payloads, and exact local network details.
Safe diagnostic summary
Run the test, Use Safe Copy.
A Safe Copy is the MyIPScan way to keep a reduced, share-safe summary of a browser/session check. It helps you compare before and after VPN, DNS, WebRTC, IPv6, or network changes without copying sensitive raw diagnostic details.
No raw IP in exports
No exact city
No full user-agent
No raw DNS/WebRTC data
Safe Copy across reports
Use the receipt layer before sending a report to someone else
Public Exposure Report, Website Exposure Scanner, Email Deliverability Doctor, AI/Search Visibility Scanner, and Domain Intelligence Report all keep the diagnosis and next steps, while Safe Copy removes raw values that are easy to overshare.
Safe output keeps HTTP, DNS, and fix context while avoiding raw headers, cookies, tokens, credentials, and oversized response details.
Safe output keeps domain-level authentication findings while avoiding private mailbox local-parts, raw DNS payloads, and raw sender-IP context.
Safe output keeps registrar/status/network context while suppressing raw payloads and RDAP contact personal data.
What makes it different
A receipt is useful because it is reduced on purpose
Most IP and VPN leak pages show a result and stop there. MyIPScan adds a safe receipt layer so users can retest, compare, and share context without carrying raw technical identifiers into chats, support tickets, screenshots, or notes.
| Receipt field | Can appear in safe receipt | Removed from safe receipt |
|---|---|---|
| IP signal | Route category, IP version, network category, review flag | Raw IPv4, raw IPv6, exact address strings |
| Location | Approximate country/region category where useful | Exact city, latitude, longitude, street-level claims |
| Browser | Browser family category and relevant privacy flags | Full user-agent and raw fingerprint values |
| DNS | Resolver category, mismatch flag, limited explanation | Raw resolver IPs and raw provider response payloads |
| WebRTC | Candidate category such as masked, local, public, or limited | Raw ICE candidate strings and raw local network data |
| Meaning | Limits, confidence, related checks, methodology link | Anonymity guarantees, provider certification, permanent safety claims |
Start with the tool that matches the question: IP, VPN leak, DNS leak, WebRTC leak, IPv6 leak, or browser fingerprint.
Reconnect VPN, change DNS, switch browser, or move from Wi-Fi to mobile data, then run the same check again.
Use the reduced receipt for your own notes or support context without exposing raw IP, exact city, full user-agent, raw DNS/WebRTC data.
A receipt is a snapshot for this browser and session. It is not proof every app, device, browser profile, or future connection is protected.
Run, save, compare
Create a Safe Copy from a live test
Choose the check that matches your question, run it, then use the receipt actions on the result page. For VPN troubleshooting, save a before result, connect or change the VPN, re-test, and copy the safe receipt.