Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.
Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
Utilities
Evidence Report Verifier guide
Recalculate the SHA-256 checksum in a locally selected evidence report.
Open Evidence Report VerifierWhat you need
- An nd-evidence-v1 JSON file
How to use it
- 1Select the evidence file.
- 2Allow local validation to run.
- 3Compare schema and checksum results.
- 4Review the manifest and payload summary.
Understanding the results
- A checksum match shows the payload agrees with that manifest.
Recommended next actions
- Confirm provenance and important findings independently.
Common problems
- Edited JSON, unsupported schema or malformed files fail verification.
Privacy and security
- The selected file is processed locally.
Worked example
- Scenario
- Checking an exported diagnostic bundle
- Example input
- diagnostic.evidence.json
- How to read it
- A matching digest shows the payload has not changed relative to its included manifest.
Limitations
- A checksum does not prove who created the file or whether its observations are correct.
Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.