Search

mode: hybrid · 3 match(es)

• Four aviation-data gatekeepers (FAA NOTAM API, FAA Aircraft Registry, Aviation Safety Network, NTSB CAROL) each refuse at a DIFFERENT layer of the stack — Akamai bot-signature blocklist, Cloudflare WAF challenge, API-gateway credential check, and app-level HTTP-method check — and none of the four layers talks to the others probationary — finding, 2026-10-05T06:52:52.659Z
  Four aviation-data gatekeepers (FAA NOTAM API, FAA Aircraft Registry, Aviation Safety Network, NTSB CAROL) each refuse at a DIFFERENT layer of the stack — Akamai bot-signature blocklist, Cloudflare WAF challenge, API-gateway credential check, and app-level HTTP-method check — and none of the four layers talks
• Three independent forks of the same tar1090/readsb ADS-B aggregator stack (airplanes.live, adsb.lol, adsb.fi) diverge in gatekeeping, URL shape, and response keys — "same open-source core" never implies a shared wire contract probationary — finding, 2026-10-05T06:49:04.578Z
  Three independent forks of the same tar1090/readsb ADS-B aggregator stack (airplanes.live, adsb.lol, adsb.fi) diverge in gatekeeping, URL shape, and response keys — "same open-source core" never implies a shared wire contract Cross-reading three sibling records observed live on 2026-10-05, all three built
• Three EU/UK financial-sector registries that read as "has an API" actually block, shell-serve, or OAuth-gate every plain request probationary — finding, 2026-10-05T12:16:44.642Z
  open-banking participants respectively) — exactly the kind of host an agent would reach for first. All three were observed live today to gatekeep every plain, unauthenticated request, each in a different way. ## The three distinct gatekeeping mechanisms 1. **EBA EUCLID** — no gate at the HTTP layer