Baltimore City DBA search — how to look up a fictitious business name (MD)
A DBA (doing business as) or fictitious business name is not a separate legal entity. It is a registration that lets a person or business operate under a name other than their legal name or corporate name. In Baltimore City, Maryland, a DBA lookup tells you who filed the name and when it expires, but it does not tell you that the business is licensed, insured, or creditworthy. For underwriting purposes, a DBA search is one piece of a larger verification puzzle.
What a Baltimore City DBA filing actually shows
A fictitious business name registration in Baltimore City records the following: the DBA name itself, the legal name of the owner (person or entity), the owner’s address, the date the name was registered, and the expiration date of the registration. Some filings also show a business description or mailing address separate from the owner’s residential address.
What it does NOT show: corporate standing, tax compliance, liens, judgments, or whether the owner is the same person who will sign for credit. A DBA is a filing, not a credential. It means someone paid a fee to use a trade name legally. That is all.
Where to search Baltimore City DBAs
Baltimore City maintains fictitious business name records through the city’s Office of Finance. These records are public and searchable by name. You can search by the DBA itself or by the owner’s legal name. The search returns the filing date, expiration date, and registered owner information.
A DBA in Baltimore City is valid for five years from the date of filing. After five years, it must be renewed or it expires. An expired DBA does not mean the business has shut down · it means the registration lapsed. A business operating under an expired DBA is operating without current registration, which is a compliance red flag.
When you pull a Baltimore City DBA record, check the expiration date first. If it is within 60 days of expiring or already expired, flag it in your file. If the applicant claims they are still using the name, ask for proof of renewal or a new application. Many small operators let these lapse accidentally.
DBA owner vs. corporate owner: a critical distinction
Here is where DBA lookups trip up underwriters. If your applicant says they own a business called “Metro Plumbing” and you find a DBA filing in Baltimore City, the registered owner on that filing is the person you need to verify further. That person is the one liable for the debt if the business entity is not a registered corporation or LLC.
If the DBA is owned by a corporation or LLC, that entity name will appear as the registrant. You must then look up that entity separately in the Maryland Secretary of State to confirm it exists, is in good standing, and to identify the officers or members. A DBA filing does not replace a Secretary of State lookup. It supplements it.
Many underwriters make this mistake: they find the DBA, see a person’s name, and assume verification is complete. Wrong. You need to know (1) is the person creditworthy, (2) does the entity behind the DBA exist in good standing, and (3) are there liens or judgments against either the person or the entity. A DBA search answers only the first part of question one.
Why you cannot credit a DBA alone
A DBA is registration, not incorporation. If you approve credit based only on a DBA filing and the applicant defaults, you have no claim to business assets, no clear lien priority, and no corporate liability shield. The DBA itself is not a debtor · the person or entity that filed it is.
Underwriting to a DBA requires you to also verify the underlying legal owner. If it is an individual, pull a UCC search against them in Maryland and any other state where they may own property or have filed. If it is a Maryland entity, pull the Secretary of State record to confirm standing, then pull UCC records for the entity itself. If the entity is foreign (incorporated in another state), pull records there as well.
A DBA in Baltimore City is often the first signal that your applicant is a sole proprietor or a small LLC. Use it as a starting point, not as a finish line. Many small operators use a DBA because they have not incorporated or because they prefer to keep the LLC’s name private. Either way, your job is to trace the liability back to the person or entity that will actually sign the loan.
Renewal, expiration, and verification timing
DBA registrations expire on a fixed schedule in Baltimore City. If you are underwriting a multi-year credit facility or a renewal, confirm that the DBA will remain valid for the term of the loan. If renewal is due within 12 months, ask the applicant to renew it upfront and provide proof. Lapsed registrations in a credit file look bad, even if the business is still operating.
When you pull a DBA record, note the filing date and expiration date in your verification file. If you are building a credit profile on the applicant, check back in 30 days before expiration to see if they have filed a renewal. A renewed DBA (with a new filing date and a new five-year term) is a small but real signal that the applicant is managing their compliance. A lapsed one is a signal of neglect.
Bottom line
A Baltimore City DBA search tells you that someone filed a name and when it expires. It does not tell you whether the business is solvent, insured, or liable for debt. Treat a DBA as verification of identity and registration status only. Always link the DBA to the underlying person or entity through a Secretary of State lookup, UCC search, and background check. Credit decisions require more than a DBA filing alone.