Navigation

Explore Kaiju

Start with a customer, prospect, account, client, or research list, then inspect how Kaiju supports each finding.

Already using Kaiju?

Continue to your Team.

Sign in

Trust resource

Know when each returned field was observed or reviewed.

Different fields may come from different public sources and dates. Kaiju keeps the relevant observation or review date close to the returned value so a user can decide whether it is still useful.

  • Observation dates
  • Review context
  • Source-specific freshness
  • Stale results made visible

Example freshness record

A concrete record, not an abstract claim

Technology observed
2026-07-17
Finding reviewed
2026-07-18
Company field reviewed
2026-07-15
Result status
Ready to inspect
Published
Jul 20, 2026
Last reviewed
Jul 22, 2026
Reviewed by
Kaiju research team
Applies to
Current CSV company-research product

Observation date

Record when the public signal was seen

A current-looking label without a date is difficult to evaluate.

  1. 1Keep the time the page, script, request, header, or other signal was collected.
  2. 2Keep the website and page context connected to the observation.
  3. 3Do 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. 1Show the date relevant to each field rather than one decorative record timestamp.
  2. 2Keep stale values visible when a newer check has not completed.
  3. 3Define 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. 1Initial market research may tolerate older observations.
  2. 2Time-sensitive outreach or migration research may require a newer check.
  3. 3High-impact automated actions should require explicit freshness rules.

Continue the evaluation

Follow the next question behind the result.

Move from one trust concern to the methodology, product explanation, or limitation that helps your team decide whether the data is safe to use.

Test the method

Review freshness using companies you know.

Compare observation dates, returned technology findings, and result status with companies your team already understands.