Free Tool · VISION §2.2 Parity · Zero Logging

IP Lookup, Fraud Score & Proxy Leak Test

Inspect your public egress IP address, carrier/ASN metadata, connection classification (Residential, Mobile, or Datacenter), and audit DNS and WebRTC leaks in real time.

Detected Public IPResidential Exit

203.0.113.195🇺🇸

Chicago, Illinois, United States · America/Chicago

Direct Connection (Simulated)

Testing against your local unmasked egress

ASN & Organization: AS7922; Comcast Cable Communications, LLC
ISP / Carrier: Comcast Cable; Postal Code: 60601
Geo Coordinates: 41.88, -87.63; US
Fraud / Proxy Score: 8 / 100 (Clean); Stealth verified

Security & Privacy Audit

Vulnerable to Leaks

Auditing whether your real local IP or ISP identity is exposed to destination web servers.

DNS Leak Protection

Resolver: 75.75.75.75 (Comcast Regional ISP DNS)

LEAK DETECTED

WebRTC Leak Protection

Host candidate leaked: 192.168.1.105 (Local LAN host candidate)

LEAK DETECTED

Hop-by-Hop & Proxy Headers

Unsanitized direct browser headers

RAW

Threat Intelligence & Reputation

T-080 Abuse Sync

Scanned against live in-memory threat feeds (Spamhaus DROP/EDROP, AbuseIPDB, C2 botnets).

Spamhaus DROP / EDROP

Clean (0 listings)

Not in bulletproof subnets

AbuseIPDB Confidence

0% Abuse Score

Zero malicious reports

Tor Exit Node

Negative

Standard residential egress

Fail-Closed Anti-SSRF

Active

RFC 1918/6598 filtered

Simulate or Lookup Custom IP:

Test from Terminal via cURL

Execute a live probe through the Sovereign Gateway using compound username targeting.

Country

City

Session ID

curl -x http://gate.sovereignip.com:8000 \
  -U "demo-product-residential-country-us-city-newyork-session-checkout-1:demo_key" \
  https://sovereignip.com/tools/ip

Frequently Asked Questions on IP Intelligence

How does Sovereign prevent WebRTC and DNS leaks?

When using Sovereign residential or mobile proxies, your DNS queries are securely resolved at the edge PoP using DNS-over-HTTPS (DoH) with zero logging. For browser sessions, WebRTC STUN candidate harvesting is masked at the socket layer to ensure your internal local IP (e.g. 192.168.x.x) is never revealed to destination websites.

What is the difference between Residential and Datacenter fraud scores?

Datacenter IPs belong to hosting providers (AWS, DigitalOcean, Hetzner) and are easily flagged by Akamai, Cloudflare, and DataDome with high fraud risk scores (>60). Sovereign residential and mobile IPs originate from genuine consumer ISPs (Comcast, AT&T, Verizon, Vodafone), achieving a low fraud score (0–10) and highest unblock rates.

How does the compound username grammar work?

Sovereign encodes targeting parameters directly into the proxy username string (e.g., demo-product-residential-country-us-city-newyork-session-checkout-1). This allows granular session stickiness, country/city/ASN filtering, and carrier selection without maintaining multiple gateway hostnames.