Certificates and public verification
Who can look up that diploma?
Certificate plugins often publish learner names and completion details on public verification pages. Some use long random IDs; others accept searchable IDs or directory lookups. Generated PDFs may sit in the media library or a protected path. Course progress itself has a separate page. Compare the documented setups below.
Based on plugin documentation, not tests of your site. Verification settings, ID formats, and PDF storage decide what outsiders can see. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on a verification or certificate page, including fonts or embeds when they load. It does not inspect server-side PDF generation or storage, vendor credential APIs, or whether a certificate ID can be guessed from another ID.
Public verification vs vendor credentials
Certificates verified on your WordPress site
List what a public verification page shows when someone has a link or ID. Prefer non-guessable IDs when verifiability does not require searchable numbers. Check whether PDFs live in the media library or a protected path, and whether download links appear without a login. Document how long credential records remain after a course is removed.
Credentials issued through a vendor service
Some connectors issue certificates or badges through an outside credential platform when a course completes. Learner details used for issuance can be sent to that service. Server-side transfers do not appear in a browser page scan. Review the fields sent, the vendor template, and where verification happens after issuance.
Certificate setups
No paid placement. Site-hosted certificate tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still publish learner names on purpose when verification is enabled. Names are alphabetical within each group.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 24TT Document Verifier Documented self-hosted document verification portal. Records can store a verification ID, recipient name, grade, issuing authority, expiration, and a PDF or JPG attached through the WordPress Media Library. Global settings can show a download or view link on the public success screen and can hide whole categories from public search. The listing says data stays on your WordPress database and server. Review which fields and file links appear after a successful lookup. Browser hosts were not verified for this snapshot. | Verification and certificates on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Academic Certificate Verification Documented self-hosted verification with clean permalinks that include a certificate ID and verification code. Visitors can search by certificate ID and an optional verification code; a verified result can show student credentials and status. Pro documents PDF download on the verification page and a public certificate directory and search table. Review ID formats, whether a directory is enabled, and where PDF files are stored. Browser hosts were not verified for this snapshot. | Verification and certificates on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Meadow Credentials Documented self-hosted credentials with public verification URLs and an Open Badges JSON endpoint. The listing says the plugin does not connect to external services, and verification QR codes are generated locally in the browser. Sensitive evidence can be stored in an encrypted vault outside the media library with randomised filenames. The listing warns that Nginx ignores the vault's .htaccess rule and may need an additional server rule to block public access. Its setup screen checks for exposure and provides that rule. Check your server configuration separately from encryption and filenames. Review which learner fields appear on the verification page and what remains after evidence is shredded. Browser hosts were not verified for this snapshot. | Verification and certificates on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| PressPrimer Certificate Documented self-hosted certificates for LearnDash, LifterLMS, Tutor LMS, and LearnPress. The listing describes unique non-guessable credential IDs, rate limiting, and a public verification page that anyone can use without an account. Share pages, verification results, and PDF downloads can open without signing in and can show the recipient name, title, issuer, dates, and any merge fields on the design (including email if the template uses that field). PDF and QR generation are described as local on your server. Review templates, what the verification page shows, and retention after a course is removed. Browser hosts were not verified for this snapshot. | Verification and certificates on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| CertifyMe for LifterLMS Documented LifterLMS connector that issues digital credentials through the CertifyMe platform when a student completes a course. Settings use an API token, template ID, and server region. Errors can be logged under uploads in a directory the listing describes as protected from public access. Learner credential issuance and verification can therefore run through the vendor service rather than only on your site. Review which learner details the CertifyMe template includes. Browser hosts were not verified for this snapshot. | Credentials issued through a vendor service | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented certificate and verification workflows, not tests of your site. Consent timing, whether certificate IDs can be guessed, PDF directory listing, and retention lengths have not been assessed. Check verification page fields, ID formats, PDF storage, and any vendor credential connectors. Course progress and enrollment are covered on the LMS page.
Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress LMS plugin privacy
- WordPress file upload plugin privacy
- WordPress QR code plugin privacy
- All privacy guides
/wp-certificate-plugin-privacy