HTTP
Browser & many scrapers
Ideal for common HTTP workflows. Use your assigned host, port, username, and password in tools that support HTTP proxies.
How Jesus Proxy works
Jesus Proxy turns a phone’s mobile (SIM) public IP into an HTTP or SOCKS proxy you can use from a PC, bot, or app — with clear auth, plan speed limits, and optional IP rotation. US mobile proxies use this same path.
In one sentence
Customers talk to Jesus Proxy. Websites see the phone’s carrier IP. The platform never pretends the server itself is your exit IP — the SIM is.
The pieces of that path, from your tool to the carrier exit, are in how proxy infrastructure fits together.
The full path
A simple hotel-lobby analogy: you enter through Jesus Proxy; the courier (your phone) finishes the trip on the cellular network.
Your browser, bot, or app connects to Jesus Proxy using your host, port, username, and password.
Jesus Proxy checks your credentials and applies your plan’s speed limit before traffic continues.
A private tunnel carries the request to your phone — the secure link between Jesus Proxy and your device.
The phone handles the real internet request using its mobile (SIM) connection.
The destination sees a real mobile network IP — not a typical datacenter address.
Getting started
Create a connection, connect the phone, add proxy access, then point your tools at Jesus Proxy. The public exit stays on your SIM the whole time.
Create your connection →In your dashboard, create a connection. Jesus Proxy prepares your access points and phone setup.
Install and connect the Jesus Proxy phone app so your SIM can become the exit path.
Create HTTP or SOCKS credentials for your tools. Each proxy routes through your connected phone.
Point your browser, scraper, or automation tool to the provided host and port — then run your work.
Proxy access
Choose the proxy type your software expects. Both are authenticated and forwarded through your connected phone.
HTTP
Ideal for common HTTP workflows. Use your assigned host, port, username, and password in tools that support HTTP proxies.
SOCKS5
Useful when your stack needs SOCKS. Dedicated access points keep sessions clear and easy to manage.
Plan limits
Plans include speed ceilings (for example 20 / 50 / 100 Mbps). The plan never raises a slow SIM above what the radio can deliver.
Change IP
When you request a new IP, the phone refreshes its cellular path and reports a new carrier public address. Your proxy host, port, and credentials stay the same so tools don’t need reconfiguration.
Link, API, and timer options are explained on rotating mobile proxies.
WiFi Split
Think of the SIM as the delivery van that must carry packages to the internet, and Wi‑Fi as a fast private road for the radio link back to Jesus Proxy.
Speed expectations
Download through the proxy depends on SIM download, the tunnel path back to Jesus Proxy, and your plan limit. With a healthy WiFi Split setup, the tunnel often rides Wi‑Fi — so the SIM download becomes the main bottleneck.
≈ min(SIM download, tunnel path, plan limit)
≈ min(SIM upload, plan limit)
A 100 Mbps plan on a ~30 Mbps SIM still measures near ~30 Mbps.
FAQ
Practical questions about exit IPs, WiFi Split, plan speed, and Change IP — answered in plain language.
Websites see your phone’s mobile carrier IP. Customers connect to Jesus Proxy, but the public exit is the SIM.
No. WiFi Split helps the private tunnel between Jesus Proxy and your phone. Proxy download speed is still limited by what your SIM can download.
No. The network used for exit is the public IP customers and websites see. Jesus Proxy exits on cellular so the exit stays a mobile IP.
Your plan is a ceiling, not a guarantee. If the SIM can only download around 30 Mbps, proxy tests will sit near that — even on a higher plan.
Your host, port, and login stay the same. Change IP requests a new mobile public address from the carrier.
Check your exit IP on the IP lookup page.
Next step
Start with Jesus Proxy and put a SIM-exit connection behind your tools.