Methodology

The catalog answers one question per interface: what does the official frontend or backend block, for whom, by which mechanism and where is it enforced. Snapshot of 2026-10-10. The site shows EVM networks only: 66 of 79 interfaces in the full catalog; Solana, Cosmos and other non-EVM apps stay in monitor/data and in the report. Only observation: nothing is bypassed, nothing is signed, no transactions are sent.

Rating

  • D: More than 20 restrictions
  • C: 6–20 restrictions
  • B: 1–5 restrictions
  • A: No technical restriction found
  • n/a: Nothing could be determined

The rating counts the technical restrictions of the official interface: every country or region where the site, trading or a feature is blocked counts once, and each feature or asset gate, wallet screening (by API or contract), VPN detection and KYC requirement counts once more. Restrictions written only in the Terms of Service are not counted. Fewer restrictions, better rating: A none, B 1–5, C 6–20, D more than 20; ? when nothing could be determined.

Versions: every official interface of a protocol version is its own row (for example Aave V3 at app.aave.com and Aave V4 at pro.aave.com). An older version is marked legacy only when the protocol itself phases it out (a deprecation notice, a move to a v2-/v3- subdomain or an announced wind-down); legacy rows are listed at the bottom. Interfaces that no longer work are kept in the catalog but not shown here.

Status values

  • yes: Confirmed by code, a live check or official documentation
  • no: Looked for and not found
  • reported: Press or user reports, not confirmed in code
  • ToS only: The right is reserved in the Terms of Service, no enforcement found
  • optional: Present in code but switched off by default
  • n/a: Not assessed or not assessable

VPN / Tor detection

  • detect: VPN or Tor users are recognised and get a limited mode or a warning
  • block: VPN or Tor users are refused access

Where screening runs (layer)

  • edge / CDN: CDN or hosting rule: the request is refused by country (HTTP 403/451/302) before the page loads
  • frontend: Code in the browser decides: a built-in address list, or a provider or on-chain oracle queried by the page itself
  • API: A server refuses the address: a compliance endpoint, the indexer, orderbook or quote API
  • smart contract: The smart contract itself rejects the address: an on-chain blacklist, allowlist or memberlist

The layer is where the check actually runs, as found in the code or in a live request. When an interface checks in several places, the deepest one is shown: smart contract, then API, then frontend.

Status for a country

  • blocked: The country is in the list of a confirmed or reported site-level geo-block.
  • close-only: The country is in a close-only tier of a site-level geo-block (Polymarket).
  • feature-limited: The country is in the list of a confirmed feature or asset gate, or the interface limits US persons to some products.
  • regional: Only sub-national regions of the country are listed (Crimea, Donetsk, Luhansk, Kherson, Zaporizhzhia, New York, Ontario, …).
  • ToS only: The country is named in the Terms of Service, or US persons are excluded there, and no enforcement was found.
  • n/a: Geo-blocking was not assessed (closed code), or a block is confirmed but the country list is not published.
  • no restriction found: None of the above; wallet screening and VPN detection may still apply.

All interfaces