A practical guide to spotting fabricated references, understanding the red flags, and protecting your organisation from bad hires.
Most employers trust the references they receive. After all, reference checking has been a cornerstone of the hiring process for decades. But that trust is increasingly misplaced. Fraudulent employment references are far more common than most HR professionals and recruiters would like to believe, and the consequences of accepting one can be severe.
This guide walks through the scale of the problem, the specific red flags to watch for, practical verification techniques you can use today, and the fundamental limitations that even the most diligent traditional checking methods cannot overcome.
Research from the CIPD (Chartered Institute of Personnel and Development) suggests that around 30% of candidates embellish or fabricate elements of their references. That figure is not limited to minor exaggerations. It encompasses a wide spectrum of dishonesty, from inflating job titles and extending employment dates to entirely fabricated references from companies where the candidate never worked.
The types of reference fraud employers encounter include:
The cost of getting this wrong is substantial. The CIPD estimates that a bad hire costs an average of around £12,000 for roles below senior management, factoring in recruitment fees, onboarding, lost productivity, and the eventual cost of re-hiring. For senior roles, the figure can be many multiples of that. Beyond the financial cost, there are risks to team morale, client relationships, regulatory compliance, and in some sectors, safeguarding.
No single indicator is proof of fraud on its own. But when multiple red flags appear together, they should trigger closer scrutiny. Here are the warning signs experienced recruiters and HR professionals learn to spot:
“The most dangerous fake references are not the obvious ones. They are the competent forgeries that look just plausible enough to pass a cursory check.”
Most employers rely on one or more traditional methods to verify references. Each has genuine value, but each also has fundamental weaknesses that sophisticated fraud can exploit.
Calling the referee to confirm the reference is one of the most common approaches. The problem is that the entire method depends on the phone number being genuine. If the candidate has provided a friend's mobile number, your call will reach a convincing impersonator who is expecting it. Unless you independently verify the phone number against the company's published contact details, phone verification only confirms that someone at that number is willing to vouch for the candidate.
Receiving a reference from a company email address provides more confidence than a personal address, but it is not bulletproof. Email spoofing (forging the sender address to appear as though it came from a corporate domain) is technically straightforward. While SPF, DKIM, and DMARC records can help email systems detect spoofing, not all companies have these configured properly, and not all receiving mail servers enforce them strictly.
A reference printed on company letterhead with an official signature carries a sense of authority. Unfortunately, company letterhead templates are trivially easy to recreate. A basic image search, combined with a word processor, can produce a convincing facsimile in under an hour. As more references move to digital formats, this method has become even less reliable.
The fundamental problem with all these traditional methods is the same: they rely on trust in the medium of communication rather than on any verifiable proof of authenticity. You are trusting that the phone number is real, that the email was not spoofed, or that the letterhead is genuine. The reference itself carries no intrinsic proof of who created it or whether it has been altered.
If red flags have raised your suspicion about a reference, here are concrete steps you can take to investigate further:
Even when employers follow every step above, traditional reference checking has structural limitations that cannot be resolved with more diligence alone.
Sophisticated fraud can defeat even the most careful manual checks. A candidate who has prepared thoroughly, with a convincing fake company website, a friend briefed on the details of the role, and a VoIP number that appears to be a landline, can pass every traditional verification step. The Arms Race between verifiers and fraudsters is one that manual methods are structurally unable to win.
Time pressure compounds the problem. Recruiters working to fill roles quickly, particularly in high-volume hiring environments, rarely have the bandwidth to phone-verify every single reference. When workloads are heavy, shortcuts happen. The references most likely to escape scrutiny are the ones that look just good enough not to raise immediate concern.
At its core, the traditional reference system depends on the honesty of the medium. A phone call is only as trustworthy as the number you dial. An email is only as trustworthy as the sending server. A letter is only as trustworthy as the paper it is printed on. None of these methods provide independent, verifiable proof that the reference is genuine. The information cannot authenticate itself.
The limitations of traditional reference checking all stem from a single root cause: the reference document has no way of proving its own authenticity. It relies on external signals (the email address, the phone number, the letterhead) that can be forged. Cryptographic verification solves this by embedding proof directly into the reference itself.
The concept is similar to how your browser verifies that a website is genuine. When you visit your bank's website, your browser does not simply trust that the page looks right. It checks a cryptographic certificate, issued by a trusted authority, that mathematically proves the site is operated by your bank. If anyone tampers with the connection, the proof breaks and your browser warns you.
The same principle can be applied to employment references. A digital signature is a mathematical proof that a specific document was created by a specific organisation and has not been altered since. The employer signs the reference with a private key that only they hold, and publishes the corresponding public key in their domain's DNS records, the same infrastructure that powers email delivery and website routing. Anyone can then verify the signature against that public key to confirm the reference is authentic.
This is the approach RefPassport takes, using Ed25519 digital signatures and DNS-based domain verification to create references that are mathematically impossible to forge. Anyone can verify the signature against the employer's public key, published in their DNS records, without contacting the issuing organisation.
For employers, this changes the calculus entirely. Instead of spending time phoning switchboards, cross-referencing Companies House, and scrutinising email headers, a verifier can confirm authenticity in seconds with mathematical certainty. The reference proves itself. No phone calls, no judgement calls, no room for sophisticated imposters to slip through.
For candidates with genuine employment histories, cryptographic references are equally valuable. They provide a portable, tamper-proof record that any future employer can trust immediately, eliminating the delays and friction that come with traditional reference checks.
The hiring landscape is evolving, and reference checking must evolve with it. Whether you choose to sharpen your manual verification practices or adopt cryptographic methods, the most important step is recognising that fake references are not a rare edge case. They are a routine part of the hiring landscape, and employers who fail to account for them are leaving their organisations exposed.
Everything employers and recruiters need to know about reference checks: types, legal framework, common mistakes, red flags, and how digital verification is changing the process.
10 min readHow GDPR affects giving, requesting, and storing employment references. Covers lawful basis, subject access requests, retention, and data minimisation.
Issue tamper-proof, domain-verified references that prove themselves. Free to start.
Get Started Free