UrMomsVPN Proxy

Route this browser's traffic through your UrMomsVPN console-proxy relay.

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 ISP-level HTTP proxy uses), authenticated per-request the moment you sign in. The relay itself runs on real WireGuard VPN servers in our fleet — the same physical servers our Windows, Android, and iPhone clients connect to — so your traffic actually exits from a real datacenter IP, not from some intermediary box sitting between you and the real infrastructure. Free-tier connections are speed-limited to a modest, clearly-disclosed rate (adjustable by us, never hidden); paid tiers get full, unthrottled speed. Nothing about which tier you're on changes which protections are turned on by default — those are the same for everyone. WHO THIS IS FOR If you already use the UrMomsVPN Windows or Android app and just want this same protection for one specific browser without running the full VPN client, this extension gives you that without the overhead of a system-wide tunnel. If you're on a machine where you can't install a full VPN client (a locked-down work laptop, a shared computer, a Chromebook) but you do have browser extension permissions, this gets you real relay-based protection anyway. If you just want ad and tracker blocking without paying for anything, the free tier includes it — that's a deliberate choice, not a limited trial. FREQUENTLY ASKED Does this work with two-factor authentication? If your account has 2FA enabled, the popup's own login form will tell you to sign in on the website first — the popup is intentionally too small to build a full second-factor code entry flow into, so it defers to the real login page and then auto-detects that session once you're back. Is this a full VPN? No — a browser extension can only ever affect this browser's own traffic, by design (that's how every browser extension proxy setting works, on every browser, from every vendor). Other apps and other browsers on the same device are unaffected. If you need every application on your device covered, that's what the UrMomsVPN Windows, Android, or iPhone client is for. Will this slow down my browsing? Paid tiers get full relay speed with no artificial cap. Free tier is speed-limited (currently a modest few megabits, clearly shown as a real limit rather than hidden throttling) to keep the free offering sustainable — you'll notice it most on very large downloads, less on typical browsing. What happens to my account credentials? Your email and password are sent once, directly to our own backend over HTTPS, to authenticate you — never to any third party, never logged in plaintext, never stored in the extension itself beyond the session token needed to keep you signed in. The proxy-specific credential that gets generated afterward is a separate, rotatable secret; it is not your account password, and losing it doesn't expose your account password. Can I use this on multiple devices at once? Yes. Signing in on a second device does not sign you out of the first — the underlying proxy credential is shared per-account, not per-device, the same way it already works for iPhone/console proxy setups. SUPPORTED BROWSERS Built on Manifest V3, so it runs on Chrome, Microsoft Edge, and Brave using the exact same package. A Firefox build is also available with its own manifest format for that browser's extension model, distributed directly for now while we work through Mozilla's signing process for addons.mozilla.org. ALSO INCLUDED • A privacy advisor that checks which of the protection toggles above are currently switched off — nothing fancier than that, just an honest read of your own settings, presented clearly instead of buried in a submenu. • A live risk indicator for the current tab: whether it's using HTTPS, how many ad/tracker requests were actually blocked on that specific page, and whether the domain appears on the live malware/phishing list — real signals pulled from what the extension is already doing, not a fabricated score. • Lifetime stats that persist across sessions: total ads blocked, trackers blocked, threats prevented, an estimated amount of data saved, and total time protected — all counted from real blocked requests, never seeded with placeholder numbers to look more impressive on first install. • A server picker, including "Connect to fastest," backed by a real latency probe against your fleet rather than a fixed regional default. • A keyboard shortcut (Alt+Shift+U by default) to connect or disconnect from anywhere in the browser, without needing to open the popup first. • Settings import/export, so you can back up or move your protection-toggle preferences between machines. Your proxy credential and password are deliberately excluded from any export file for safety — reconnect with a fresh sign-in on the new machine instead. PERMISSIONS, EXPLAINED • proxy — to actually configure this browser's traffic to route through the relay. This is the core permission the entire extension exists to use. • webRequest / webRequestAuthProvider — to answer the proxy's own authentication challenge automatically with your signed-in credential, instead of showing you a native browser login popup asking for a username and password on every single new connection. • declarativeNetRequest — to block ad/tracker/malware domains and to enforce the HTTPS-upgrade and third-party-cookie-blocking rules described above, all of which are individually toggleable by you. • privacy — to set WebRTC's IP-handling policy, which is what actually implements the WebRTC leak protection described above. • storage — to save your connection settings, your session, and your protection-toggle preferences locally in the browser, so you don't have to reconfigure anything between sessions. • alarms — to refresh the ad/tracker and malware block lists automatically in the background on a schedule, without needing the popup open. • tabs — to identify the currently active tab's URL, which is what powers the popup's real per-tab risk indicator described above. • Host permission (access to all sites) — a proxy extension has to be able to route and protect traffic on any site you might visit; there is no way to build this specific kind of feature with a narrower permission, and it is never used here for tracking, analytics, or any purpose beyond actually running the proxy and its protections. TROUBLESHOOTING If the popup shows "Couldn't verify these credentials against the proxy," the most common cause is a temporary network hiccup between your device and the relay — try again in a moment before assuming something's broken. If it keeps happening, try signing out and back in from the popup; that generates a fresh proxy credential and re-applies your settings from a clean state. If a specific site looks broken while connected — a broken image, a missing script, a layout that looks wrong — the most likely cause is one of the blocking protections catching something it shouldn't (a false positive on the ad/tracker list, or the HTTPS-upgrade rule hitting a page that genuinely only serves over plain HTTP). Open the popup, expand "Privacy & security," and try turning off ad blocking, tracker blocking, or HTTPS upgrade one at a time to isolate which one is responsible, then leave it off for that browsing session if needed. None of the protections are permanently locked on. If "Connect to fastest" seems to pick a server that doesn't feel fastest for you personally, keep in mind the latency probe measures the path from our backend to each relay server, not the path from your specific device and network to that server — it's a reasonable approximation for most users, not a guarantee for every network configuration. You can always pick a specific server manually from the dropdown instead if you know which one performs best for your connection. OUR PHILOSOPHY ON THIS LISTING A lot of proxy and "VPN" browser extensions market themselves with vague, unfalsifiable claims — "military-grade encryption," "AI-powered threat detection," "bank-level security" — phrases that sound impressive and mean almost nothing concrete. We've tried to write this listing, and the extension's own in-popup copy, the opposite way: naming the actual mechanism behind every claim (WebRTC IP-handling policy, a specific declarativeNetRequest rule, a specific named threat-intelligence feed) so you can verify it yourself instead of taking our word for it. Where a feature has a real, honest limitation, we've said so directly rather than let a vague claim paper over it. If you find a claim in this listing or in the extension itself that doesn't hold up, we'd genuinely like to hear about it through the support channel on our website. A NOTE ON THE FREE TIER Ad and tracker blocking, malware/phishing blocking, WebRTC leak protection, and every other protection listed above are available on the free tier, not held back as a paid-only upsell. The only difference between free and paid tiers is connection speed through the relay — paid tiers get full, unthrottled bandwidth; the free tier is speed-limited to a modest rate that's disclosed as an actual number, not silently degraded traffic disguised as a "connection issue." We'd rather you use the real protections for free and decide later whether faster speed is worth paying for than gate the actual privacy features behind a paywall and call ad blocking a "premium feature." GETTING HELP Support requests, bug reports, and general questions can go through the support page linked from your account once signed in at urmomsvpn.com, or through the contact details in our privacy policy. We read every message that comes in through the actual support inbox, not a ticket queue that disappears into nothing. We don't sell, rent, or share your browsing data with anyone. Full details are in our privacy policy: https://urmomsvpn.com/privacy.html