The profile clock and the exit address disagree: what is compared first

The address arrives ahead of any script: it sits in every request, or the answer never reaches you. Nobody asks your permission for it, and it cannot be switched off.

The clock follows: the zone name comes from the browser itself, with no prompt and no delay. A platform then compares countries rather than times.

1. 1

   Reads the address

   It sits in the request header, before the first line of the page.

2. 2

   Asks for the clock

   A zone name such as Europe/Berlin goes to any page that asks.

3. 3

   Runs the move backwards

   Zone to country, language to country, both against the address.

A zone is not the time on the clock, it is a name such as Europe/Berlin or Europe/Moscow. Every name belongs to a country, and the move backwards from it is unambiguous.

Across 114 countries there are 114 distinct zones and the same number of distinct language stacks. So the zone and the stack each name your country on their own, without your address.

Take a German address and a profile carrying Europe/Moscow. A platform gets two countries out of one visit and picks which of them to believe.

No real machine answers that way: a person in Berlin keeps Berlin hours rather than Moscow ones. The gap shows without a single extra request.

A platform reads the language list with the same move it uses on the clock. The first tag in it carries the region: de-DE is Germany, ru-RU is Russia.

Stacks come in different lengths: 10 countries carry two languages, 85 carry three, 19 carry four. English is in all 114, and it sits at the tail in 109: in the other five a local language follows it.

Your profile asks for the country of its own address, and it asks through the same proxy it will use afterwards. The answer comes over a secure connection, from four independent sources in turn.

Otherwise whoever runs the proxy could name any country and hand your profile a clock that argues with its own address. An answer sent in the clear is rewritten by anyone on the path; a secure one is not.

1. 1

   Through your own proxy

   The question goes the road the profile will take, not around it.

2. 2

   Over a secure connection only

   Otherwise the country is swapped by anyone standing on the path.

3. 3

   Four sources instead of one

   One refusal does not decide what clock your profile ends up with.

On ARMANOS Browser the clock comes from the browser itself, which is why the zone name and the offset from UTC come from one place. On the built-in engine a script over the page sets them: one place as well, but a different layer.

A platform often asks both ways at once. A browser whose two answers disagree gives the swap away faster than the zone itself ever would.

Most countries in the set carry one zone, and the profile gets exactly that. Eight countries are written out separately, and seven of them hold several zones: the United States and Canada four each, Australia four, Brazil, Mexico and Russia three, Indonesia two.

For those countries the zone falls to a profile by lot from its own seed. So two profiles on one American address usually show different clocks, and that works for you: identical clocks across five profiles would say more.

A country's language stack opens with an exact pair: German of Germany for Germany, Russian of Russia for Russia. Then comes the plain language, and English closes the row.

The pair with a region matters more than the language itself. Austrian German on a German address is no mistake, while German of Germany next to a Brazilian address is already a mismatch.

The clock comes from the country rather than the city of exit. If your address is in Denver and the profile drew the New York zone, a platform sees a two hour gap inside one country.

That happens to living people too: someone flies across the country with a laptop and the clock stays at home. But when it repeats across five of your profiles in a row, the picture reads differently.

The set holds a hundred and fourteen countries, each with a ready pair: a zone and a language stack. These are the countries sellers most often hand addresses from.

A country outside the set is not left without a clock: the zone and the language fall to the profile by lot from its seed. They are then under no obligation to match the country of the address, and the app does not warn about it.

So an address from a rare country is worth checking on the very first page: the clock and the language will tell more about the profile than the address does.

Rotating the address on a proxy does not change the exit country while the proxy stays the same. Moving a profile onto a proxy in another country changes everything at once: the clock and the language both.

After such a move, open the profile and check three things side by side: the address, the clock and the first language. A mismatch shows at a glance, and it is fixed before the first sign-in rather than after.

Open a profile and read four values in a row: the address, the zone name, the offset from UTC and the language list. Reduce them to one country.

If the countries part ways, a platform sees exactly the same thing. If they agree, this pair of signals makes you look like an ordinary machine at home.