2xBRCheck object ↗
2XBR CHECK / INTEGRITY + TRUST + EVIDENCE

Check what holds.
Know what it means.

Drop a file or a 2XBR artifact. CHECK detects the strongest available contract, verifies complete bytes and shows trust as a separate decision. Signed evidence and run history stay available when you need them, without becoming separate products you must learn first.

Check object →
CHECKOBJECT / CONTRACT→RESULTPASS / REVIEW / FAIL→TRUSTSEPARATE DECISION→EVIDENCEWHEN YOU CHOOSE
ONE FLOW / FOUR STATES

Check first. Decide trust after.

2XBR keeps verification, trust and evidence separate internally, but you do not need to navigate separate products to understand the result.

01 / CHECKWhat holds?

Detect the strongest local contract and recompute complete-byte integrity before continuing.

CHECK OBJECT →
02 / RESULTWhat does it prove?

PASS, REVIEW and FAIL describe integrity. A valid signature does not silently become identity or trust.

QUICK DIAGNOSIS →
03 / TRUST0 trusted signers

0 blocked in this browser. Unknown valid keys remain unknown until you explicitly decide.

MANAGE TRUSTED SIGNERS →
ADVANCED CHECK CAPABILITIES
WEB EXPOSURESECRET SCANPRIVACY CLEANUPEVIDENCE CASETRUSTED SIGNERSSIGNED PACKAGE
CHECK / LOCAL VERIFIERCONTENT-FIRST ROUTINGSHA-256 / COMPLETE FILENO UPLOAD / NO AUTO-TRUST
01 / OBJECT

Drop anything verifiable.

PROOF, CASE, AUDIT, DELTA, ZIP or any local file. VERIFY detects the strongest supported contract before deciding what can actually be proven.

02 / OPTIONAL KNOWN HASH

Already know the SHA-256?

Paste an expected 64-character SHA-256. A generic file can then move from fingerprint-only REVIEW to an exact byte-for-byte PASS.

EMPTY = VERIFY EMBEDDED CONTRACT ONLY
03 / CHECK → RESULT

CHECK never promotes a plain hash into identity or authenticity. Signed/manifested 2XBR artifacts use their native verifier; generic files receive content identity + SHA-256 only.

DROP A LOCAL OBJECT OR CHOOSE A FILE
STRONGEST CONTRACT WINSContent before filename.

ZIP internals are inspected for PROOF, CASE and DELTA markers. AUDIT is recognized by schema. Renaming an artifact does not intentionally downgrade its verifier.

PASS ≠ IDENTITYIntegrity and trust stay separate.

A PROOF may have valid bytes and signature while its signing key remains NEW, ROTATED or locally blocked. VERIFY surfaces both states instead of merging them.

GENERIC FILESFingerprint, not mythology.

A normal file has no built-in authenticity contract. VERIFY reports REVIEW unless a supplied expected SHA-256 matches the complete bytes.