HTTP and HTTPS on gw.ludaxproxy.com:8081 — the Premium TLS service has its own port. Premium TLS is a separate prepaid balance on the same account.
RESIDENTIAL PREMIUM TLS · PREPAID · NO SUBSCRIPTION
When the target checks the address and the handshake
The screened Residential Premium pool with a separate premium pool, carrying a pinned browser TLS handshake. One request, both signals: an exit with a cleaner reputation, and a ClientHello matched to a real browser build.
ONE-OFF PREPAID TRAFFIC · NO AUTO-RENEWAL · CRYPTO BILLING
- Screened premium exits
- 127 browser profiles
- Country and ASN
- Exit and profile held together
Your requestYour code is unchanged — an ordinary proxy address and one password parameter.
GET /account
Browser TLS profileHANDSHAKEOpened the way the captured build opens it — ClientHello, cipher order, ALPN and HTTP/2 SETTINGS.
profile chrome145
ja4 · t13d1516h2_8daaf6152771_b0da82dd1658
Screened premium exitPREMIUM POOLA residential address screened before it entered the pool, held for the session lifetime.
Berlin, DE
Protected targetWhat the site can check: where the connection came from, and how it was opened.
200 OK
SCREENED EXIT
BROWSER HANDSHAKE
Both signals are set at the relay, not in your code.
- STARTING PACKAGE
- $5.241 GB of prepaid traffic, one-off. No auto-renewal. The effective rate falls to $2.54 / GB at the 500 GB package.
- EXIT POOL
- Premium residentialThe Residential Premium pool, kept separate from the standard pool, with a separate premium pool.
- HANDSHAKE
- 127 browser profilesCaptured from real Chrome, Safari, Firefox, Edge, Android and iOS builds.
- SESSIONS
- Rotating or stickyNew exit and profile per request, or hold both together for 1–1000 minutes.
[ WHAT TLS MEANS HERE ]
A screened IP can still look like a bot.
The premium pool fixes who you appear to be. TLS fixes how you appear to connect. Websites read both — and the second one is decided before the page even starts loading.
PREMIUM EXIT, SCRIPT HANDSHAKE
Screened home IP24.18.106.77 · Austin, US
Automation signalScript connection · requests 2.32 cipher order
TECHNICAL FINGERPRINT (JA4)
t13d1112h2_e8f1e7e78f70_6bebaf5329ac✗ LOOKS LIKE AN AUTOMATION TOOLThe address passes the reputation check, but the connection still looks automated.
The signals do not matchRESIDENTIAL PREMIUM TLS
Screened home IP24.18.106.77 · Austin, US
Real browser signalChrome 145 connection · browser cipher order
TECHNICAL FINGERPRINT (JA4)
t13d1516h2_8daaf6152771_b0da82dd1658✓ LOOKS LIKE A REAL CHROME BROWSERThe screened address and the browser identity agree.
Both signals matchBoth lanes leave from the same screened premium address. Only the browser connection is different.
[ BEFORE THE PAGE LOADS ]
What happens in the first 50 milliseconds
In the first blink, a website can tell what kind of software is connecting. Premium TLS makes that first impression match a real browser, on a premium exit.
ClientHello inspector · profile chrome145Building browser identity…
0 MS18 MS34 MS50 MS
TLS 1.3 CLIENTHELLO0–8 ms
version 0x0303 · legacy_version
random 32 bytes
session_id 32 bytes
cipher_suites [ 0x0a0a, 0x1301, 0x1302, 0x1303, 0xc02b … ]
Like saying hello at the door
Before a page loads, your software introduces itself. The way it says hello is already enough for a website to guess what kind of software is calling.
Ludax handles this at the relay, using profiles recorded from real browsers. Add -profile- to choose one, or leave it off and Ludax picks for you.
[ 127 PROFILES ]
Choose the browser you want to match
Pick Chrome, Safari, Firefox, Edge or mobile. Ludax uses a profile recorded from the real browser, and holds it for the whole sticky session alongside the screened exit.
Chrome 145 · Windows 11
-AE-chrome145
CONNECTION DETAILS
- Cipher order
- GREASE, 0x1301, 0x1302, 0x1303
- ALPN
- h2, http/1.1
- Key share
- X25519MLKEM768
- H2 window
- 6291456
Recorded from a real browser
Profiles are updated as browsers change, so your connection does not look outdated.
[ PREMIUM TLS USE CASES ]
Where both signals have to agree
DE · workspace A · chrome14515:00Session held
US · workspace B · chrome14515:00Session held
GB · workspace C · safari_ios_2607:20In session
IdentityExit + profile
One screened exit and one browser profile per workspace, pinned together
One identity per workspace. Example data.
One identity per account — address and browser both.
- The screened exit reduces the chance a session starts on an address with abuse history.
- The profile stays pinned for the session, so the handshake does not change mid-flow.
- For accounts you own or are authorized to operate — see the Acceptable Use policy.
DE · GermanySponsored
Winterreifen ab 89 € — heute bestellt
Jetzt ansehenServedUS · United StatesSponsored
All-season tires from $79 — free fitting
Shop nowServedBR · BrazilPatrocinado
Pneus a partir de R$349 em 10x
Ver ofertasServedThe same slot, one creative per market. Example data.
Load placements from a network and a browser the stack recognises.
- Ad stacks that score the exit and read the handshake are the case this product exists for.
- Pin an ASN and a mobile profile when you need to see what a phone in that market is served.
- Follow the redirect chain to the landing page on the same held session.
DE · GermanyLocal view
de-DE · EUR · VAT shown
CA · CanadaLocal view
en-CA · CAD · tax at checkout
JP · JapanLocal view
ja-JP · JPY · tax included
What a local customer would be served. Example data.
Test your own release as a local visitor on a real browser.
- Geo routing, currency, tax display and consent flows, checked from inside the market.
- Switch between desktop and mobile profiles to see which build your edge serves.
- If an ASN has no capacity, the request falls back to the country instead of failing.
US · protected storefront$189.00Page served
DE · protected storefront€199,90Page served
JP · marketplace¥28,800Page served
BR · marketplaceR$1.149,00Retry queued
Prices as published on each local storefront. Example data.
Read guarded catalogues without spending the run on retries.
- Two of the checks a storefront makes are answered before the first byte of HTML.
- Hold one exit and one profile through cart, variant and shipping steps that reveal the real price.
- Keep the cheaper products for open storefronts and spend Premium TLS where it is needed.
Run 07:00 · 3 marketsparseOutput ready
Run 13:00 · 3 marketsfetchRunning
Run 19:00 · 3 markets—Queued
Gatewaygw.ludaxproxy.com
Same endpoint as the other residential products · Premium TLS credentials
Stage status per run. Example data.
Give the hardest sources in a pipeline their own lane.
- One gateway and one credential change — no rewrite to move a job onto Premium TLS.
- Route only the sources that keep failing here, and leave the rest on a cheaper product.
- Prepaid balance caps the spend a runaway retry loop can reach.
[ HOW IT WORKS ]
How the handshake and the screened exit combine
Both are applied at the relay, in the same request. Nothing in your client changes except the password parameters.
Add -profile- with an identifier such as chrome145, or leave it off and the relay selects a profile. Country, an ASN where you need one, and rotating or a sticky lifetime of one to fifteen minutes.
The ClientHello is built from the captured browser build, then the request leaves on a screened premium address with a separate premium pool. In a sticky session the address and the profile are held together until it ends.
premium-tls.sh
# screened premium exit in Germany, Chrome 145 handshake, sticky for 10 minutes
curl -x "http://user_a1f9c2:yourpass-country-de-session-x71-profile-chrome145@gw.ludaxproxy.com:8081" \
https://api.ludaxproxy.com/whoami
# let the relay choose a plausible profile
curl -x "http://user_a1f9c2:yourpass-country-de@gw.ludaxproxy.com:8081" \
https://api.ludaxproxy.com/whoamiEvery parameter, with defaults and fallbacks, is listed in the documentation.
FOR DEVELOPERS
Ready to integrate?
Authentication, endpoints, session, targeting and -profile- parameters, with code examples — Premium TLS uses the same reference as the other residential products.
[ COVERAGE & TARGETING ]
Choose the exact place—not just the country.
Set your location in seconds: pick a country, then pin the ASN network you need. Pick a country and the example cycles through three networks inside it — the country itself only changes when you choose another.
See all locationsUnited States
Country → ASN
Premium · ASN
AS7922 · Comcast Cable
[ CAPABILITIES ]
What Premium TLS adds — and what it does not
Documented capabilities, documented parameters, and the limits stated before you buy rather than after.
Screened exit pool
The same pool as Residential Premium: addresses are screened for abuse history before they enter it, and premium traffic is routed over the premium ports.
Pinned browser handshake
127 profiles captured from real Chrome, Safari, Firefox, Edge, Android and iOS builds — ClientHello, cipher order, ALPN and HTTP/2 SETTINGS.
Country and ASN
The Premium targeting depth — country and ASN — with country fallback when an ASN has no capacity at that moment.
One identity per session
Rotate both per request, or hold the screened exit and the browser profile together for a lifetime you set between one and fifteen minutes.
Transparent limitationsWhat Premium TLS changes — and what it cannot.
- Ludax does not publish uptime, success-rate, pool-size or concurrency figures for Premium TLS.
- It removes two common mismatches at once. No proxy can guarantee that a target will serve a request.
- Your client still controls clicks, timing, JavaScript behaviour, headless settings and account history.
- Pick a profile that agrees with the rest of your request. An iOS handshake behind a desktop user-agent is its own mismatch.
- This is the most expensive residential product per GB. Buy it only for the targets that check both signals.
- Traffic content is not stored; account, billing and aggregate usage records are retained as described in the Privacy Policy.
Full technical specifications
- Network type
- ISP-assigned residential (premium pool)
- IP version
- IPv4
- HTTP
- Supported
- HTTPS
- Supported
- SOCKS5
- Supported
- Authentication
- Username and password
- IP allowlisting
- Not supported
- Country targeting
- Supported
- State / region targeting
- Not supported on Premium
- City targeting
- Not supported on Premium
- ASN targeting
- Supported where available
- Routing
- Separate premium pool
- TLS profiles available
- 127 captured browser builds
- Profile pinning
- Supported via
-profile- - Profile held in sticky session
- Supported
- Rotating sessions
- New exit and profile per request
- Sticky sessions
- 1–1000 minutes
- Concurrency
- Not published
- Billing model
- Prepaid traffic, per GB
- Plan validity
- 30 days from activation
- HTTP(S) gateway
- gw.ludaxproxy.com:8081
Values Ludax does not measure publicly are labelled Not published rather than estimated. Full parameter reference lives in the documentation.
[ FOUR RESIDENTIAL PRODUCTS ]
Two problems, and the product that solves both at once
Residential TLS fixes the handshake. Residential Premium fixes the exit reputation. Premium TLS is for the workflows where a target checks both — and where paying twice in retries costs more than the higher rate. See the full product comparison for every technical detail.
| DIMENSION | RESIDENTIAL | RESIDENTIAL TLS | RESIDENTIAL PREMIUM | RESIDENTIAL PREMIUM TLS |
|---|---|---|---|---|
| Entry package | $0.99 / 1 GB | $1.49 / 1 GB | $3.49 / 1 GB | $5.24 / 1 GB |
| Rate at 100 GB | $0.59 / GB | $0.89 / GB | $1.99 / GB | $2.99 / GB |
| Exit pool | The main rotating residential pool | The main rotating residential pool | A separate premium pool with its own gateway ports | The same premium pool |
| Routing | Standard gateway routing | Standard gateway routing | Separate premium gateway ports | Separate premium gateway ports |
| Targeting | Country, state or region, city where available | Country, state or region, city where available | Country and ASN where available | Country and ASN where available |
| TLS profile control | Not supported | 127 captured browser profiles | Not supported | 127 captured browser profiles |
| Sessions | Rotating, or sticky 1–1000 minutes | Rotating, or sticky 1–1000 minutes with the profile held | Rotating, or sticky 1–1000 minutes | Rotating, or sticky 1–1000 minutes with the screened exit and the profile held together |
| Suited to | Open targets, where cost per GB decides | Targets that inspect the handshake | Protected targets that score the exit address | Targets that check the exit and the handshake |
-
Residential Premium TLS
THIS PAGE- Entry package
- $5.24 / 1 GB
- Rate at 100 GB
- $2.99 / GB
- Exit pool
- The screened premium pool
- Routing
- Separate premium gateway ports
- Targeting
- Country and ASN where available
- TLS profile control
- 127 captured browser profiles
- Sessions
- Rotating, or sticky 1–1000 minutes with the exit and the profile held together
- Suited to
- Targets that check the exit and the handshake
-
Residential Premium
- Entry package
- $3.49 / 1 GB
- Rate at 100 GB
- $1.99 / GB
- Exit pool
- A separate premium pool with its own gateway ports
- TLS profile control
- Not supported
- Suited to
- Protected targets that score the exit address
-
Residential TLS
- Entry package
- $1.49 / 1 GB
- Rate at 100 GB
- $0.89 / GB
- Exit pool
- The main rotating residential pool
- TLS profile control
- 127 captured browser profiles
- Suited to
- Targets that inspect the handshake
-
Residential
- Entry package
- $0.99 / 1 GB
- Rate at 100 GB
- $0.59 / GB
- Exit pool
- The main rotating residential pool
- TLS profile control
- Not supported
- Suited to
- Open targets, where cost per GB decides
SCROLL THE TABLE SIDEWAYS
Residential TLS Proxies
The handshake on its own, on the standard pool. From $0.74 / GB.
See Residential TLSResidential Premium Proxies
The premium pool and a separate premium pool, without the handshake. From $1.69 / GB.
See Residential PremiumAll pricing
Every package across the products, with effective rates side by side.
See pricing
[ PRICING ]
Prove it on 1 GB. Scale when it holds.
Prepaid Premium TLS traffic, no subscription and no auto-renewal. Effective per-GB rates are shown for comparison, measured against the 1 GB package rate of $5.24 / GB.
Only buy both if you need both. If the handshake alone is the problem, Residential TLS starts at $1.49 / GB. If the exit reputation alone is the problem, Residential Premium starts at $3.49 / GB.
[ FAQ ]
Residential Premium TLS questions
Eight answers on the combination, the profiles, the sessions and the price.
What is Residential Premium TLS?
It is the screened Residential Premium exit pool with a separate premium pool, plus the pinned browser TLS handshake documented for Residential TLS. One request carries both: an exit address screened before it entered the pool, and a ClientHello matched to a captured browser build.
When is Premium TLS the right product?
When a target checks both the exit and the connection. If only the handshake is the problem, Residential TLS is cheaper. If only the address reputation is the problem, Residential Premium is cheaper. Premium TLS is for workflows that need stronger IP reputation and TLS-profile consistency at the same time.
How is Premium TLS priced?
Five prepaid packages: 1 GB for $5.24, 5 GB for $22.45, 25 GB for $93.50, 100 GB for $299.00 and 500 GB for $1,270.00. Effective per-GB rates are $5.24, $4.49, $3.74, $2.99 and $2.54. There is no subscription and no auto-renewal, and billing is in crypto.
Which browser profiles are available?
127 profiles captured from real Chrome, Safari, Firefox and Edge builds, plus Android and iOS mobile builds. Add -profile- with an identifier such as chrome145 to pin one, or omit the parameter and the relay selects a profile for you.
Does the profile stay the same during a sticky session?
Yes. On a sticky session of one to fifteen minutes the screened exit address and the browser profile are held together, so a multi-step flow finishes on one identity rather than changing shape half-way through.
Does this guarantee a target will serve my request?
No. It removes two common mismatches at once — a suspect exit address and a handshake that does not look like a browser. What your software does after connecting, and what the target decides, are still outside the proxy.
Which protocols and endpoints does it use?
HTTP and HTTPS on gw.ludaxproxy.com:8081, the dedicated Premium TLS port. SOCKS5 is available on Residential Premium (normal mode) only. Authentication is username and password; IP allowlisting is not supported.
Can I move between the residential products?
Yes. Each product is a separate prepaid balance on the same account, and all of them are reached through the same gateway, so switching is a credentials change rather than an integration change. Buy the smallest package and run the same job twice to compare.
[ RESIDENTIAL PREMIUM TLS ]
Run the job that keeps failing, once
Buy 1 GB, point the job that keeps getting challenged at it, and compare what comes back. Move the volume across only if the difference is real — nothing renews on its own.