Registered Agent Visibility by State — Explainer
Matrix explainer. Exposure verbs mapped: visible + searchable. Source matrix: registered-agent-visibility-by-state. 51 jurisdictions (50 states + DC); typed unknowns preserved per cell. Not legal advice.
Short answer
Every state requires an LLC to name a registered agent at formation, and everywhere the matrix could observe the live portal — 46 of 51 jurisdictions — the registered agent's name and address are publicly displayed. This is the canonical formation-level disclosure surface, and the most universally addressable one. A commercial registered-agent service substitutes the RA's address for the founder's home address on the public record. That's one layer of privacy, not four.
Searchability is where states diverge: 14 jurisdictions confirm public search by agent name, 10 confirm they offer none, and only Florida confirms search by agent address.
What this matrix tracks
For each of the 51 jurisdictions, seven cells:
- Registered agent name in snapshot — does the cached entity record name the RA? (22 yes; NY partial at 20.2% of rows; 28 jurisdictions have no snapshot data)
- Registered agent address in snapshot — same counts as the name cell (NY's address cell is 20.4% populated).
- Registered agent name visible on portal — does the live state SoS portal display the RA name? (46 yes / 5 typed unknowns)
- Registered agent address visible on portal — (46 yes / 5 typed unknowns)
- Searchable by agent name — can the public reverse-search the registry by the agent's name? (14 yes / 10 no / 27 typed unknowns)
- Searchable by agent address — (1 yes — FL / 1 partial — AR, city-level / 12 no / 37 typed unknowns)
- Filed documents visible — are downstream filings (Articles, Statements, amendments) accessible from the entity page? (43 yes / 8 typed unknowns)
Why this exposure surface matters
The registered agent is the canonical public point of contact for an LLC. If the founder names themselves as the RA at their home address, that home address goes into the state business registry — searchable, indexable, and available for aggregation by data brokers. Founders who route their RA through a commercial RA service substitute the service's commercial address, and the founder's home address never enters the public record at this layer.
The less-obvious risk is reverse search. Where a registry can be searched by the agent's name — 14 confirmed jurisdictions (FL, AL, AK, AR, GA, IA, KY, LA, MO, MT, NV, NC, WA, WV) — a founder who serves as their own agent can be enumerated by name: every entity they represent, in one query. Address-keyed search is rarer; Florida's Sunbiz is the only portal where the matrix confirms it, via street-address and zip-code search options. This is one of the reasons commercial RA services use very high-volume addresses — anonymity by crowd.
Key findings (51 jurisdictions)
- RA name and address exposure is universal where observable. All 46 jurisdictions with an observable portal display both; the remaining 5 (CO, WY, MS, MT, VT) are typed unknowns — observed portal inaccessibility, not observed privacy.
- 14 jurisdictions confirm search by agent name — FL, AL, AK, AR, GA, IA, KY, LA, MO, MT, NV, NC, WA, WV. Several run dedicated agent-search interfaces (Missouri's Registered Agent Search, Iowa's Business Entity Agent search, Montana's enumerable Commercial Agent List).
- 10 jurisdictions confirm NO agent-name search — CO, DE, CA, TX, IL, NH, NJ, ND, OH, OK. These portals offer no public agent-name search key (nine of the ten still display the agent on the entity record; CO's display cells are themselves typed unknowns).
- Only Florida confirms full address-keyed search, with Arkansas partial at city granularity. 12 jurisdictions confirm no; the remaining 37 cells are typed unknowns. For the full enumeration-by-address question, including paid tiers and aggregator paths, see the reverse-lookup explainer.
- Filed documents are reachable from the entity page in 43 of 51 jurisdictions — meaning the RA disclosure usually travels with the full filing history, not just the current record.
What this matrix does NOT prove
- Does not prove what a commercial RA service charges, how it handles process service, or whether any specific RA service maintains the address it lists.
- Does not prove the operational reliability of the state's portal at any specific moment.
- Does not prove the data broker exposure for any specific RA address.
- Does not prove anything about whether the founder's home address has been previously associated with an LLC at any state's portal (historical exposure is out of scope).
- Does not measure what third-party aggregators (OpenCorporates, BizFile, etc.) re-publish from these portals — a confirmed "no" on portal search does not mean an agent cannot be enumerated through aggregators.
Methodology
Per-jurisdiction observation captures the portal state at a specific date, recorded per cell with a last_checked date. Where a portal could not be observed, the cell carries a typed unknown naming the failure mode — unknown_operator_declared_inaccessible (WY), unknown_portal_inaccessible (MS), unknown_portal_blocked (MT), unknown_source_unreachable (VT), and unknown_portal_not_observable_via_webfetch for portals that return an app shell to direct fetch. These are NOT "we don't know" cells; they are "we observed the inaccessibility itself." The underlying RA data in those states is still legally public; the matrix just cannot observe it via the production-runtime path.
See full methodology at /about/methodology/.
Sources and refresh cadence
Primary-source citations per row — the state SoS portal or search interface actually observed — live in the matrix's sources.json companion, one official URL and last_checked date per jurisdiction. The full source taxonomy lives at /about/source-registry/.
Refresh cadence: 180 days. Trigger events: state SoS portal redesign, statutory change to RA disclosure, new commercial RA aggregator that changes the reverse-lookup landscape.
Not legal advice
This matrix is research-grade structured-fact infrastructure. RA selection has legal, tax, and operational implications that depend on the specific entity's circumstances. Consult counsel for compliance-specific questions.
See also: Registered Agent Visibility by State (matrix) · RA Address Reverse Lookup by State (explainer) · What Is a Registered Agent?
Frequently asked questions
Why track snapshot vs live portal separately?
Caches and live secretary-of-state sites diverge — both columns are required per /about/methodology/. The snapshot layer currently confirms 22 of 51 jurisdictions; the live-portal layer confirms 46 of 51.
Does a commercial RA prevent home-address exposure?
On the formation filing, usually yes for the RA field — member and foreign-qualification layers are separate questions.
Can the public search a registry by the agent's address?
Florida is the only jurisdiction where the matrix confirms full address-based search (Sunbiz street-address and zip-code options); Arkansas confirms partial city-level agent search. 12 jurisdictions are confirmed no; the remaining 37 are typed unknowns. See /business-formation/registered-agent-address-reverse-lookup-by-state-explainer/ for the dedicated reverse-lookup layer.
Where is the structured matrix?
/business-formation/registered-agent-visibility-by-state/ — 51 jurisdictions, seven cells per row, per-row primary-source citations in sources.json.
Are filed documents included?
This matrix tracks whether filings are reachable from the entity page (43 of 51 yes); /business-formation/filed-document-access-by-state/ tracks document retrieval in depth.
Go deeper with source-backed research
Explore methodology, datasets, and related matrices cited on this page.