Invented engagement example. No real provider finding.
UNVERIFIABLE
Your directory: Listed as an active provider · Published source: No active registry entry for the listed identifier
Supported action: The registry search completed and returned no active entry matching the directory’s identifier at the observed time.
Limit: Whether the provider holds a registry registration — absence of a match is not absence of a registration.
Evidence & verification
The readings used
Your directory
Listed as an active provider
Observed Sep 18, 2026 10:00 UTC · excerpt sha256 7a9d31e6c05f4012b8d3e6c29f17a3d5e8c41b09a7f52d6318e5c0b9d42a77f6
NPPES registry
No active registry entry for the listed identifier
Observed Sep 22, 2026 09:00 UTC · excerpt sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Why these readings are comparable
Subject binding not established: the NPPES registry search returned no active entry matching the directory’s identifier.
Both readings address the same field: the provider’s registry listing.
Subject binding NOT established — the readings must not be combined.
The readings are dated: Sep 18, 2026 (directory) and Sep 22, 2026 (registry).
Rule: directory-vs-nppes-registry, version 1
Check this finding in your browser
Integrity
Not run.
Issuer recognition
Not checked.
Currentness
Not established.
Not run — invented example; nothing here is signed
An intact signature establishes that the signed material has not changed. It does not establish that the authority is right.
Signature checking is local. No checkpoint is included with this evidence.
Technical evidence +
Digests
Claimed excerpt sha256 7a9d31e6c05f4012b8d3e6c29f17a3d5e8c41b09a7f52d6318e5c0b9d42a77f6
Authority excerpt sha256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Canonical recipe
Canonical form: stableStringify — one canonicalisation, no second recipe (published on the Technical page with the downloadable verifier).
Signature
Signed scope: not established
Public key: not established
Dependency manifest sha256: not established
Issuer configuration
Issuer keys: /.well-known/woc-issuer-keys.json
Checkpoint reference: Currentness not established.
Technical evidence — the downloadable verifier, issuer keys, canonicalization and raw views.