How to check if a certificate is fake or real

TRUE helps issuers issue verifiable documents so authenticity can be checked instantly via QR code or a verification portal, which reduces the chance that a forged PDF is accepted as genuine.

No. TRUE supports many document types, including diplomas, licenses, memberships, transcripts and vouchers.

No. TRUE supports custom domains, so documents live on your own domain.

You can start with dashboard issuing, then move to automation. TRUE also supports email-based issuing and a REST API (5 endpoints).

PDFs can be edited and re-shared without a reliable verification method. TRUE documents are blockchain-secured, tamper-proof, and verifiable forever.

The most telling signs are poor print quality, inconsistent typography, and missing verification details. Fake certificates often use slightly wrong logos, mismatched fonts, or uneven spacing that wouldn't pass quality control at a legitimate issuing organisation. Look for missing certificate numbers, absent security features, and vague language that avoids specifics about what was certified. Legitimate certificates include precise details: the credential name, issuing authority, date, and a way to verify authenticity. If any of these are missing or look off, investigate further before accepting the credential.

Start by contacting the issuing organisation directly using contact details from their official website, not from the certificate itself. Many certification bodies offer online verification portals where you can enter a certificate number and confirm validity. For blockchain-secured credentials, verification is instant: scan the QR code or visit the verification URL to check the credential against an immutable blockchain record. This is the fastest and most reliable method, requiring no phone calls or waiting. If the issuer doesn't offer digital verification, request confirmation in writing from their registrar or certification department.

Check for blurry or pixelated logos, which indicate the forger used low-resolution images. Look at font consistency. Legitimate certificates use carefully chosen, consistent typography throughout. Examine alignment: text should be evenly spaced and properly centred. Check colour accuracy against the issuer's brand guidelines. Inspect signatures for signs of digital pasting (sharp edges, inconsistent backgrounds). Security features like embossed seals, holograms, or watermarks should feel and look consistent with known authentic examples. Any visual inconsistency warrants further investigation through the issuer's official verification channels.

Authentic certificates contain specific, verifiable details: unique certificate numbers, precise credential titles, issuer identification, and verification mechanisms (QR codes, verification URLs, or registry numbers). Fake certificates often use generic language such as "certificate of completion" without specifying what was completed. Authentic credentials reference specific programmes, standards, or qualification frameworks. Fake ones stay vague to avoid easy checking. Most critically, authentic blockchain-secured certificates have cryptographic records that can be verified instantly, while fakes have no corresponding record. The difference is absolute: either the blockchain record exists or it doesn't.

Verify every credential that is material to the hiring decision, especially certifications required by regulation, safety qualifications and professional licences. Cross-reference certification dates with the candidate's employment history to check plausibility. Ask candidates to provide verification links or certificate numbers, then check through the issuer's official channels. Watch for candidates who resist verification, provide excuses for delays, or offer alternative documents when you request specific credentials. Establish a standard verification procedure so every hire gets the same scrutiny. Document verification outcomes for compliance records.

The most effective technology does not detect fakes. It makes faking impossible. Blockchain-secured credentials create an immutable record when issued. Verification is a mathematical comparison: does the credential's cryptographic hash match the blockchain record? If yes, it's genuine. If no, it's been altered or was never issued. This approach is superior to AI-powered detection, which must constantly update to catch new forgery techniques. Blockchain verification is permanent and absolute. No amount of sophistication can forge a credential that has no corresponding blockchain record.

Organisations that hire based on fraudulent credentials face regulatory penalties, professional liability, and reputational damage. In regulated industries such as healthcare, construction and financial services, employing unqualified individuals can result in fines, licence revocations and legal action from affected parties. If a workplace incident traces back to an unqualified employee, the hiring organisation may bear liability for negligent credentialing. Insurance coverage may be voided if required qualifications weren't properly verified. Beyond legal exposure, credential fraud undermines workforce quality, team trust, and organisational credibility with clients and partners.

Modern forgery tools have made credential fraud disturbingly accessible. PDF editing software can modify any digital certificate, changing names, dates or credential levels in minutes. AI-powered tools generate realistic signatures, seals, and layouts. Online services sell custom-designed fake certificates that replicate specific issuers' branding. Template marketplaces offer ready-made designs for common credential types. Some fraudsters create entirely fictional issuing organisations with professional-looking websites. The quality of forgeries has increased dramatically, making visual inspection alone unreliable. Only cryptographic verification against an immutable record provides certainty.

Follow a structured verification process: First, request the original credential or a verifiable digital version with a certificate number. Second, identify the issuing organisation and locate their official verification channel (not contact details from the credential). Third, submit the verification request: scan the QR code for blockchain credentials, use the online portal for digital registries, or contact the issuer directly. Fourth, confirm that the credential details (name, date, qualification level) match what the candidate presented. Fifth, document the verification result. For high-volume hiring, consider platforms that automate credential verification at scale.

TRUE eliminates certificate fraud at the source. Every credential issued through TRUE is written to blockchain creating a permanent, tamper-proof record across thousands of independent computers. When someone needs to verify a TRUE credential, they scan the QR code for instant confirmation. No phone calls, no waiting, no ambiguity. The credential either has a valid blockchain record or it doesn't. TRUE credentials live on the issuer's own domain, are eIDAS compliant, and have been used to issue 500,000+ documents for 200+ organisations across 15+ countries. That is not fraud detection. It is fraud prevention by design.

This message means the certificate you scanned is a copy, whether a photocopy, screenshot, scan or reprint, and not the original TRUE-secured document. It's a security feature working exactly as intended: TRUE certificates are bound to their original, so a duplicated copy is automatically flagged. If you're verifying someone's credential and see this message, ask them for the original certificate (the one they received directly from the issuer) and scan that. A genuine TRUE certificate will verify as authentic and show its full details. If someone can only provide a copy that triggers this message, treat the credential as unverified until you can check the original. This is the difference between a document that looks official and one that is provably authentic.

Scan the certificate's QR code or enter its verification URL at trueoriginal.com/verify. It's free, no account needed. A genuine TRUE certificate verifies instantly against the blockchain and shows the issuer, recipient and issue date. That proof comes from cryptographic mathematics, not from trusting a website. If a certificate has no verifiable QR code or URL, that itself is a warning sign. For certificates not secured by TRUE, ask the issuing organisation to confirm directly, and check for the warning signs of forgery (inconsistent fonts, missing security features, unverifiable issuer details).