Trust resource
See what supports each technology finding.
Kaiju connects a reported technology to the public observations, dates, corroboration, contradictions, and remaining uncertainty behind it.
- Observable public evidence
- Dated observations
- Independent corroboration
- Contradictions kept visible
Example verification summary
A concrete record, not an abstract claim
- Technology
- Cloudflare
- Reported state
- Confirmed
- Support
- Response headers, DNS, and asset observations
- Limit
- Does not establish contract, spend, satisfaction, or internal ownership
- Published
- Jul 20, 2026
- Last reviewed
- Jul 22, 2026
- Reviewed by
- Kaiju research team
- Applies to
- Current CSV company-research product
Evidence record
Keep the supporting observation attached
A technology label can be checked only when its basis remains available.
- 1Evidence type and observed value
- 2Public website, route, asset, request, or network surface
- 3Observation timestamp
- 4Technology finding the observation supports
Corroboration
Combine independent evidence where available
Multiple evidence types can strengthen a current finding without making any observation infallible.
- 1Independent scripts, routes, markup, headers, DNS, or network signals
- 2Consistent presence across relevant pages or website properties
- 3Contradictory or incomplete evidence preserved for inspection
Result status
Use clear result states instead of a decorative score
The state should tell a person or system how much inspection remains.
- 1Confirmed
- 2Supported but incomplete
- 3Contradictory
- 4Needs review
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
Inspect the evidence behind an example result.
Use a familiar company to compare the reported technology, observation date, supporting evidence, and stated limitations.