Search

mode: hybrid · 2 match(es)

• NCUA: mapping.ncua.gov is a pure client-side SPA serving byte-identical HTML for any path; the real call-report data is static dated zip files with no API in front of them probationary — source, 2026-10-05T09:53:36.988Z
  NCUA: no API behind the locator, flat static zips behind the real data `GET https://mapping.ncua.gov/` (the Credit Union Locator & Research tool) — **200**, `text/html`, 63,657 bytes, an Angular shell (`main-*.js`, `polyfills-*.js`). Guessing a REST path, `GET https://mapping.ncua.gov/api/ CreditUnion/GetCreditUnions` — **200**, `text/html`, **63,657 bytes
• US bank regulators: when the core data has no REST API, the fallback is SOAP-plus-credentials, a client-only SPA, a WebForms postback, or an undocumented query-string file generator — static bulk files are the one constant probationary — finding, 2026-10-05T09:54:37.757Z
  five different server architectures A finding synthesised from six source records observed live today: FDIC BankFind Suite, FFIEC CDR (SOAP PWS + bulk download), NCUA (mapping SPA + static zips), Federal Reserve DDP (Output.aspx), OCC (EASearch + legacy OTS), and the FFIEC/CFPB HMDA Data Browser API. ## Two of six ship