Identifying Address Fraud During Skip Tracing

The address shows up on three different databases. Same street, same unit, same ZIP. Looks solid. You drive out, knock, and a nice lady in a bathrobe tells you she's lived there eleven years and never heard of your guy. And she's telling the truth.

So what happened? Maybe your subject moved. Maybe somebody fat-fingered a record years ago and every data company copied it. Maybe your subject used that address on purpose to throw people off. Or maybe somebody stole his identity and he's never set foot on that street in his life.

That's the whole problem with address fraud in skip tracing. A bad address can be an honest mistake, a stale record, or a deliberate lie, and from your car they all look exactly the same. Here's how to tell the difference, verify before you burn attempts, stay inside the legal lines, and write it up without calling anybody a criminal.

By Mighty Mike Reid

The Big Rule: A Bad Address Is Not Automatically Fraud

Let's get this out of the way first.

Address fraud generally means somebody intentionally used false or unauthorized address information to mislead investigators, creditors, courts, businesses, or government agencies. That could be a location that doesn't exist, somebody else's house, a commercial mailbox, or an old address they know is dead, all to hide where they really are.

But a wrong address does not prove any of that. Bad information comes from a lot of boring places:

  • A recent move

  • A clerical error

  • A mixed consumer file (two people with similar names merged together)

  • A family mail arrangement, like an adult kid still getting mail at mom's house

  • Identity theft

  • Databases that haven't caught up yet

Here's how I think about it. When I was serving, I noticed it's a bell-shaped curve. You get a few crazy weirdos on one end and a few super good people on the other end who almost never get served. But everybody in the middle who gets served is just your average Joe. They're not trying to hurt anybody. Most people with a bad address on file aren't running a scheme. Their life just moved faster than the database did.

So the rule is simple. You document facts. You don't decide somebody's a fraudster. That call belongs to the court, the client, or law enforcement, not the server.

How Bad Addresses Wreck a Serve

Whether it's fraud or just a stale record, a bad address costs you. It causes:

  • Delays. Every wasted attempt pushes the serve closer to the hearing date.

  • Cost. Somebody's paying for that gas and that time, either the client or you.

  • Wrong people getting bothered. Unrelated residents end up dealing with a stranger on their porch about somebody they never met.

  • Papers landing with the wrong person or at the wrong place.

  • Challenged service. This is the big one. If you do substituted service at an address that isn't actually the recipient's dwelling, that service can get challenged. Now your affidavit is the one everybody's picking apart.

And here's something a lot of people miss. False information spreads. One bad record gets bought, sold, and copied by data company after data company. So when you see the same address on five different sites, that's not five confirmations. That's one source wearing five different hats. Duplicate database listings are not independent verification.

Warning Signs Something's Off

None of these prove fraud by themselves. They're reasons to slow down and dig before you drive.

Records that don't agree. One source says residential, another says it's a business, another puts your subject in a different state. When the records fight each other, find out why before you pick one.

Rapid address churn. A bunch of address changes in a short window. Could be somebody dodging. Could also be a divorce, a job change, or couch surfing. Write down the dates and look for a pattern.

A commercial property listed as a home. Watch for coworking spaces, virtual offices, registered agent addresses, and commercial mail receiving agencies (CMRAs, the private mailbox stores). A "Suite 214" that turns out to be a box at a mailbox store is not where anybody sleeps. Somebody can't live at a registered agent's office, either.

Nonexistent or incomplete addresses. A house number that skips right over the real ones, a street that doesn't exist in that city, or an apartment complex address with no unit number.

A lot of unrelated people at one address. When twenty different names with nothing in common all point at one house, that address might be a mail drop, a shelter, a halfway house, or a data mess. It's not a confirmation your guy lives there.

Vacant or demolished properties. If the house is boarded up, or it's a dirt lot, your subject isn't living there no matter what the database says.

Repeated denials from current residents. One "never heard of him" doesn't mean much. People lie to servers all the time. But when the current residents tell you the same thing on attempt after attempt, and their story lines up with the property records, believe the evidence.

Get the Information Before You Burn Attempts

Most bad-address problems start at intake, not in the field.

When an order came in, I asked the same questions so much. Do they work? What time do they work? What kind of car do they drive? Do you have a picture of them? With those answers I could serve almost everybody on the first attempt. Why? Because a person isn't just an address. They're a schedule, a car, and a face. If the house turns out to be wrong, you still know where they work and what they drive. And when somebody sends you to an address and can't answer a single one of those questions, that tells you how much homework was done on that address in the first place.

Then do your own homework. Use Google the right way. Put the full name in quotes and Google keeps it in that exact order. Add "site:" with a specific website, like a county court site or a local news site, and you only get results from that site. It's a basic trick, but it's one of the best free skip tracing tools out there.

I used to charge $75 or $150 for a skip trace. And you don't need Social Security numbers or anything like that to figure out where to serve somebody. You need good public records, a little patience, and the discipline to verify before you drive. (Those office verification visits some big skip tracing vendors require? That's mostly for their own insurance purposes. It doesn't tell you where your guy sleeps.)

Bad leads waste attempts fast. I had a law firm client once with serves all over the place out of town, and some of the addresses we attempted were just bad. He sent new addresses and a phone number. Every one of those bad addresses meant another trip and another charge. Better info up front would have saved everybody money.

Tools That Actually Help

Address verification software. Great for confirming an address exists and is mailable. But mailable doesn't mean anybody lives there. A CMRA box is perfectly mailable. So is a vacant house.

Cross-referencing independent sources. The key word is independent. Property and tax records, court filings, business registrations, professional licenses, voter info where you can legally get it, vehicle records where you're authorized, utility info where lawful, what your client knows, and what happened on prior attempts. When sources that don't copy each other agree, that means something.

Maps and geolocation. Pull it up on a map and street view before you go. Is it a house, an apartment complex, a strip mall, a UPS Store, an empty lot?

Social media. Public posts can confirm a lead, show you a car, a workplace, or the house in the background of a photo. But you never use deception to get into a private account. No fake profiles, no friend requests under a made-up name. If it's private, it's private.

Property and postal research. Deed and tax records tell you who owns a place and where the tax bill goes. The U.S. Postal Inspection Service warns about people filing false change-of-address requests to divert mail, so a forwarding trail is a lead, not gospel.

A Simple Verification Process

Here's how I'd run it before calling any address good or bad:

  1. Identify the source. Where did this address come from? The client, a database, a court filing, a returned piece of mail? Write it down.

  2. Build an address timeline. Every address gets a date and the source it came from. That's how you separate the old stuff from the new leads.

  3. Confirm the property type. House, apartment, business, mailbox store, registered agent, vacant lot.

  4. Compare independent records. Do sources that don't copy each other agree?

  5. Verify the subject's identity. Make sure the person tied to that address is actually your person, not a same-name cousin, not a Jr., not a mixed credit file.

  6. Do a field check. Lawfully, from where you're allowed to be.

Field Check: The Hard Lines

You can observe a lot from the street. You can knock on the door. You can ask a property manager a few limited questions, like whether a person by that name lives there. You can't do whatever you want to get an answer.

  • No trespassing. If it's posted, gated, or you've been told to leave, respect it.

  • No opening mailboxes. Not to peek at names, not to check for mail, not ever. That's federal territory.

  • No impersonating anybody. Not a postal carrier, not law enforcement, not an investigator if you're not one.

This one's personal for me. I used to show up with a box like I had a delivery. But I never put FedEx or anything like that on it. One of the attorneys I worked for told me that's giving false representation, and that can get the case thrown out. Think about that. You spend all that time finding the guy, and the whole serve gets tossed because you pretended to be somebody you weren't. Not worth it. Never pretend.

Confirm the Person, Not Just the Address

Before you decide an address is fake, make sure you'd even recognize your subject.

I had a serve once, a restraining order, where I scrolled through the subject's social media. I could see a brand new Audi, I could see her in front of her dad's house, I could figure out where she worked. So I drive to the work, and the new Audi is sitting right in front of the radiology department. I go in, ask for her, and they bring out this gal who looks completely different than her pictures. Four feet tall. Brown hair, not blonde. But it was definitely her. She had a name badge on.

I always say there's the online social look and then there's the in-person look. When I'm looking at social media, I'm looking for the one photo that looks like the in-person look, usually something somebody else tagged her in. If I'd gone off the glamour shots alone, I might have walked away thinking I had the wrong person, or worse, that the whole lead was bogus.

Same goes for addresses. If you can't confirm who your subject actually is, you can't confirm whether an address belongs to them. Identity first, then the address.

Document Facts, Not Accusations

Your job is to write down what you saw. Not what you think somebody's up to.

Bad: "Subject is committing address fraud."

Good: "Address listed on the order is a commercial mail receiving agency. Staff stated they cannot confirm whether the subject rents a box. No residence observed at this location."

Bad: "Resident lied to me."

Good: "Adult female resident stated she has lived at the address for 11 years and does not know the subject. County property records show the same owner since 2015."

Bad: "Fake address."

Good: "No house number 4420 exists on this block. Numbers observed run from 4410 to 4416, then 4424."

Neutral, observable, dated. That's the report a judge can trust, and it's the report that protects you if anybody ever challenges the serve.

A process server documents facts. A server doesn't accuse anybody of a crime. If you think something's off, tell your client what you found and let them decide what to do with it.

Know the limits that apply to you. Privacy laws, consumer reporting laws, and licensing rules control what data you can pull and how you can use it, and they're different from state to state. Check your own state's rules before you run a search you've never run before.

A few public resources worth knowing:

Knowing these exist helps you explain to a client why a bad address might not be your subject's doing at all.

For Attorneys and Firms Hiring a Server

If you're an attorney, paralegal, or firm, here's how to get fewer wasted attempts and a cleaner affidavit.

Send everything up front. Last known address, where it came from and when, employer, work hours, vehicle, a photo, and any other addresses you've seen. The more you give, the fewer attempts you pay for.

Tell your server where the address came from. "Client's ex says he moved here last month" and "pulled from a database in 2022" are two very different leads.

Don't count duplicate database hits as confirmation. Five sites showing the same address may all trace back to one bad record.

Ask before you approve substitute service. If the address hasn't been verified as the subject's dwelling, a sub-serve there can come back to bite you.

Read the report for facts. "Resident stated subject does not live here" is a fact. "Subject is hiding" is a guess. Good servers keep those separate.

Where Mighty Process Server Fits

Every one of those facts needs to live somewhere your client can see it. Mighty Process Server keeps it on the job itself: every attempt, your notes, GPS, and photos in one place. Clients get their own private portal, so when they ask why you stopped attempting the address on the order, the answer's already there with a timestamp and a picture of the empty lot.

The affidavit builds right from the job. When it needs a notary, the Mighty Notary integration gets it signed and notarized right in the app.

When the Real Address Is Out of Town (or Out of the Country)

Sometimes you do all this work and find out the address on file was bogus because your subject moved three states away. Or overseas.

That's what Mighty Process Server is built for. Address search covers more than 171,000 cities worldwide. Servers set their own fees area by area or upload a fee schedule as a CSV, and clients get an instant quote. So when the good address turns out to be in Phoenix or Manchester, you can find a local server there and order the serve without calling around for a week. A local server knows the neighborhoods and can verify that address in person, which is exactly what a shaky lead needs.

Mistakes to Avoid

  • Treating five database hits as five confirmations

  • Accusing a resident, or your subject, of lying or committing a crime in your report

  • Doing a sub-serve at an address nobody verified

  • Opening mailboxes, trespassing, or pretending to be someone you're not

  • Skipping intake and driving out with nothing but an address

Quick FAQ

Is an outdated address fraud? No. Outdated is the most common reason an address is wrong.

Is a PO box fraud? No. Lots of people use PO boxes for privacy or convenience. It's just not a place you can serve someone at home.

Does returned mail prove the subject doesn't live there? No. It's a clue, not proof.

Should I tell my client the subject committed fraud? No. Report what you observed and let them draw conclusions.

If the same address shows up on multiple databases, is it confirmed? No. Duplicate database results often come from the same original source.

The Bottom Line

Do this long enough and people start saying "go to Mike, he'll find him." That reputation doesn't come from guessing. It comes from verifying.

A bad address is a question, not an answer. Most of the time it's a move, a typo, or a stale database. Sometimes it's something worse. Either way, your job is the same. Get good info at intake, check independent sources, confirm the person, stay inside the lines in the field, and write down what you saw in plain, neutral words.

Stay sharp. Stay informed. Live Mighty!


Read the full article at www.mightyprocessserver.com


This article is published by Process Server Daily, powered by MightyAutomation.ai, the leader in legal support intelligence.