SleuthPost

My Audit of Three Background Search Tools: What the Data Got Wrong After 60 Lookups

A LinkedIn profile can make someone look like they updated their life yesterday. A court record can make the same person look frozen in 2015. Neither one is lying, exactly. They're just partial, and after more than sixty lookups across three paid services, that gap between "current" and "on file" turns out to be most of what these tools get wrong.

Three services, one spreadsheet, and nowhere near the dramatic energy people assume this takes. This is really a question of background-check accuracy, honestly — how far you can trust a public-records search, and how much digital safety that search actually buys you before you ever meet someone face to face. A woman I know online, Rhonda Tarkington, found my writing through a divorce-recovery group on Facebook a while back. She's run checks on maybe seven men in the time I've run past sixty, same worry, wildly different math, and neither of us is wrong about how much is enough.

Three Services, One Spreadsheet, No Benefit of the Doubt

Logging results somewhere boring is most of the method. Usually that happens with the overhead light off and nothing but the laptop throwing any glow at all across the kitchen table, which says more about my evening habits than my research rigor. I keep a Notion doc on every stranger with the same columns every time — name variants, address history, court filings, whatever a reverse number search turns up — so I can see where a free glance at one service and a paid pull from another actually disagree, instead of trusting my memory of "yeah, that one seemed fine."

None of these tools are magic. They're aggregators, pulling arrest logs, deed filings, marriage indexes, and old utility hookups from however many counties happen to have digitized their records, then stitching all of it into one profile with a face and a name on it. Whatever never got digitized at all just doesn't show up anywhere, clean report or not, and nothing about the stitching happens in real time, which is worth knowing before you trust a blank result.

Reading Court Records Without Trusting the Clock

Court records live and die by jurisdiction. A filing in one county doesn't automatically follow someone two counties over when they move, and small claims cases in particular tend to stay local in a way felony charges don't. None of this counts as a Fair Credit Reporting Act background check, either, which matters if you're trying to use what you find to screen a tenant or a job applicant instead of deciding whether to meet someone for coffee. And because consumer reporting rules put a lookback window on most civil judgments and old bankruptcies, a clean report sometimes just means the mess aged out of view, not that it never happened.

How Accurate Is a Public-Records Search, Really?

Accuracy, here, usually means accurate as of whenever a county last uploaded a file, not accurate as of today. I've watched a listed address sit two or three moves behind where someone actually lives, simply because no government office updates faster than it feels like. Frankly, most background checks are stuck in the past for reasons that have nothing to do with which service you picked and everything to do with how slowly public records move in general.

An address trail still tells you something, even slow. I've written before about why my date's address history mattered more than his bio, and the short version is that six-month leases strung together read differently than five years in one place, even when the most recent line on the report is a year or two stale.

Phone Numbers and Profiles Don't Always Tell the Truth

A phone number is borrowed more often than people assume. Carriers recycle disconnected numbers after enough time passes, so a reverse lookup can hand you the previous owner's name instead of the current one, with no obvious flag telling you which one you got.

Social profiles carry a version of the same problem. I ran a first date's name through LinkedIn once, expecting a current read on his career, and got a profile that hadn't been touched in four years — a job title and a city and a headline that all predated whatever he was actually doing now. Treating that as proof he'd been honest with me would have been exactly backwards.

A separate message that same season claimed to be from a property manager confirming a rental. Tracing the header out of curiosity, the reply-to address routed to a post office box somewhere in Nevada, nowhere near the property or the person it supposedly came from. That's the kind of detail a records search won't catch and a two-minute header check will.

Relatives and Common Names Can Scramble a Report

That "possible relatives" list is more useful for spotting a pattern than for catching a lie, since most people really are related to who the database says they're related to. Common names are where it gets messy. Two men sharing a first and last name in the same metro area will cross-contaminate each other's report unless you can narrow things down by a middle name or a birth year, and a legal name change from a marriage or a filing can knock someone's entire history loose from the rest of their file for years afterward.

Does a Clean Business License Mean Anything?

Registering a business with the state tells you someone filled out paperwork, not that they're good at the job, and I don't confuse the two anymore. Employment history pulled from a people-search service has the same limit. It's assembled from whatever data brokers could buy or scrape, not a call to HR, so a gap in it might mean nothing more than an employer who never reported to the right database.

Property records are the one category that's held up consistently well in my spreadsheet, probably because deed filings get recorded county by county with more urgency than the rest of this data gets, and a name on a title is about as hard to fake as any of this gets.

Why I Still Pay for Three Subscriptions Instead of One

None of the three services I pay for pull from identical sources, which is the actual reason I keep all three instead of picking a favorite. One has consistently sharper coverage inside Arizona specifically. Another reaches further into other states' court systems. The third is hit or miss on both but occasionally turns up a record the other two missed outright.

They're not cheap, and the billing tends to auto-renew in a way you have to watch for, which is its own small tax on staying vigilant. People can also remove themselves from some of these databases entirely, so a blank report occasionally means someone opted out, not that there's nothing there — one more reason a blank result should raise a question instead of settling one.

My brother Owen is the person I run most of this past before any of it goes public. If a workflow I'm describing would make him uneasy about his own data showing up the same way, I rewrite it. We got into exactly this argument over fruit at the Gilbert Farmers Market once, about whether a blank result from a single service should ever be trusted on its own. His answer, and now mine: never run just one search before a decision that actually matters. Pull the same name through a second service before trusting either a clean report or a scary one, because it's the disagreement between the two that tells you something, not either report by itself.

Related Articles