Verification built around the evidence.
One structured way to ask the right question, collect the relevant records, and communicate a defensible conclusion.
From action to answer.
Define the claim
Start with an exact statement. What was requested? Which system and record matter?
Identify authoritative evidence
Determine which destination-side observations can establish the result.
Reconcile what differs
Separate agreement, contradiction, missing information, and self-reported activity.
Document the conclusion
Record the scope and relevant evidence so another reviewer can understand the decision.
Three possible answers.
Much better decisions.
Match — the records support the defined claim.
Conflict — the observed evidence contradicts the claim.
More evidence needed — the available records do not establish the requested outcome.
Scope is the foundation
of strong verification.
We focus on defined claims and available evidence. Verification findings describe what was examined; they do not replace a financial audit, legal opinion, or broad security certification.
Verify a shared evidence record.
Validate the signature and original record of a VERIFY DNS observation receipt.
Validate a receipt ↗Evidence at the point of observation.
Run public DNS record comparisons (A, AAAA, CNAME, TXT, MX, NS, CAA and SOA) and discover published email policies (SPF, DMARC, DKIM, MTA-STS, TLS-RPT and BIMI). Each result includes a timestamp, the observed values, the comparison and a service-signed JSON record.
Use the verification workspace ↗A published policy is not proof that mail is delivered, encryption is enforced, or a full security audit has been completed.