Connecting your modem to the tools you work in
Your modem presents itself as a standard proxy: a hostname, an HTTP port, a SOCKS5 port, a username and a password, all shown in the dashboard at desk.dedicatedmobileproxies.com. Any tool that can take those five values can use the modem, and most tools people ask us about can. This page walks through the ones that come up most, starting with the two profile browsers we recommend for account work, Undetectable.io first and GoLogin second, then the helpers for ordinary browsers, whole computers, scripts, phones and API testing. The principle behind every setup is the same: one modem carries one identity, the address is left alone while that identity is signed in, and the profile's time zone matches the modem's city.
Undetectable.io
Anti-detect browserThe profile browser we recommend first. Each profile is a separate browser with its own fingerprint, storage and proxy, so a modem can be bound to a profile once and every launch of that profile goes through it. The built-in proxy check reports the carrier and city before anything loads, which catches a wrong modem before it touches an account.
- Install Undetectable.io and sign in.
- Create a new profile and open its proxy tab.
- Choose HTTP or SOCKS5 to match the port you are using, then paste the modem's host, port, username and password.
- Run the check; it should report a US carrier in the modem's city. Set the profile's time zone and language to match.
- Save, launch, confirm the address on an IP lookup page, and only then sign in to the account that lives on this modem.
- Bind one profile to one modem. Two profiles on one modem arrive from the same address at the same time, which is the pattern you are trying to avoid.
- Never rotate the modem while a profile is open and signed in.
GoLogin
Anti-detect browserOur second recommendation, with the same profile-plus-proxy model and a few differences that matter to some teams: a Linux build, an Android app that opens the same profile from a phone, and cloud-run profiles for people who do not want the browser on their own machine. The proxy is attached to the profile and checked before launch.
- Install GoLogin on your platform and sign in.
- Create a profile and accept the generated fingerprint for the operating system the account expects.
- In the proxy section pick HTTP or SOCKS5, paste the modem's details, and press check.
- Let GoLogin set the time zone and language from the proxy, or set them to the modem's city yourself.
- Launch, confirm the address, and keep this profile on this modem for as long as the account exists.
- Opening the profile from the Android app still routes through the modem, so the site sees the same address from a second device.
- Keep a sheet of profile, modem, city and renewal date so nobody launches a profile on the wrong line.
FoxyProxy
Browser extensionA Chrome and Firefox extension that sends an ordinary browser through a proxy, with pattern rules for which sites go through it. The right tool when you want one identity in one normal browser, or a quick look at a page from the modem's city without a full profile browser.
- Install FoxyProxy from your browser's extension store.
- Add a proxy: type HTTP or SOCKS5, the modem's host and the matching port, then the username and password.
- Set it to apply to all URLs, or add patterns so only chosen sites use the modem.
- Open an IP lookup page and confirm a US carrier in the modem's city.
- A normal browser keeps its own fingerprint and time zone; set the operating system's time zone to the modem's city if the account is sensitive.
- Disable WebRTC in the browser, or a site can learn your real address through it.
Proxifier
System-wide proxy for Windows and macOSRoutes every application on the computer, or a chosen list of them, through the modem without the applications knowing. Useful for desktop software that has no proxy setting of its own, and for making sure nothing on a work machine leaks around the modem.
- Install Proxifier and add a proxy server with the modem's host, SOCKS5 port, username and password.
- Create a rule: either all applications through the modem, or named applications only.
- Add a rule above it that sends your local network and the dashboard host direct, so you can still reach them.
- Open any application and check its address on an IP lookup page.
- Use the SOCKS5 port so that UDP-based applications work as well.
- Proxifier shows every connection in its log, which is the fastest way to see which program is talking to what.
Playwright
Browser automationA scripted browser for monitoring routines, screenshot series and QA walks through forms. Playwright takes a proxy per browser context, so one script can drive several modems at once, each context on its own modem, which is how most of the listing-monitoring routines on our use-case pages are automated.
- Install Playwright for Python or Node.
- Launch the browser with a proxy option of server set to the modem's host and HTTP port, plus username and password.
- Set the context's time zone and locale to the modem's city.
- Open an IP lookup page first and assert the carrier and city before running the routine.
- Pace the script like a person: a few pages a minute, with waits between them.
- One modem per context. Do not share a modem between two contexts that represent different identities.
- Save screenshots with the date and the modem's city in the filename so series stay comparable.
Python requests
Scripts and automationFor API calls, page fetches and lightweight monitoring without a browser. Pass the modem as the proxies argument on a session and every request in that session goes through it. Use the HTTP port for HTTP(S) targets and the SOCKS5 port, with the socks extra installed, when you want UDP or a SOCKS-only target.
- Build the proxy URL as http://username:password@host:port using the modem's HTTP port.
- Create a requests.Session and set session.proxies to that URL for both http and https.
- Fetch an IP lookup endpoint and check the carrier and city before doing anything else.
- Keep the session object alive for the whole routine so the connection is reused.
- Set a realistic User-Agent and accept-language header; a carrier address with a default Python agent is an odd pairing.
- To rotate between batches, call your rotation link from the dashboard, wait for the modem to reconnect, then confirm the new address before continuing.
curl
Command lineThe quickest way to prove the modem works and to check which address it holds. One line with the proxy flag and the credentials, pointed at an IP lookup endpoint, tells you the carrier and the city. Also the right tool for wiring the modem into shell scripts and cron jobs.
- Run curl with -x and the proxy URL http://username:password@host:port against an IP lookup endpoint.
- For SOCKS5, use socks5h:// in place of http:// and the SOCKS5 port, so DNS resolves through the modem too.
- Add -s and pipe to jq when you want just the carrier and city fields.
- Put the same line in a script to confirm the address before each batch.
- socks5h, not socks5, keeps DNS lookups on the modem side.
- Store the credentials in a netrc file or an environment variable rather than in shell history.
Shadowrocket
iPhone and iPad appAn iOS app that routes the device's traffic through a proxy, with per-app and per-domain rules. The usual way to put an iPhone's apps on a modem, for testing how an app behaves for a user on a US carrier in a given city, or for running a mobile-only account from the modem.
- Install Shadowrocket from the App Store.
- Add a server of type HTTP or SOCKS5 with the modem's host, matching port, username and password.
- Set the global routing to proxy, or add rules for the apps and domains that should use the modem.
- Connect, open an IP lookup page in Safari and confirm the carrier and city.
- Set the phone's time zone to the modem's city before opening a sensitive app.
- Shadowrocket shows a live connection list, which tells you which app is talking to which host.
Android Wi-Fi proxy
Built into AndroidAndroid can route a Wi-Fi connection's browser and most app traffic through an HTTP proxy with no extra software, which is enough for testing a web app or a browser-based account from the modem. Apps that ignore the system proxy need a proxy client app, and SOCKS5 needs one too.
- Open Wi-Fi settings, long-press the connected network and choose modify.
- Expand advanced options, set proxy to manual, and enter the modem's host and HTTP port.
- Save, open the browser, and sign in to the proxy when prompted with the username and password.
- Load an IP lookup page and confirm the carrier and city.
- The system proxy covers the browser and well-behaved apps; test each app you care about, since some bypass it.
- For SOCKS5 or for apps that bypass the system proxy, use a proxy client app and the modem's SOCKS5 port.
Postman
API testingFor checking how an API answers a client on a US carrier in a specific city: geo-dependent pricing endpoints, lead-routing APIs, feature flags served by region. Postman takes a proxy in its settings and applies it to every request in the workspace, so a collection can be replayed from each of our metros in turn.
- Open settings, go to the proxy tab, and enable a custom proxy.
- Enter the modem's host and HTTP port, enable authentication, and add the username and password.
- Send a request to an IP lookup endpoint and confirm the carrier and city.
- Run your collection; move the modem to another of our cities from the dashboard and run it again to compare.
- Save the IP lookup request at the top of the collection so each run starts with a location check.
- Postman's console shows the proxy in use for each request, which helps when a request seems to go direct.
The five values every tool needs
Host, HTTP port, SOCKS5 port, username, password. They are on the line's card in the dashboard, and they are the same whether you connect from a browser, a script or a phone. Both ports lead to the same modem and the same address. HTTP(S) is the simpler choice for browsers and most scripts; SOCKS5 adds UDP and is the one to use for system-wide routing and for apps that are not web browsers. Nothing about the plan changes with the tool: 4G at $5 a day, $28 a week or $69 a month, 5G at $6, $31 or $79, unlimited data, free moves between our cities, and a two-hour test at $2 or $3 to try the pairing first.
Why we recommend exactly two profile browsers
Account work needs a browser that keeps each identity's fingerprint, storage and proxy together, and both Undetectable.io and GoLogin do that well. We recommend Undetectable.io first because its proxy check and profile model fit the one-modem-per-identity rule with the least setup, and GoLogin second for teams that need Linux, Android or cloud-run profiles. We do not list other browsers of that kind because we have not tested them against our modems and would rather say nothing than guess.
The rule that applies to all of them
One modem carries one identity. Signed-in work stays on one address from sign-in to sign-out. Signed-out monitoring can rotate between batches. The profile's time zone and language match the modem's city. Check the address before the first request of every session. Because nobody else is on your modem, every one of these rules is within your control, which is the point of having the modem to yourself.
Integration questions
Which tool should I start with?
For accounts, Undetectable.io. For a quick look at a page from the modem's city, FoxyProxy or curl. For scripted monitoring, Playwright.
HTTP or SOCKS5?
HTTP(S) for browsers and most scripts. SOCKS5 for system-wide routing, UDP and apps that are not web browsers. Both reach the same modem.
Can several tools use one modem at once?
Yes, if they represent the same identity. Tools representing different identities belong on different modems.
How do I rotate from a script?
Call the rotation link shown in the dashboard, wait for the modem to reconnect, then confirm the new address before the next batch.