Public IP observed by MyLeaks

Loading…

Checking… Checking connection

JavaScript is required to run browser-local measurements and display their results. The page structure, explanations, navigation, and links remain available without JavaScript.

Privacy Summary

See what your browser and network reveal

Checking

Checks are still completing

Review the completed checks and open any item that needs attention.

What should I pay attention to?

Waiting for evidence

Important findings will stay visible here even when technical details are collapsed.

Current checks

Waiting for structured test results…

Test coverage

0 of 10 measurement groups produced a result

10 groups are still checking.

View all result explanations and evidence

Guide

Detailed interpretation

Exact evidence, limitations, and why each observation may matter

Open any result to see what was tested, what it means, and when it matters.

Network Privacy

Addresses and networks visible to the tests

How these tests work →

Human-readable outcomes come first. Addresses, candidates, network indicators, and resolver records remain available under technical details.

IP & network

Loading…

Public IP checking…

Country: Checking…
Network / ASN: Checking…
Network type: Checking…
VPN classification: Loading…
Proxy classification: Loading…

IP location is approximate. Open the focused public-IP view or review VPN and proxy indicators.

IP intelligence technical details

Location evidence

Country: Loading…
Region: Loading…
Estimated city: Loading…
Estimated IP timezone: Loading…
Approximate coordinates: Loading…
IP location accuracy radius: Loading…

Network evidence

ASN: Loading…
AS organization: Loading…
Network type: Loading…
ISP: Loading…
Network domain: Loading…

Additional classifications

Residential proxy: Loading…
Tor: Loading…
Hosting: Loading…

Additional indicators

Risk indicator: Loading…
Proxy confidence evidence: Loading…
Proxy first observed: Loading…
Proxy last observed: Loading…
Likely network operator: Loading…

WebRTC

Testing…

Direct public WebRTC candidates are compared with the main HTTPS address. A mismatch shows that the connections used different public paths. Open the focused WebRTC comparison.

HTTPS public IP: Testing…
WebRTC public IPs: Testing…
Public IP difference: Testing…

WebRTC technical details

Local address: Testing…
STUN: Testing…

Host candidates: 0
Server-reflexive: 0
Relay: 0
Total: 0

Relay candidates are shown but excluded from direct public-IP mismatch comparison.

Waiting for ICE candidates…

ICE candidate errors

Waiting for ICE gathering…

DNS

Testing…

Resolver results show which DNS networks handled the test names. Open the focused DNS resolver check.

Observed resolver addresses: 0

DNS resolver technical details

HTTPS public IP: Testing…
Observed probes: 0

Observed DNS resolver

Waiting for DNS observations…

Full resolver records

Waiting for DNS observations…

QUIC public-IP comparison

Checking

QUIC public-IP comparison is being checked

When HTTP/3 is available, MyLeaks compares its public path with the main HTTPS connection.

Full QUIC and HTTP/3 fingerprints are grouped under Advanced network fingerprints.

Browser & Device

Compact browser and connection context

Browser and platform checking…

Connection details checking…

Display and timezone checking…

Hardware details checking…

Show browser, device, connection, privacy, and consistency details

Connection

Observed by this HTTPS connection

Public IP: Loading…
IP version: Checking…
TLS version: Loading…
TLS cipher: Loading…
HTTP protocol: Checking…
User-Agent: Loading…
Accept-Language: Loading…
Low-entropy Client Hints: Loading…

Browser

Browser-reported and conservatively derived

Reported browser: Checking…
Reported version: Checking…
Reported platform: Checking…
Timezone: Checking…
Primary language: Checking…
Languages: Checking…
User Agent Client Hints: Checking…
Raw User-Agent: Checking…

Device

Values exposed by the browser

Screen resolution: Checking…
Available screen: Checking…
Device Pixel Ratio: Checking…
Color depth: Checking…
Pixel depth: Checking…
CPU logical cores: Checking…
Approximate device memoryBrowser-reported approximate value.: Checking…
Touch support: Checking…
Max touch points: Checking…

Privacy & Storage

Current browser settings and availability

Cookies: Checking…
LocalStorage: Checking…
SessionStorage: Checking…
Do Not Track: Checking…
Global Privacy Control: Checking…

Automation

Basic directly observable signal only

WebDriver exposed: Checking…

This value reports the browser automation flag as exposed on this page.

Consistency comparisons

Conservative comparisons over evidence already collected in this page load

Consistent: 0
Compatible: 0
Warnings: 0
Mismatches: 0
Informational: 0
Unknown: 0
Checking: 11

These counts describe rule results. They are not a score and are not weighted. Important warnings also remain visible in the Privacy Summary.

Network

Browser

Rendering & Automation

Open a mismatch or warning to see which values differ.

Browser Fingerprint

Same-page surface measurements

Stability describes repeated measurements during this page load. Open the focused seven-surface test →

Checking

Availability: 0 surfaces available
Same-page stability: 0 stable during this page load
Repeated measurements: 0 changed between repeated measurements

Seven surfaces are still being checked.

Show all browser fingerprint surfaces and hashes

Tested: 0 / 7
Available: 0
Unavailable: 0
Unstable: 0

Each surface is measured twice so you can see whether it remains stable during this page load.

Canvas

Loading…

Fixed text and graphics rendering are measured twice.

Same-page result: Checking…
SHA-256: Checking…

Technical details

Waiting for measurement…

WebGL

Loading…

Graphics rendering and browser-reported GPU characteristics are measured.

Same-page result: Checking…
SHA-256: Checking…
Version: Checking…
Reported vendor: Checking…
Reported renderer: Checking…
Unmasked vendor: Checking…
Unmasked renderer: Checking…

Technical details

Waiting for measurement…

GPU information

Loading…

Browser-reported graphics values may differ from the exact physical GPU.

WebGL vendor: Checking…
WebGL renderer: Checking…
WebGPU vendor: Checking…
WebGPU architecture: Checking…

ANGLE, SwiftShader, or software rendering is shown factually and is not marked suspicious.

WebGPU

Loading…

Adapter capability data is measured without a permission prompt or benchmark.

Same-page result: Checking…
SHA-256: Checking…
Reported vendor: Checking…
Reported architecture: Checking…

Technical details

Waiting for measurement…

Audio

Loading…

Silent offline audio processing is measured twice.

Same-page result: Checking…
SHA-256: Checking…

Technical details

Waiting for measurement…

Fonts

Loading…

The browser-visible set of tested local fonts is measured twice.

Same-page result: Checking…
Detected: Checking…
SHA-256: Checking…

Technical details

Waiting for measurement…

ClientRects

Loading…

Fixed DOM geometry is measured twice.

Same-page result: Checking…
SHA-256: Checking…

Technical details

Waiting for measurement…

Text Metrics

Loading…

Canvas text metrics for fixed text and fonts are measured twice.

Same-page result: Checking…
SHA-256: Checking…

Technical details

Waiting for measurement…

Advanced Network Fingerprints

Connection characteristics for technical review

Methodology and limitations →

These are connection observations, not personal identities. Many clients can share them and intermediaries can alter them.

TLS / JA3 / JA4: Checking
HTTP/2 / myleaks-h2-v1: Checking
HTTP/3 / myleaks-h3-v1: Checking
QUIC / myleaks-quic-v1: Checking
TCP / myleaks-tcp-v1: Checking

Show TLS, HTTP/2, HTTP/3, QUIC, and TCP technical details

TLS

TLS Client Fingerprint

ClientHello observed for this connection

Observing…

JA4

Checking…

JA3

Checking…

TLS ClientHello

Versions offered: Checking…
Cipher suites: Checking…
Extensions: Checking…
ALPN: Checking…
SNI: Checking…

Technical raw values

Waiting for the dedicated TLS connection…

Interpretation: JA3 and JA4 summarize offered TLS features. Many clients can share them, and middleware can change them.

HTTP/2 Client Fingerprint

Direct initialization observed on dedicated TCP port 8443

Testing…

Protocol

Checking…

MyLeaks H2 fingerprint

Checking…

Observed HTTP/2 behavior

SETTINGS: Checking…
Connection window update: Checking…
Initial frames: Checking…
Pseudo-header order: Checking…

Technical raw values

Waiting for the direct HTTP/2 connection…

Interpretation: SETTINGS, frame ordering, flow control, and header ordering can be fingerprinting signals. The project-defined hash is not a unique identity.

QUIC / HTTP3

Direct HTTP/3 client characteristics and public network path over UDP/443

Testing…

Protocol & network path

Protocol: Checking…
QUIC public IP: Checking…
Network path: Checking…
QUIC version: Checking…

MyLeaks QUIC fingerprint

Checking…

Algorithm: myleaks-quic-v1

MyLeaks HTTP/3 fingerprint

Checking…

Algorithm: myleaks-h3-v1

Observed protocol characteristics

Transport parameters: Checking…
HTTP/3 SETTINGS: Checking…

Technical raw values

Waiting for the direct HTTP/3 connection…

Interpretation: Transport parameters and settings describe this connection. Many clients can share them; proxies or middleware can block or alter them.

TCP

TCP Connection Characteristics

Passive IPv4 initial-SYN characteristics on the existing HTTPS connection

Observing…

MyLeaks TCP fingerprint

Checking…

Algorithm: Checking…

Initial TCP SYN

Window: Checking…
MSS: Checking…
Window scale: Checking…
SACK permitted: Checking…
Timestamp option: Checking…
TCP Fast Open: Checking…
ECN flags: Checking…
IPv4 DF: Checking…

TTL observation

Observed TTL: Checking…
Estimated initial TTL: Checking…
Estimated hops: Checking…

Initial TTL and hop count are heuristic estimates excluded from the fingerprint hash.

Technical raw values

Waiting for the HTTPS connection SYN…

Interpretation: This is myleaks-tcp-v1, not JA4T. It summarizes the initial TCP characteristics observed for this connection.