Reference
Know when each returned field was observed or reviewed.
Different fields can have different dates. Kaiju keeps the relevant observation or review date beside each value.
Example freshness record
One example record
- Technology observed
- 2026-07-17
- Finding reviewed
- 2026-07-18
- Company field reviewed
- 2026-07-15
- Result status
- Ready to inspect
Observation date
Record when the public evidence was seen
A current-looking label without a date is difficult to evaluate.
- 1
Keep the time the page, script, request, header, or other evidence was collected.
- 2
Keep the website and page context connected to the observation.
- 3
Do not imply that a later export date means the website was checked again.
Field freshness
Different fields can age differently
Technology evidence, company attributes, and reviewed conclusions may not share one date.
- 1
Show the date relevant to each field rather than one decorative record timestamp.
- 2
Keep stale values visible when a newer check has not completed.
- 3
Define when a field should be checked again based on how it will be used.
Using older results
Match freshness requirements to the decision
Not every decision requires the same recency.
- 1
Initial market research may tolerate older observations.
- 2
Time-sensitive outreach or migration research may require a newer check.
- 3
High-impact automated actions should require explicit freshness rules.