Free · No account required · Works with any OB3 issuer

Verify any Open Badge 3.0 credential

Drop a .jwt file, paste a credential URL, or paste the JWT string directly.

Drop a .jwt or .json file here

or

Credentials are validated entirely in your browser. Files are never stored.

About this validator

What is Open Badges 3.0?

OB3 is the W3C-compatible digital credential standard governed by 1EdTech. Badges are cryptographically signed, holder-owned, and verifiable by anyone — no login required.

What we check

  • OB3 field structure
  • @context URLs
  • Expiry date
  • Issuer DID document
  • Cryptographic signature (ES256)

Which credentials work?

Any OB3 JWT-VC credential from any issuer using did:web. This includes credentials from CertLister, Open Badge Factory, and other OB3-native platforms.

JSON-LD format credentials are not supported in this version.

Frequently asked questions

Is my credential data stored?

No. Validation happens entirely in your browser. The only server request is to fetch the issuer's DID document for signature verification — your credential data never leaves your device.

Why does signature verification need a server?

Browser CORS policy blocks direct fetches to third-party issuer endpoints. We proxy that single request through our server so any issuer's DID document can be retrieved — your credential payload stays in the browser.

What does UNVERIFIED mean?

The credential structure is valid and it's not expired, but we couldn't fetch the issuer's DID document to check the signature — usually due to a network issue or the issuer's server being unavailable. The credential may still be authentic.

Does this work for credentials from other platforms?

Yes, as long as they're in OB3 JWT-VC format with a did:web issuer DID. Credentials from platforms like Open Badge Factory and other OB3-native issuers should validate correctly.

Ready to issue OB3 credentials?

CertLister issues cryptographically signed Open Badge 3.0 credentials — Pro plan. Free to start.