Trust Centre

Open any result and see why it exists.

Inspect what Kaiju found, the public page or signal behind it, when it was observed, and whether anything prevented a complete check.

Open one field Kaiju added and ask

What did Kaiju return?

Which value was added to this company row?

Which page, script, request, header, form, or other public signal produced the observation?

Which maintained field definition and rule turned the observation into the returned finding?

Did the required checks complete, or was the website blocked, incomplete, contradictory, or unresolved?

Inspect the result

Use these pages when a value looks surprising, a field is blank, or your team needs to understand what Kaiju checked before returning the CSV.

See the public observations, dates, corroboration, contradictions, and remaining uncertainty behind a technology finding.

Understand when a website signal was observed, when a field was reviewed, and when a result may need to be checked again.

See what Kaiju was able to check before reading a blank, not-found, incomplete, or unknown result.

Evaluate company matching and technology findings separately using known positive, negative, ambiguous, and difficult examples.

Understand what public website and technology evidence can support, and which internal facts remain unknown.

Challenge a company match, technology finding, company field, or supporting evidence record and document the outcome.

Review how public web evidence, uploaded company files, generated results, access, retention, and delivery should be handled.

Test the returned data

Compare Kaiju’s findings with known answers, then inspect the supporting evidence and incomplete results before increasing volume.