UrMomsVPN Proxy

Route this browser's traffic through your own UrMomsVPN console-proxy relay — the same infrastructure already used for iPhone, PlayStation, and Xbox proxy setups. This is a real forward proxy, not a status widget: once connected, every request from this browser exits through your relay, and the proxy server itself never gets weaker than what's described below — no shortcuts, no silent downgrades. Sign in with your normal UrMomsVPN account email and password — that's it. No separate credential to generate or copy-paste; that happens automatically behind the scenes the first time you sign in, using the exact same relay infrastructure your iPhone or console proxy setup would use. Already signed into urmomsvpn.com in this browser? The extension detects that through a same-origin content script and skips the login step entirely — open the popup and you're already at the server picker. Works on any account, including the free tier, with no credit card and no trial period required. Pick a server from the dropdown, or choose "Connect to fastest" to auto-select the lowest-latency one from a real TCP-connect latency probe run against every active server in the fleet — not a hardcoded default, not a guess based on your account's billing region. Then flip the power switch. The extension verifies the connection actually works (a real request through the tunnel, not just "the settings were applied") before it ever shows "Connected." REAL PROTECTION, HONESTLY LABELED Every feature below does exactly what it says — no invented AI, no fabricated risk scores, no placeholder statistics designed to look impressive in a screenshot. If a protection has a real limitation, that limitation is written down in the popup itself, not buried in fine print. • WebRTC / IPv6 leak protection — forces WebRTC's ICE candidate gathering through the proxy, the standard fix for a VPN/proxy extension leaking your real IP via a STUN request that bypasses the proxy tunnel entirely. This is the single most common way browser-based proxy tools leak a user's real IP address despite the proxy itself working correctly, and it's on by default here. • DNS leak protection — automatic while connected, with nothing to configure. Hostname resolution for anything you visit happens at the relay server, not on your device, so your ISP or local network never sees a plaintext DNS query for the sites you're actually visiting. • Ad blocking & tracker blocking — over 20,000 domains pulled from the HaGeZi and StevenBlack blocklists, the same feeds already used server-side for DNS-level blocking on our VPN clients (Windows, Android, and iPhone via WireGuard). The list refreshes automatically every 12 hours in the background, so it stays current without you doing anything. A small hand-curated list of the most common ad/tracker infrastructure is also bundled directly into the extension, so basic blocking works immediately after install, before the first background refresh even completes. • Malware & phishing blocking — a live feed from abuse.ch's URLhaus project, a free, actively-maintained, community-run list of confirmed-malicious hosts (malware command-and-control servers, phishing kits, drive-by download sites). Refreshed on the same 12-hour cycle as the ad/tracker list. • HTTPS upgrade — automatically upgrades plain HTTP navigations to HTTPS wherever possible, the same category of protection browsers themselves are increasingly building in natively, applied here at the network-request level via Chrome's own declarativeNetRequest API. • Third-party cookie blocking — strips cookies on cross-site requests, which is the closest real equivalent to "cookie isolation" that's actually achievable from a browser extension. This is not the same thing as Firefox's per-site container tabs, and we don't claim it is — it's an honest third-party-cookie-blocking implementation, not a full isolation/container system, and the popup says so directly. • Fingerprint reduction (opt-in, off by default) — noises canvas, WebGL, and Web Audio API output that's commonly used for browser fingerprinting, plus generalizes a couple of navigator properties (hardwareConcurrency, deviceMemory) that can contribute to a fingerprint. This is off by default, on purpose, because noising these APIs can visibly break sites that legitimately depend on exact pixel or audio output — some image editing tools, certain CAPTCHA implementations, and some audio production tools in the browser. You decide whether the tradeoff is worth it for your use case. WHAT IT DOESN'T CLAIM We don't pretend a domain blocklist passes every "extreme" ad-blocker grading test you'll find online — those tests also grade cosmetic element-hiding (CSS injection to visually hide ad containers even when the underlying request wasn't blocked) and anti-adblock-detection-script circumvention, neither of which this extension attempts. Building a full cosmetic-filtering engine is a much larger undertaking than a domain blocklist, and we'd rather tell you that plainly than quietly fail your test and let you wonder why. We don't claim IPv6 leak protection at the operating-system level, because no browser extension actually can reach that — there's no extension API that lets a piece of installed browser software disable or reroute the host OS's own IPv6 network stack. WebRTC is the actual leak vector that matters in practice for a proxy extension like this one (raw IPv6 traffic outside the browser was never going through the proxy to begin with, proxy or no proxy, extension or no extension), and that's specifically what's covered. Read the specifics for yourself in the popup — every single protection listed there has a short, honest, one-line description of exactly what it does and exactly what it doesn't cover, written for a general audience, not buried in a EULA nobody reads. HOW IT WORKS Your browser's proxy setting points at our relay over standard HTTP CONNECT tunneling (the same mechanism any corporate or…