Written by a person from the record · 2026-07-27 12:00:00 UTC

The most thorough reader of this site declares itself a 2019 handset, from ten countries at once

One user agent string — a consumer iPhone running iOS 13.2.3, released November 2019 — has made 222 requests to this site from 168 distinct addresses in ten countries, averaging 1.32 requests per address. It has taken 49 distinct paths, read robots.txt, taken no disallowed path, executed no script and never asked whether anything had changed. It is the only client that has fetched all three pages published here on 27 July. A single handset is one device in one place; the shape is the part that cannot be reconciled with the declaration.

What was observed

Between 25 July 11:22:49 UTC and 27 July 17:42:48 UTC, 222 external requests arrived carrying one identical user agent string:

Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15
(KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1

iOS 13.2.3 was released in November 2019. The string describes one consumer handset.

The addresses geolocate to US (95 requests), SG (26), DE (22), KR (16), BR (16), JP (15), HK (14), CN (9), TH (5) and ID (4).

How it behaves

Three pages were first published here on 27 July. This client fetched all three, and is the only one that has:

What the shape establishes

A consumer handset is one device. It holds one address at a time, changes address when its network changes, and is in one country. It does not appear in Singapore, Germany, Korea, Brazil, Japan, Hong Kong, China, Thailand and Indonesia over three days while averaging 1.32 requests from each of 168 addresses.

That average is the part worth reading twice. Traffic spread this thinly leaves no address looking busy: examined one address at a time, every one of these is an unremarkable visitor who loaded a page or two. The pattern exists only when the requests are grouped by what they declared, which is the one field nobody has to tell the truth in.

The declaration and the behaviour disagree, and only the declaration is under the client's control. That is the entire finding.

What it does not establish

Not who sent these requests. Not what they were for. Not whether one party or several arranged it. A request carries no field for intent and this site does not infer one.

Nor does it establish misconduct. This client read the rules and took no path it was asked to leave alone — every disallowed page on this site remains unfetched by anyone, and this client is part of that record rather than an exception to it. A false declaration and a violated rule are different things, and only the first is present here.

The politeness is worth stating plainly because it is the intuition most likely to mislead. A reader who learns "well-behaved crawlers are the genuine ones" has learned a rule this record contradicts: the most rule-abiding client here is also the one whose declaration its own shape refuses.

Limits

• No attribution. The address blocks are not resolved to an operator here. Doing so would mean citing a registry lookup taken at one moment as though it were part of the record, and this site publishes what it observed. The shape is established; who owns it is not.
• Country codes are geolocations of connecting addresses reported by the CDN. They say where a packet entered the network, not where anybody is.
• One site, three days, 222 requests. This is a description of what happened here. It supports no rate, no proportion, and no claim about how common this pattern is on the web.
• "Executed no script" is established by the absence of any beacon request. This client also never fetched the page carrying the script, so it is evidence about these visits rather than a capability claim.
• The user agent is the only thing linking these 222 requests into one client. If two unrelated systems happened to send byte-identical strings, this describes their sum. Nothing in the record can separate them, and nothing here assumes it can.

Governed by

• I. Reality is not interpretation — Reality ≠ Interpretation
• IV. Replay guesses nothing — Every figure must be reproducible from the record
• VI. The record is honest about its size — Sample size is stated; absence is reported as absence

These are the standards this finding was held to, not a claim that it is beyond question. The constitution states them in full.

Other findings

• One address requested 165 distinct paths within 17 seconds
• One address requested 31 distinct paths within 6 seconds
• One address requested 47 distinct paths within 5 seconds
• Which content formats are actually fetched
• One address requested 22 distinct paths within 3 seconds

All findings · Live record · Methodology