Scored signals use data obtained during this run: the IP profile, comparison of IP and browser timezones, and a WebRTC probe. Failed requests, missing information and blocked probes are marked unmeasured, rather than treated as confirmed types or full marks. Region match is also excluded when no target market is selected.
The question that matters most when running multiple accounts — does this environment resemble my other one — cannot be answered from outside. That takes comparing against a population, or against your other environment. A single browser session can only count how many fingerprint signals it collected, and that number comes out much the same for everyone. Rather than display a near-constant in the nineties dressed up as a measurement, we say plainly that it is out of reach.
This page checks your current network and browser environment. It does not touch, and cannot see, the state of your platform account. A clean environment is not the same as a safe account — linkage decisions also rest on history, cookies, payment methods and shipping addresses, none of which are observable from outside. Treat the result as a risk indication, not a substitute for signing in and testing on the platform itself.
How this works
AliExpress is region-bound in the same way as Temu, with one key difference: it has a large third-party seller ecosystem, and the environment requirements on the seller side are far stricter than on the buyer side. The two are treated separately below. What follows is industry observation; the platform does not publish risk-control details.
Cross-border shipping is tightly bound to country — the same item sent to different countries has entirely different lanes, rates and delivery times. The platform works out where you are from the IP and shows the matching options.
So the visible symptom on the buyer side is rarely a block; it is shipping rates and delivery times that look wrong. When that happens, first confirm the IP's country is actually your target market.
Seller Center is considerably stricter than the buyer experience. Signing in from a datacenter address, switching countries frequently, or several accounts sharing one exit are all common causes of account review.
If you sell here, read this page's advice the way you would read the Amazon page: a stable residential exit, a country matching where you operate, and independent environments per account. Buyers can be more relaxed.
Browsing and adding to cart are barely restricted; problems appear at payment. At that step the platform checks the IP's location, the billing address, the delivery address and the card's issuing country together, and disagreement between them triggers verification.
This means getting the IP right is not enough on its own — if the payment method's issuing country is far from the IP, the contradiction remains. The environment and the business details have to line up together.
On the buyer side, whether an order succeeds also depends on payment method, billing address and order history. On the seller side it involves store credentials, product compliance and dispute history. All of that is inside the platform.
This page answers only whether the network environment is consistent with the target market and whether it will trigger risk controls. It does not assess the account or store itself.
They use the same weight profile, so the same environment should score similarly. A large difference usually means you selected different target markets on the two pages. The scoring itself does not differ; the site selection does.
Not quite. Seller-side requirements approach Amazon's: a stable residential exit, a country matching where you operate, and independent environments per account. Buyers face more tolerance for datacenter IPs. This page scores to the stricter standard, so sellers can use it as-is.
Yes. Cross-border shipping is tied to destination country, and lanes, rates and delivery times genuinely differ. A rate change is the normal result of switching region.
It may be one factor, but the payment step checks the IP's location, billing address and card issuing country together. Getting the IP right while the card is issued somewhere far away leaves the contradiction in place. Line them up together.
The lookup passes through our servers, so ordinary access logs are produced. We do not sell or share query records. Browser-side checks are computed locally and not uploaded.
