Privacy scan

Choose what to inspect. See each source, result and coverage limit in one place.

Run a browser privacy scan

Choose the checks you want to run. Each item explains its destination and scope. Nothing starts until you request it; this page does not calculate a privacy score.

Choose checks and advanced options

This browser and connection

Refresh the public address visible to this site. This is one path from this browser.

Source: MyIP.dog /api/v1/ip

Make two direct HTTPS requests. Each provider sees the source address and normal request metadata; an unavailable family stays unknown.

Source: api.ipify.org and api6.ipify.org

Create a temporary peer connection and contact Cloudflare STUN. Candidate gathering stops after 12 seconds; no media is captured.

Source: Browser ICE API; stun.cloudflare.com:3478

Read supported browser, screen and preference fields locally. No browser report is uploaded. Graphics are a separate choice.

Source: Browser APIs; browser-signals-v1

Requires Browser signals. Runs a fixed local graphics sample; no images, hashes or graphics values are uploaded.

A specific public IP address

Required for reverse DNS, mail blacklists or TCP checks. These results describe this target, which may differ from your browser’s connection.

This button makes one request to this site and fills the address. A shared, VPN or gateway address may belong to another operator.

Send the target’s reverse DNS question through this site to Google Public DNS. No connection is made to the target.

Source: Google Public DNS via this site

Check SpamCop and PSBL through Google Public DNS, including source health controls. Queries disclose the target address to these systems.

Source: SpamCop SCBL / PSBL via Google Public DNS

Make bounded connection attempts from this site to the target. Requires separate permission confirmation; the target can log these attempts.

Source: Site TCP probe; shared diagnostic budget

TCP only: 22, 25, 80, 443, 3389, 8080. Up to six server-side attempts, one at a time; no application payload. Existing shared quotas apply. No automatic port sweep.

Choose checks to begin.

What this scan does not cover

DNS resolver exposure, VPN/proxy/Tor classification, remote IP geolocation, breach exposure, TLS certificate chains and other device/application traffic are not checked. Those gaps remain untested even when every selected item finishes.

Choose observations, then interpret their scope

  1. Select the question

    Choose browser checks, target checks, or both.

  2. Review destinations

    Read local collection and external service disclosures.

  3. Run independent checks

    Preserve each component’s evidence and collection state.

  4. Act on specific findings

    Read differences, listings and TCP outcomes without a privacy score.

Browser and target checks have different data flows. The diagram explains the selected workflow; it does not imply all checks run automatically.
On this page

Learn more about Privacy scan

Choose the scope of your privacy scan

A privacy scan collects selected browser, connection and public-target observations in one report. Choose only the checks that answer your question, review their sources and start deliberately. Opening the page does not begin a scan.

Read more

Browser privacy checks describe this browser and its connection. Target checks describe the public IP you enter, which may belong to a server you administer. Their contexts remain separate.

Targets require one public IPv4 or IPv6 literal. Use connection IP fills a fresh site observation without granting authority to probe it. Changing or refilling the target resets TCP permission confirmation.

Consent and destinations for network privacy checks

Site IP contacts this website; family checks contact ipify directly; WebRTC uses Cloudflare STUN and the browser ICE API. Each selected destination can observe protocol-related metadata.

Browser signals are read locally. Canvas and WebGL require an additional choice. Reverse DNS and mail-list queries travel through our server to Google Public DNS; TCP connections originate from our server.

TCP requires explicit confirmation for a target you own, administer or are authorized to test. A VPN exit or shared gateway may belong to another operator; an observed address does not establish authority.

Read a privacy scan one component at a time

Every component shows its state. Not selected means it did not run; Complete observation means expected evidence arrived within that scope, not that privacy passed. The summary counts selected checks completed.

Read more

Partial, unsupported, unavailable, cancelled and timed-out work stays visible. One failed source does not erase another’s useful evidence, and missing replies do not explain their own cause.

Site and address-family observations

Site IP records this website’s observed address, family and time. It does not identify a specific device behind a shared connection or a household location.

Family checks request separate IPv4 and IPv6 HTTP observations. A missing IPv6 result means no valid response on that path, not that every application lacks IPv6.

WebRTC evidence and its limits

WebRTC creates a temporary peer connection for gathering, without camera, microphone, media tracks or a remote peer session. Resources close when collection ends.

Compare only public non-relay candidates with same-family HTTP observations from this run. A manually entered target is never a reference for your browser. Missing references remain unperformed or inconclusive.

Matching available candidates cannot certify every route. Differences need context; errors or incomplete gathering retain uncertainty. mDNS names are not resolved, and detailed exports omit their identifiers.

Browser signals and optional graphics

Browser values have available, blocked, unavailable and not-run states. Optional graphics are local observations. There is no representative population, uniqueness percentage or persistent visitor identifier.

Target reverse DNS and mail-list evidence

PTR evidence includes resolver, response code and returned names. An operator-supplied name is not verified identity, exact location or proof of service. No PTR answer is not automatically a fault.

Mail checks use SpamCop and PSBL with positive and negative controls. They concern named mail-list policies, not complete fraud, malware or personal-reputation coverage.

These integrations do not cover IPv6. Failed controls, unexpected answers and resolver failures remain unknown. Read the mail blacklist checker for source-specific interpretation.

Deliberately selected TCP checks

TCP checks use the fixed common preset: 22, 25, 80, 443, 3389 and 8080. Attempts are sequential, bounded and made from this server. No logins, software detection or exploit run occurs.

Open means a TCP connection completed on that path. Refusal, timeout, unreachable, restricted and unavailable are distinct. A common port label is an association, not a verified application.

Stop, clear and share a privacy scan

The overall deadline is forty-five seconds; components have shorter limits, including twelve-second WebRTC gathering. No automatic retry starts another measurement.

Read more

Stop preserves returned observations and cancels pending work. Clear removes results, target, selections and confirmation. Hiding the tab or leaving also discards working data; late responses cannot restore it.

The privacy report defaults to coverage, states, times and counts, omitting addresses, PTR names and browser values. Detailed export is an additional deliberate choice; inspect it before sharing.

Detailed reports can contain target and observed addresses, DNS records, configuration and graphics. They omit raw session descriptions and mDNS identifiers. No report is added to URL parameters, browser storage or tool analytics; clipboard retention is separate.

Understand what remains outside the privacy scan

Coverage gaps include authoritative DNS resolver-exposure evidence, VPN/proxy/Tor classification, remote city geolocation, breach records and full TLS chains. Other applications, provider logging and account security require separate evidence. Completed selected checks do not fill these gaps.

Questions about the privacy scan

Can I run only local checks?

Yes. Select Browser signals and leave the network and target components unchecked. Optional graphics remain a separate choice. The privacy scan then collects that local evidence without starting its IP echo, STUN, DNSBL, PTR or TCP measurements. Ordinary page delivery and site analytics remain separate, as described in the privacy policy.

privacy policy

Should I change my network settings after one result?

First confirm what the privacy scan actually observed, its source and its limits. Repeat a relevant component deliberately when conditions are stable, or use the linked specialist tool to understand the result. This page organizes evidence; it does not prescribe a universal configuration change based on a missing field or a single unsuccessful probe.

Why is there no overall privacy score?

A browser signal, a mail listing and a successful TCP connection have different meanings and denominators. Adding them into one percentage would invent a relationship that the evidence does not establish. Start with the specific question you selected, read that component’s finding, then decide whether it differs from your intended configuration.

Which checks stay local, and which contact services?

Browser configuration and selected graphics reads are local. Site-IP, ipify and STUN checks contact their named endpoints from your browser. PTR and mail-list questions pass through this server to Google Public DNS. Selected TCP attempts originate from this server. Read the source beside each option before choosing it; the whole scan is not an offline inspection.

Can an entered server address be used as my VPN baseline?

No. An entered target belongs only to PTR, mail-list and authorized TCP questions. It may be a server unrelated to your current browser. WebRTC comparisons use matching-family HTTP observations gathered from this browser in the same run. When those references are missing, the tool keeps the comparison incomplete instead of substituting the manually entered target.

Does the copied privacy report include every observed address?

No. The default copy emphasizes coverage, states, times and counts while omitting addresses, PTR names and browser values. Detailed export is a separate deliberate choice. Review that content for identifiers before sending it to someone else.

Do stopped network privacy checks count as successful?

No. Returned evidence stays visible, while cancelled, unavailable and incomplete components retain their states. Interpret each component’s coverage independently; a useful local observation does not convert an unfinished network check into a result.