01
Three wrong answers
Every one of them returns something.
A workflow that takes a business name and matches state corporate filings returns nothing for a DBA-only business — the state never registered the trade name, and the DBA lives at the county. A workflow that treats the DBA as the entity returns a confirmation that never mentions the legal party. And a workflow that matches a DBA to a similarly named entity returns a match that is simply wrong.
The throughline: a DBA is a connection between a public name and a legal entity, not an entity in itself. Verification has to resolve the connection.
Three wrong answers
All of them look right
01 · Name in, state filing out
- In
- “Green Thumb Landscaping”
- Back
- No result
The Secretary of State never registered it. The LLC is “GTL Services LLC” and the DBA sits at the county. The two systems do not coordinate.
02 · DBA treated as the entity
- In
- “Green Thumb Landscaping”
- Back
- Verified
The customer-facing brand is confirmed. The party that signs contracts and owes debts is not mentioned at all.
03 · DBA matched by name
- In
- “Green Thumb Landscaping”
- Back
- Matched — wrong entity
A franchisor’s DBA in one state and a franchisee’s in another share text and resolve to different legal parties. Matching on the name manufactures a false positive.
Failure modes as described
02
The stack
Coverage, coherence, lifecycle.
A DBA stack is every trade name registered to one legal entity across every jurisdiction it has filed in. Coverage is the shape: one DBA in one county is the simple case; twelve across nine counties and three states is a multi-brand strategy, a multi-location operation, or both.
Coherence asks whether the portfolio makes sense. Three regional retail brands under a holding company is coherent. One in food service, one in construction and one in financial services is either diversification or something to understand better.
Lifecycle is the dates. Abandoned DBAs often mark business lines tried and dropped — and repeated short-lived DBAs at one address in one line of business is the continuity attempt described in the phoenix article.
03
Worth watching
Three patterns, all detectable only from the entity side.
The serial single-use DBA: file a name, run a campaign, accumulate complaints, abandon it, file another. The legal entity is stable while the names cycle, and the pattern is visible only by linking the DBAs back to the entity and reading its history.
The franchise look-alike: a DBA that resembles a well-known or regulated trade name, registered at a county, with an underlying entity that has no connection to the brand.
And the shared DBA across distinct entities — which may be a franchisor and its franchisees, or unrelated parties with a name collision. Telling those apart needs officers, addresses and ownership, not the name.
04
The point
Most DBA filings are honest commerce.
The mechanism exists so a business can trade under a name customers recognise, and the overwhelming majority of filings do exactly that. The reason to read them carefully is not suspicion — it is that the trade name is the layer a customer sees and the legal entity is the layer a contract binds, and a verification that conflates the two has answered a different question from the one asked.