← All setup help

Using MizpahGuard with T-Mobile Home Internet

T-Mobile’s home internet gateway keeps its own DNS and doesn’t offer a bridge or passthrough mode, so the usual “change it on the router” step doesn’t exist.

What T-Mobile’s gateway does

The gateway’s DNS setting is fixed, and it can’t be switched to bridge mode. (Sources are community and support posts from T-Mobile customers and router vendors; T-Mobile can change this with a firmware update.)

Option 1 — Whole home: add your own router behind it

Plug an Ethernet cable from a LAN port on the T-Mobile gateway into the WAN/Internet port of a router you own, set DNS on your router to the address below, and turn off the T-Mobile gateway’s own Wi-Fi so every device uses your router instead.

74.208.171.84If the device also has an IPv6 DNS field, enter:2607:f1c0:f0da:1300::1
Because the gateway can’t be bridged, your router sits behind it (a “double NAT”). That works for browsing and streaming; online gaming and port forwarding can behave differently.
T-Mobile Home Internet’s public address can change often and can be shared with other customers, so the address-based setup may be unreliable. If your router supports secure DNS (DNS-over-HTTPS) use your home’s secure-DNS address from your router setup page instead; it identifies your home directly, not by address.

Option 2 — One device or browser at a time

Protect a browser, or set DNS on a device: iPhone / iPad / Mac, Android, Windows, game consoles.

How to tell it’s working

The quick test: on the device you just set up, open example.com. On an unprotected device you see a plain page titled “Example Domain”. On a device protected by MizpahGuard you see our “It’s working” page instead — it is blocked on purpose, for every household, so you can tell at a glance. (Your browser may show a certificate warning first, as it does for any blocked site; continue past it.)

You can also open your home’s Activity tab in MizpahGuard and look for the device’s browsing within a minute. If the test page doesn’t appear, the device is still using another DNS server — recheck the steps, or contact support from your dashboard and tell us your device and internet provider.