Thordata setup starts with redeeming your traffic code in its dashboard, then generating an endpoint with the location, authentication and session settings your client needs. Thordata states that its residential service supports HTTP and HTTPS access, country-to-city targeting and sticky sessions lasting up to 90 minutes.
27Proxy sells Thordata residential GB codes. We are an independent reseller, not affiliated with Thordata.
Thordata review: who it suits
Thordata offers country, city and ASN controls for tasks such as regional website QA and permitted public-data collection. Username/password access works for clients that accept proxy credentials; whitelisting offers another route for servers with a stable public address.
Before buying, check your client's protocol support, the code's traffic validity and the session duration your task needs. A country-level content check needs fewer restrictions than a city-and-carrier check.
Thordata residential proxy authentication
Thordata's residential getting-started guide lists credential and IP-whitelist authentication. The GB code supplies traffic; the generated endpoint supplies the connection details your application uses.
| Choice | Use it when | Setup detail |
|---|---|---|
| Username and password | A browser or application accepts proxy credentials | Create a proxy user, then select it in the generator |
| IP whitelist | Requests come from a stable public source IP | Add that source address to the whitelist |
| Rotating session | Each request can use a different exit IP | Select rotation without a session ID |
| Sticky session | Several requests need the same exit IP | Use a session ID and a duration within the documented limit |
Whitelisting identifies the machine connecting to Thordata. It does not select the residential exit address. On a changing home or mobile connection, credentials avoid having to keep the whitelist aligned with a new public source IP.
Thordata setup from a CDK
Step 1
Reveal the completed order's code
Once your 27Proxy order completes, open Orders, select the order and choose Show code. Keep the activation code private. It is separate from the proxy password you will create later.
Step 2
Redeem the code with Thordata
Sign in through Thordata's website and open the CDK redemption field in the dashboard. Enter the code and submit it. Thordata's CDK page describes adding the corresponding traffic to your account through dashboard redemption.
Step 3
Check the credited traffic and validity
Check the credited traffic and its effective period before configuring a client. Thordata's CDK page describes customizable validity. Its general traffic FAQ says standard plans last 30 days or until the traffic is used, whichever comes first. Use the effective period attached to your redeemed code when planning usage.
Step 4
Create a Thordata proxy user
According to the User & Pass auth guide, open Proxies → Residential Proxies → Proxy Setup → Users and select Add. Quick Add can generate a username and password. Select an enabled user; a limited user also has a traffic cap measured in MB.
Step 5
Generate the endpoint
Open Endpoint Generator under Proxy Setup. Choose user authentication and your proxy user, then set the location and session mode. Select the protocol, output format and quantity before generating the connection details. Copy the host, port, proxy username and proxy password into the matching fields in your client.
Thordata explicitly distinguishes the proxy authentication username from the dashboard management username. Using the website login as the proxy login is the wrong credential pair.
Step 6
Check the connection
Use the dashboard's generated sample request with the provider's IP-information endpoint. Inspect the returned exit address and location, then make a permitted request to the actual service you intend to use. A successful IP lookup checks connectivity to that lookup service. Check the expected response from your intended destination separately.
For order delivery questions, contact 27Proxy support. For a client connection problem, keep the selected protocol, gateway and error text available, with passwords removed.
Country, city and ASN targeting
Thordata's Location Settings documentation lists country, state, city, continent and ASN controls. Country parameters use two-letter ISO codes. The country guide gives country-DE for Germany and country-JP for Japan.
Start with the country your task requires. Add a city only when the distinction matters, such as checking a city-specific page you operate. The city guide gives country-DE-city-munich and country-JP-city-tokyo as examples. These are targeting parameters, not complete proxy usernames.
ASN targeting selects a network or carrier. Thordata's ASN guide requires the ASN parameter together with a country parameter. It also says an unavailable ASN can produce an error response. If carrier selection is optional, country-only targeting leaves more addresses eligible.
Thordata notes that location databases can disagree. Compare the location using the database relevant to your QA task, and record which database produced the result. A different city label in another lookup is a reason to investigate the mapping rather than immediately diagnose an authentication failure.
Rotating and sticky sessions
The Session Control guide describes rotation as a new residential IP for each request. Sticky mode reuses an IP across requests with the same sessid; sesstime controls the requested duration. The documented maximum is 90 minutes.
Thordata states that a sticky IP can change when the session expires, the address becomes unavailable or the session is idle. A request still running at the session deadline can be interrupted. For a sequence of related QA requests, choose a duration that covers the work and handle connection failures in the client.
For whitelist access, follow the Whitelisted IPs guide. Its API-list warning matters: listed IPs can be system identifiers rather than actual exit IPs. Verify the address seen during a request instead of treating a generated list entry as the final exit.
Thordata setup: protocols and connection checks
Thordata's residential protocol page documents HTTP and HTTPS proxy connections. HTTPS encrypts the connection to the proxy, and the page warns that some older libraries and third-party tools lack HTTPS proxy support.
Its protocol and port FAQ lists port 9999 for rotating residential access. Use the gateway generated for your configuration and match the client's proxy scheme to the selected protocol.
If a connection fails, check the proxy user's enabled status and traffic cap, the copied credentials, and any source-IP whitelist. Then check the client's protocol support. Change one setting at a time so a successful retry identifies the cause. If the destination refuses proxy traffic, use its approved API, request permission or use an allowed direct connection.
For help interpreting an IP reputation lookup, read our Scamalytics guide.
Thordata strengths, limits and alternatives
Thordata's documented strengths are detailed routing controls, two authentication methods and configurable sessions. City and ASN availability varies, sticky reuse has a time limit, and clients must support the selected HTTP or HTTPS proxy connection.
| Your requirement | Option to consider | Reason |
|---|---|---|
| Country, city or carrier controls with GB traffic | Thordata GB | Documented targeting and session parameters |
| DataImpulse access through a reseller dashboard | Supproxy (Dataimpulse) | Supproxy lists DataImpulse gateway credentials and session controls |
| Usage measured by extracted IP count | NovProxy IP | Separate short-term per-IP model rather than GB traffic |
Compare residential GB plans, Supproxy (Dataimpulse) and NovProxy IP keys around billing units and client needs. The NovProxy setup guide explains its separate traffic and per-IP workflows.
FAQ
Can I redeem a Thordata CDK in the dashboard?
Yes, dashboard redemption adds the traffic attached to your CDK to your Thordata account. After submitting it, check the credited traffic and effective period before generating an endpoint.
Does Thordata traffic expire?
Yes: Thordata's general validity FAQ says standard-plan traffic ends after 30 days or when consumed, whichever happens first. A CDK can carry a custom validity period; use the entitlement shown for your redeemed code.
Which protocols do Thordata residential proxies support?
Thordata lists HTTP and HTTPS for residential proxy access. HTTPS proxy support varies among older libraries and third-party clients, so match the generated protocol to what your application accepts.
Thordata vs DataImpulse: which should I choose?
Choose Thordata when you need its documented country, city and ASN configuration; consider Supproxy for DataImpulse access through a reseller dashboard. Supproxy provides gateway credentials and session controls. Compare each option's authentication and client compatibility against your workflow.
Does a sticky session keep one IP permanently?
No: the provider's maximum sticky duration is 90 minutes. Expiry, inactivity or an unavailable address can end reuse of that IP, so configure sticky mode for a limited sequence of requests.