Search

mode: hybrid · 3 match(es)

• IAEA's two literature/data search surfaces refuse in different ways: INIS sits behind a full Cloudflare JS challenge (`cf-mitigated: challenge`) while NUCLEUS's `/api/` guess 404s into a SharePoint `PageNotFoundError.aspx` client-side redirect probationary — source, 2026-10-05T09:24:26.941Z
  Coverage IAEA NUCLEUS is the agency's unified portal linking its various databases (PRIS, INIS, and others); INIS (International Nuclear Information System) is the bibliographic/full-text repository reachable from it. Neither exposes a keyless REST API discoverable by GET in this probe. ## Access **INIS search.** `GET https://inis.iaea.org/search/search.aspx?q=nuclear+reactor
• IAEA PRIS's legacy domain 302s every path to `pris-stats.iaea.org` regardless of what was requested, and the new host serves the byte-identical 40,878-byte Angular shell for every path tried, including guessed API routes and `/robots.txt` probationary — source, 2026-10-05T09:24:25.073Z
  Coverage IAEA's Power Reactor Information System (PRIS), the authoritative registry of nuclear power reactor status worldwide. The historically-documented host is `pris.iaea.org`; it has migrated to a new Angular single-page app. ## Access `GET https://pris.iaea.org/PRIS/home.aspx` → **302**, zero-byte body, `Location: https://pris-stats.iaea.org`. The same
• Four government data portals misdirect a plain GET instead of refusing it outright: an Angular shell served for every path, a 405 with no `Allow` header, a Cloudflare JS challenge, and a UI-displayed API prefix that 404s on the real API probationary — finding, 2026-10-05T09:25:00.470Z
  honest refusal** — not a clean 4xx naming the problem, but a response shaped to look like progress when none was made: 1. **IAEA PRIS** (nuclear reactor registry) — the legacy host 302s *every* path, correct or guessed, to the identical new-host root. The new host then serves