TL;DR: A fake DBA certificate is a fictitious business name filing, either edited after the county clerk recorded it or generated to look like that recording, offered as if it proved the company exists. The FBI's 2025 Internet Crime Report recorded 1,008,597 complaints. That is a broader fraud figure, not a rate for DBA filings. Treating the certificate as good standing fails as a visual check, because a county filing was never a formation document and carries no secretary of state seal to inspect.
What a Fake DBA Certificate Actually Is
A DBA certificate, in California a fictitious business name statement, is a county filing that makes public who is using a name other than their own. Business and Professions Code section 17900 says the filing exists so people dealing with that name can learn who the registrants are. The statement does not form an entity, and it does not register a trademark.
The county clerk of the county where the principal place of business sits files it. The California Secretary of State does not. A seal from the Secretary of State on a fictitious business name statement is the wrong issuer. Existence and standing live on a different document, covered in how to spot a fake certificate of good standing.
Section 17913 requires the fictitious name, the address, the registrants, how the business is conducted, and the date use began. The registrant declares that information true. Declaring a material matter knowing it is false is a misdemeanor, with a fine of up to $1,000. The penalty describes the real filing. It does not authenticate a PDF. Section 17920 sets the life: five years after filing, 40 days after a change in the 17913 facts except as section 17923 provides, or when the registrant files a statement of abandonment. A statement past one of those dates is not a current record of who is using the name.
The upload arrives in two production classes. Edited-after-creation starts from a real county-filed statement, then changes the registrant, the address, the file number, or the filing date. Generated-from-scratch builds a page that looks like the county's form, file stamp included, with no underlying recording. FinCEN's September 9, 2024 analysis of check fraud tied to mail theft found that 44 percent of the checks were altered and then deposited, and 26 percent were used as templates for counterfeits. Those percentages describe checks. They illustrate the two classes, a genuine instrument changed after it existed and a new instrument built from a template, and they are not a rate for DBA certificates.
Tells That Still Work, and the Ones That Do Not
The county index still works. Look up the file number in the fictitious business name index of the county named on the certificate. The registrant, the fictitious name, the address, and the filing date should match the index. Expiration still works. Count five years from the filing date, and ask whether a change in the facts of section 17913 would have ended the statement 40 days later. A file number the index does not contain, or a registrant the index lists differently, is the case.
Good standing fails as a reading of this document. A current fictitious business name statement says who registered the name in that county. It does not say the registrant is a formed entity, that the entity is in good standing, or that the name is a trademark. A Secretary of State seal on an FBN fails for the same reason. The clerk of the county files this statement. A state seal is not what a genuine California fictitious business name statement carries.
When the registrant is an LLC or a corporation, section 17913 points the legal name back to the articles on file with the Secretary of State, including the state of organization. That name should match the formation record in the business file. The ownership behind an LLC registrant sits in the operating agreement, a different document, covered in how to spot a fake operating agreement. A DBA that names a real LLC does not prove the member who uploaded it controls that LLC.
How Detection Actually Works
The file's story is that a named county clerk recorded this fictitious name for these registrants on this date, under this file number, and that the statement is still inside its statutory life. Detection asks whether the bytes support that story.
Production method asks how the page was made. A county download or a certified copy, a later edit of that PDF, a phone photo of a clerk's printout, and a generative pipeline do not share a path. Edited-after-creation leaves a real recording under a later save, often with the registrant line or the file number as the change. Generated-from-scratch has no county file underneath, even when a stamp image sits in the corner. The case note should name the class.
Timestamp trail asks whether creation and modification fit the filing date. A statement filed two years ago and scanned yesterday can be an ordinary copy of a live recording. A statement whose filing date is three weeks ago, and whose file was created months earlier with a different registrant, reads as an edit. Re-scans and county portal reprints add noise, so the trail is evidence beside the index, not a substitute for it.
Issuer matching asks whether the county named on the page is the county that would have filed it, and whether that county's index contains the file number. The Secretary of State is the wrong issuer. The index should show the same fictitious name, the same registrant, and a filing date that supports the date on the certificate. Expiration is part of the match: five years from filing, 40 days after a change in the 17913 facts, or an abandonment, whichever came first.
Consistency checks the page against itself and against the application. The conduct line, individual, corporation, LLC, or partnership, should match the registrant block. The address should be the one the application uses, or a change the applicant can explain with a newer statement. A generated form agrees with itself by construction. Model artifacts are layout, stamp, and wording that do not come from that county's actual statement. Recycled patterns are the same stamp, the same file number, or the same certificate image on an unrelated business name. One reviewer with one file will not see the second use. How banks miss the same classes of edit on other documents is covered in document fraud in banking.
What to Do with a Suspect File
Hold the upload and search the file number in the fictitious business name index of the county printed on the certificate. No such number, or a different registrant, name, or filing date, means the PDF and the register disagree. If the index matches, check the life of the statement: five years from filing, 40 days after a change in the 17913 facts, or abandonment. An expired statement is not current proof of who is using the name. An individual registrant should be the applicant. An LLC or corporate registrant should match the articles, and the person applying still has to show authority for that entity.
A matched, unexpired statement still does not prove the business exists as an operating company, and it does not prove a trademark. A name with no activity behind it is a different problem, covered in shell company red flags. When the index matches and the file still looks rewritten, ask whether the registrant line changed after the county page was produced. For a scored read of that history, check the file. The x-ray is production method, timestamps, issuer match, consistency, model artifacts, and recycled patterns. The county index remains the register.
Where Sphinx Fits
Watchdoc scores the certificate and shows the x-ray a reviewer can point to. Sphinx's published product figures include clean files clearing in under 28 seconds, at $0.45 per document. The Watchdoc playground is free for the first file. Run the file number and the registrant line against the file's history, and against the county index, before the DBA is treated as the business.
Frequently Asked Questions
How can you tell if a DBA certificate is fake?
Look up the file number in the county clerk's fictitious business name index and compare the registrant, the fictitious name, and the filing date. Then check whether the statement has expired: five years after filing, 40 days after a change in the facts, or on abandonment. Visual defects still catch crude forgeries. Competent fakes fail when a real county page was edited after filing, or when the page was generated and the index has no matching entry.
Does a DBA filing prove the company exists?
No. In California, a fictitious business name statement makes the registrants public. It does not form a corporation or an LLC, and it does not register a trademark. Formation and good standing are secretary of state questions. The DBA answers who registered that name in that county, and only while the statement is unexpired.
How long does a California fictitious business name statement last?
Under Business and Professions Code section 17920, the statement generally expires five years after the county clerk files it. It expires 40 days after a change in the facts set out in section 17913, aside from the exception in section 17923, and it expires when the registrant files a statement of abandonment. A scan of an expired statement can still look official.
Is a Secretary of State seal expected on a DBA certificate?
No. The county clerk files the fictitious business name statement in the county of the principal place of business. A genuine California FBN does not carry a Secretary of State seal, and a seal from that office does not make the filing a certificate of good standing. Confirm the file number in the county index instead.
.png)
