Maricopa County DBA search — how to look up a fictitious business name (AZ)
A DBA (doing business as) or assumed name filing in Maricopa County is not a business registration. It’s a public record showing who is trading under a name that differs from their legal entity name. For underwriters, pulling a DBA record answers a specific question: is the applicant using a name that belongs to someone else, and when does that filing expire? But it does not verify the entity itself or show corporate ownership. You need both the DBA record and the underlying business registration to build a credit file.
What a Maricopa County DBA filing actually shows
When a person or business wants to operate under a name different from their registered legal name, they file an assumed name or fictitious business name statement with the Maricopa County Recorder. This filing includes the legal name of the owner (individual or entity), the fictitious name being used, the effective date, and the expiration date. Most Maricopa County assumed name filings are valid for five years and must be renewed.
The filing does not show you the company structure, officers, members, or ownership hierarchy. It shows only that Person A or Company B has claimed the right to use Name C for business. If the applicant lists “John Smith” as the owner and files a DBA for “Smith’s Plumbing,” the record confirms John is trading under that name. It does not confirm John is a real person, solvent, or authorized to sign for credit. It is a public notice, not a business credential.
How to search the Maricopa County Recorder’s office
The Maricopa County Recorder maintains a publicly searchable index of assumed name filings. You can access this through the county’s official records portal using the Recorder’s search tools. Search by the fictitious business name, the owner’s legal name, or the filing number if you have it. The search returns the filing date, expiration date, and legal owner information.
If you are searching a business that claims to operate under a DBA in Phoenix or elsewhere in Maricopa County, start with the DBA search. Write down the legal name of the owner shown in the filing and confirm it matches what the applicant told you. Note the expiration date; an expired DBA means the applicant may no longer have the legal right to use that name. Then cross-reference the legal owner name against Arizona Secretary of State records to find the actual business registration (LLC, corporation, or sole proprietorship) behind it.
Why underwriters must pull both DBA and SOS records
A common underwriting mistake is accepting a DBA filing as proof of business legitimacy. It is not. The DBA only proves someone filed paperwork claiming a name. It says nothing about the entity’s good standing, ownership structure, tax status, or debt obligations.
Here is the real workflow. An applicant applies for equipment financing and lists their business name as “Phoenix Fleet Services.” You search Maricopa County and find a DBA filing for that name, owned by “Phoenix Fleet Services LLC.” Now you must search the Arizona Secretary of State registry for “Phoenix Fleet Services LLC” to confirm it exists, is active, and to see the actual members, managers, or officers. The DBA filing is a pointer; the SOS record is the foundation.
If the DBA owner is a sole proprietor (not an LLC or corporation), the Maricopa County record will show an individual name. In that case, you cannot look up a corporate structure on the SOS because none exists. Instead, verify the person’s legal existence, credit history, and personal guarantees become your primary underwriting lever.
DBA expiration and renewal red flags
Maricopa County assumed name filings expire after five years. If a DBA filing has expired and not been renewed, the legal owner no longer has the public right to use that name. An applicant operating under an expired DBA is technically operating without a current filing and should be flagged in your credit memo.
Check the expiration date on every DBA record you pull. If it is within six months of expiring, ask the applicant whether they plan to renew. A business that lets its DBA lapse suggests either abandonment or operational carelessness. Neither is a credit positive. Conversely, a recently renewed DBA (within the past year) is less of a concern but still not a substitute for verifying the underlying business registration and ownership.
What to do if the DBA owner doesn’t match the applicant
If you search Maricopa County and find that the DBA is registered to someone other than the person or entity who applied for credit, stop. This is a fraud or misrepresentation risk. The applicant may have no legal right to use that name. Require the applicant to explain the discrepancy in writing, and ask for a bill of sale, assignment agreement, or court order showing the transfer of the DBA right. Do not fund based on an applicant’s claim that they “took over” the business unless you have evidence in the county record or a signed transfer agreement.
Bottom line
A Maricopa County DBA search is part of the underwriting toolkit, not the entire toolkit. It confirms who filed a claim to a fictitious name and when that filing expires. But it proves nothing about the applicant’s credit, identity, or authority to bind the underlying entity. Always pair a DBA lookup with a full Arizona Secretary of State search of the legal entity name to verify registration, ownership structure, and good standing. When you pull both records and they align, you have a clearer picture. When they don’t, you have a problem worth investigating before you sign the deal.