NAIC Map of 56 Insurance Jurisdictions

Datadory delivers NAIC map of 56 insurance jurisdictions data covering every US insurance regulator - the 50 states, the District of Columbia and five territories - with each jurisdiction's department contact information, its agent and broker locator route, and its complaint-filing path, normalized to one row per jurisdiction and ready to join onto any state-keyed panel.

What is the NAIC Map of 56 Insurance Jurisdictions?

Fifty-six regulators, one roster. The NAIC Map of 56 Insurance Jurisdictions is the National Association of Insurance Commissioners' directory of every US insurance jurisdiction: the 50 states, the District of Columbia and five territories - American Samoa, Guam, the Northern Mariana Islands, Puerto Rico and the US Virgin Islands. Each jurisdiction carries three working routes: the department's contact information, the state's own agent/broker locator, and the path for filing a complaint with that department.

The name oversells the geometry and undersells the usefulness. The header graphic looks like a map, but no region is clickable; selection runs through three dropdown-and-go interfaces - a state-department contact lookup with filter options, a find-an-insurance-agent selector, and a file-a-complaint router. Department detail never renders inline; it surfaces behind those filters or inside one consolidated directory of all state info. The page also bundles InsurTech/innovation contacts and MEWA contacts, a pairing no other NAIC navigation property offers.

Within Datadory's catalog of 1,744 datasets across 159 viable industries, this is one of 10 cataloged insurance brokers datasets and scores 8/10 on the quality rubric - the front door of the US regulatory stack, where every deeper licensing dataset eventually points.

Get a sample of this dataset

What do sample rows look like?

Illustrative rows in the delivered shape - one jurisdiction per row:

jurisdiction           : one of the 56 NAIC jurisdictions
department_contact_info: contact details for that jurisdiction's insurance department
agent_broker_locator   : route to the state's agent/producer search tool
complaint_filing_route : path into that department's complaint process

jurisdiction           : second jurisdiction
department_contact_info: resolved through the state-department lookup
agent_broker_locator   : surfaced via the find-an-agent selector
complaint_filing_route : surfaced via the file-a-complaint router

Read the anatomy rather than the placeholders. One row names a regulator; the next three columns say how to reach it, how to check a producer against it, and how to complain to it. Because all 56 rows share that shape, a fifty-state outreach plan or a territory-by-territory verification pass is a filter, not fifty-six separate lookup sessions. Live values for the jurisdictions you nominate arrive with your sample.

Which fields does the dataset include?

Four documented fields, one row per jurisdiction, all four verified against the live directory during research: the jurisdiction itself, the department's contact information, the agent/broker locator, and the complaint filing route.

Additional fields on request: the directory publishes beyond the core four. InsurTech/innovation contacts and MEWA contacts sit on the same page; the consolidated all-state directory renders every department's detail in one document; and a per-jurisdiction completeness flag records where the find-an-agent interface exposes a territory's locator. Tell us the workflow and the column set is confirmed against delivery.

Where does the coverage reach?

  • Geography - the United States in full regulatory extent: all 56 NAIC jurisdictions, the 50 states, the District of Columbia and the five territories. This is the only cataloged dataset that enumerates the territory regulators alongside the states.
  • Time - a live directory rather than a dated series. Each cut reflects the current state of department detail; schedule repeated cuts over time and the diffs become your change log for reorganizations and renamed departments.
  • Granularity - one row per jurisdiction. A complete cut holds exactly 56 rows, which makes it small enough to read in one screen and stable enough to use as a dimension table.

How is the data delivered?

API, files, or your warehouse. Daily, weekly, or hourly.

Name the jurisdictions when you request the sample - all 56, or a slice cut to your footprint. The sample ships first either way, and the ongoing feed lands on whatever cadence your work needs.

Who uses this data, and for what?

A jurisdiction roster earns its keep as the spine other work hangs on:

  • Lead enrichment and outbound prospecting - route each state-level broker lead to its own regulator's locator before first contact, so the list you call matches the licenses that actually exist; see the lead enrichment use case.
  • Citation-grade research - attribute every state-level insurance claim to the correct department, with the association of state regulators as the named source; see the citation-grade research use case.
  • Compliance routing - point licensing questions, appointment filings and consumer complaints at the right department the first time, across all 56 jurisdictions including the territories most lists forget.
  • Market framing - frame US coverage plans around the actual regulatory geography rather than a 50-state shortcut that silently drops DC and five territories.

Which personas get the most value?

Sales and growth teams (relevance 2) get the state-by-state locator spine for broker prospecting without buying a full registry report first; see sales growth teams use cases. Market researchers and consultants (relevance 2) get the citable regulatory geography for US coverage plans; see market researchers use cases. Journalists, academics and students (relevance 2) get department contacts and complaint routes across all 56 jurisdictions from one verifiable source; see journalists academics use cases. Data scientists (relevance 1) use the roster to seed crawls of state producer-locator endpoints - the map is a gateway, not a dataset of records; see data scientists use cases. Competitive-intel teams (relevance 1) identify which department to query when tracking a competitor's licensing posture or complaint record. Developers (relevance 1) get fair warning: 56 state systems sit behind these routes, each with its own interface.

How does it compare to alternatives in its slice?

Within the 10-dataset insurance brokers slice, this roster competes on reach, not depth. The NIPR-operated Producer Database holds realtime licensing records for millions of producers across the jurisdictions, but its reports and batch pulls are subscriber products - the roster tells you which door to knock on, the PDB tells you what is behind it. NIPR Licensing Lookup answers single-producer "who is licensed" queries one NPN at a time, while this dataset answers "who regulates whom" for all 56 jurisdictions at once.

Abroad, the FCA Financial Services Register covers UK intermediaries and the IRDAI list covers India's licensed brokers in far greater firm-level detail than any US directory attempts; the head-to-head against India's register is settled on our IRDAI vs NAIC jurisdictions comparison. The sibling NAIC Industry Hub explains filing and compliance tooling but stops at pointing to NIPR - only the jurisdictions map enumerates all 56 regulators.

What should I know before requesting a sample?

Three things worth settling upfront.

First, depth versus breadth: this is a directory, not a records database. Four fields per jurisdiction, 56 rows per cut - pair it with a licensing dataset when per-producer history is the analysis.

Second, the territory caveat: the find-an-agent interface appears to omit some territories, with American Samoa, Guam and the Northern Mariana Islands flagged during research. Department contacts and complaint routes still cover all 56 jurisdictions, and the per-jurisdiction completeness flag rides along as an additional field on request so the gap is visible in your extract rather than discovered mid-project.

Third, freshness expectations: the underlying directory changes as departments reorganize, so treat any single cut as point-in-time and put repeated cuts on a schedule if reorganizations matter to you.

Field dictionary

Every field below is documented against real records. The full dictionary ships with the sample.

Field dictionary — NAIC Map of 56 Insurance Jurisdictions, one row per jurisdiction
FieldTypeDefinitionExample
jurisdictionstringOne of the 56 NAIC insurance jurisdictions: 50 states, DC, American Samoa, Guam, the Northern Mariana Islands, Puerto Rico, the US Virgin Islands.Puerto Rico
department_contact_infotextContact details for the jurisdiction's insurance department - the regulator that licenses and polices producers there.department name with phone and email
agent_broker_locatorstringRoute to the jurisdiction's own agent/producer search tool, where a specific broker's license standing can be confirmed.state producer locator route
complaint_filing_routestringPath for filing an insurance complaint against a producer or insurer with that jurisdiction's department.state complaint route
Additional fieldsFolded under 'additional fields on request': InsurTech/innovation contacts, MEWA contacts, the consolidated all-state directory contents, and a per-jurisdiction completeness flag for the find-an-agent interface.on request

Questions buyers ask

Which jurisdictions does the NAIC map of 56 insurance jurisdictions cover?

All 56 NAIC insurance jurisdictions: the 50 US states, the District of Columbia and five territories - American Samoa, Guam, the Northern Mariana Islands, Puerto Rico and the US Virgin Islands. Each carries one row, so a complete cut holds exactly 56 rows with the same four fields throughout.

What fields come back for each jurisdiction?

Four documented fields per row: the jurisdiction itself, the insurance department's contact information, the route to that state's agent/broker locator, and the path for filing a complaint with the department. InsurTech/innovation contacts, MEWA contacts and the consolidated all-state directory ride as additional fields on request.

Why is it called a map if nothing on it is clickable?

The header graphic resembles a map, but no region is selectable. Navigation runs through three dropdown-and-go interfaces - a state-department contact lookup, a find-an-insurance-agent selector and a file-a-complaint router - and department detail surfaces behind those filters or in one consolidated directory document rather than rendering inline.

Does every territory include an agent/broker locator?

Not everywhere. Research flagged that the find-an-agent interface appears to omit some territories, naming American Samoa, Guam and the Northern Mariana Islands. Department contacts and complaint routes still cover all 56 jurisdictions, and a per-jurisdiction completeness flag can be added to your extract so the gap is explicit in the data.

How is this dataset different from NIPR producer licensing data?

Different layers of the same stack. This roster answers who regulates insurance in each of the 56 jurisdictions and how to reach them; NIPR's Producer Database answers which individual producers hold what licenses, as a subscriber product. Teams typically start with the roster for routing and coverage planning, then pull licensing records for the specific producers they care about.

Can jurisdiction rows be joined onto my own state-level panel?

Yes - the jurisdiction name is the join key on every row, held constant across all 56 entries, so the roster attaches cleanly to any state-keyed panel such as Census brokerage counts, premium totals or complaint volumes. Territory rows use their standard names, which keeps DC and the five territories from falling out of a naive state join.

What does a Datadory sample include?

The jurisdictions you nominate, delivered in exactly the four-field structure documented above, with any requested additional fields - InsurTech and MEWA contacts, the consolidated directory, the completeness flag - confirmed against the extract before anything ships. Samples exist to prove fit, so joins built during evaluation survive unchanged into production.

Notes on this record

  • A directory, not a records database Four fields per jurisdiction, 56 rows per cut - the roster that routes every deeper question. Pair it with a licensing dataset when per-producer history is the analysis rather than the routing.
  • Three interfaces behind one page Department contacts, agent locators and complaint routes resolve through separate dropdown-and-go interfaces, with the full department detail consolidated into a single all-state directory document.
  • The territory caveat, stated plainly The find-an-agent interface appears to omit some territories - American Samoa, Guam and the Northern Mariana Islands were flagged during research. Contacts and complaint routes still reach all 56 jurisdictions, and the completeness flag makes the gap explicit on request.
  • Named source, verified fields Published by the National Association of Insurance Commissioners, the association of US state insurance regulators. All four fields were checked against the live directory during research; quality scored 8/10 on the catalog rubric.

See the rows before you pay anything.

Name this dataset and we send real records from it — scoped to the fields you asked for.

See pricing