All 461 records in OnlyDetect's 30 September 2026 research sample had validation timestamps on 27 September 2026. That establishes when the directory recorded those checks. It does not establish when the creators last posted, changed their prices, or became active.
This timestamp audit explains a common ambiguity in “updated” labels. A technical refresh and a material change are different events, and a useful source should say which one it means.
The observed validation window
The earliest recorded validation was 27 September at 06:52:05 UTC. The latest was 09:17:50 UTC on the same day. All 461 therefore fell within both the seven-day and 30-day windows at the research observation time.
The downloadable snapshot retains precise timestamps. Its editorial date is 30 September in Asia/Bangkok, while the two aggregate observation timestamps fall late on 29 September UTC. These are timezone descriptions of the same research period, not contradictory dates.
Three dates that should not be confused
Scroll across the table on smaller screens.
| Date | What it can describe | What it does not automatically prove |
|---|---|---|
| Directory validation time | When a record was checked by the directory | When an offer changed |
| Source publication or modification date | A date asserted by the source page | That every statement is newly verified |
| Article publication or revision date | When an article was published or materially revised | That a live checkout still matches |
A date becomes useful only when its meaning and source are clear. Replacing a timestamp every time a page is built would not create new evidence about a creator.
Why we cannot report refresh latency
Latency would require knowing when a source actually changed and when the directory first captured that change. This snapshot contains validation times, not a complete immutable event history for every offer. Subtracting an arbitrary source date from a validation time would manufacture a measurement we do not have.
Similarly, seeing all records validated on the same day does not establish that the system checks every record daily. It describes this selected sample at one observation.
How to use freshness when making a decision
Treat a recent observation as a reason to inspect the source, not as a guarantee that a promotion remains available. Prices, account links, and offer conditions can change after a check. For a subscription decision, verify the current official offer.
The profile refresh guide explains what to do when a listing and its source differ. OnlyDetect's refresh methodology also distinguishes refresh targets from guarantees.
What a stronger future study would need
Preserve comparable observations over time, identify material field changes, retain the first observed source change and first directory update, and report failures separately. A delayed observation and an unchanged source are not the same outcome.
Until those measurements exist, the accurate result is this dated validation window. It supports understanding the sample's freshness metadata, not a claim about platform activity or ingestion speed.