Verify the issuer behind a certificate
Prove control of your organisation's domain by publishing your issuer DID, so recipients and employers see a verified issuer on the certificate page.
A signature proves that a certificate came from a particular key. It does not prove that the key belongs to the university or company named on the page. That gap is where a fake issuer can look convincing.
Issuer verification closes it.
How to verify a domain
Open Settings, then Issuer Verification, and add the domain you want to claim. Publish your issuer DID in one of two places:
https://your-domain.com/.well-known/verifycate-issuer.json- a DNS TXT record at
_verifycate.your-domain.com
Then choose Check. The claim moves from pending to verified when the DID matches. A failed or expired claim stays visible with its status, so the workspace can see what needs attention.
What the badge means
A verified issuer badge appears on the public certificate page when a viewer resolves the issuer. The certificate stores the issuer DID; the verification claim is resolved separately. Adding or changing a claim later updates what the next viewer sees — no reissue, no new certificate, no broken link.
Manual verification is available as an admin override for organisations that cannot publish a DNS record. The override records who verified the claim and when.
What it does not mean
Domain control is not accreditation. A verified issuer has proved that it controls the domain, not that it is a licensed institution, an approved training provider, or a member of any scheme. The badge says "this domain belongs to this issuer"; it does not say "this programme is recognised".
Issuer verification is a Pro feature.
Related