District of Columbia (state-level) DBA search — how to look up a fictitious business name (DC)
A DBA (doing business as) or fictitious business name filed in District of Columbia is a sole proprietor or partnership saying “I’m operating under a name other than my legal name.” It is not a registered entity like an LLC or corporation. Many underwriters skip the DBA step and miss the actual owner. If someone tells you they operate under a DBA in DC but haven’t incorporated, you need that filing to tie the trade name to the person behind it.
What a District of Columbia DBA actually is
A DBA is a legal notice that a person or partnership is using a business name that differs from their legal name or the partnership’s registered name. It does not create a separate business entity. The owner remains a sole proprietor or general partner. If you’re underwriting a $50K equipment-finance deal and the applicant says “I do business as Joe’s Plumbing Supply” but is legally registered as a sole prop under “Joseph M. Kowalski,” the DBA filing connects the dots. Without it, you’re verifying the wrong name on credit bureaus and UCC searches.
In District of Columbia, DBA filings are maintained at the county or city level, not at the state corporation office. This is the opposite of states where the Secretary of State handles assumed names. The distinction matters: a state-level LLC filing and a DBA filing live in different places, and many underwriters only check the state office and miss the DBA entirely.
How to search for a DBA in District of Columbia
District of Columbia is not a traditional county structure; it’s a single municipal jurisdiction. DBA filings (also called “fictitious business names” or “assumed names”) are recorded through the District of Columbia’s business licensing and regulatory apparatus, not through a county recorder.
To find a DBA filing in DC, start with the District of Columbia’s business records portal or the Office of the Deputy Mayor for Planning and Economic Development. These offices maintain the public record of assumed-name filings. You will need the business name, the owner’s name, or both. Some portals allow name searches; others require you to know at least one piece of information. If you have the trade name, search for it. If you have the owner’s legal name, search for that.
The search will return filing date, expiration date (if any), the legal owner’s name, and sometimes a business address. Write down the filing number and the date. This matters for your file: if a DBA expired and the owner never renewed it, the operator may no longer be legally entitled to use that name.
What a DBA filing shows (and what it does not)
A DBA filing shows: - The trade name (the “doing business as” name). - The legal name of the owner(s). - The filing date and expiration date. - Sometimes a business address.
A DBA filing does not show: - Whether the owner is creditworthy. - UCC liens or judgments. - Whether the owner has other DBAs. - Tax status or business revenue. - Officers, managers, or beneficial owners beyond the registered name.
This is why a DBA lookup is a first step, not a complete verification. After you find the DBA, you still need to run a credit check on the owner’s legal name, search UCC filings, and verify the owner’s identity. A DBA filing is a single fact: this person is using this name.
DBA vs. registered entity: the critical difference
Underwriters often conflate DBAs and registered entities, and this mistake kills deals. Here is the difference:
A registered entity (LLC, corporation, partnership) is filed with the state, has its own EIN, can hold property and debt, and has formal governance. You can verify it through the Secretary of State.
A DBA is filed locally, does not create a separate legal entity, and does not have its own credit file. The owner remains personally liable for all business debts. If you run a credit check on “Joe’s Plumbing Supply” and nothing comes back, but you’ve never checked “Joseph Kowalski,” you have no credit history.
If an applicant has a DBA but no LLC or corporation, the personal credit and UCC history of the owner are what matter. If an applicant has an LLC and a DBA (using a trade name for the LLC), verify both: the LLC in the state registry and the DBA locally, to confirm the LLC is the registered owner of the DBA.
Common DBA traps in underwriting
Expired DBAs. A DBA that expired 18 months ago is not valid. If the applicant is still using that name, they’re operating without a current filing. This is a compliance red flag and can indicate sloppy operations or a cash business that avoids formal licensing.
No DBA on file. An applicant claims to operate under a trade name but the DBA search returns nothing. Either they never filed, they filed under a different name, or they incorporated instead and the DBA is tied to the LLC. Always ask the applicant directly why the DBA is missing and request a copy of the filing.
Multiple DBAs under the same owner. It is legal for one person to file multiple DBAs. But if the applicant has five DBAs, five business licenses, and five different trade names, ask why. Sometimes it’s legitimate (a person who genuinely runs multiple ventures). Sometimes it’s a sign of rapid pivoting or a hustle-to-hustle operation that hasn’t stuck to one business model.
DBA filed to an address that is a virtual mailbox or serviced office. A DBA address is not proof of a real location. If the applicant’s DBA address is a UPS store or a co-working space, it’s not a red flag by itself, but it is a signal that you need to verify the actual business location separately.
Bottom line
A DBA search in District of Columbia is a required step if the applicant operates under a trade name. The filing connects the trade name to the owner’s legal name, and the owner’s legal name is what you verify for credit, UCC, and beneficial-ownership checks. Do not skip the DBA search and do not treat a DBA as a registered entity. If you’re running these lookups manually across multiple jurisdictions, you’re spending hours on data entry and cross-referencing. A consolidated business-verification tool that pulls DBA records, state registries, and UCC filings into a single report eliminates the legwork and reduces the risk of a missed filing.