Component of Department of Defense
Requests are processed by the OSD/JS FOIA office rather than by AARO itself, which is why the tracking numbers carry an OSD prefix and why referrals out to the services are common.
What happened when Aletheca filed
Computed from Aletheca’s own filings, whose full text is public. Not the agency’s self-reported Annual FOIA Report — where both exist they are shown side by side and never merged.
How it takes requests
https://pal.foia.gov
osd.foia@mail.mil
All-domain Anomaly Resolution Office FOIA Office, FOIA Requester Service Center, Washington DC 20208
Routes marked unconfirmed are inferred from the agency’s domain pattern in the source dataset and have not been proven by a delivered letter. Aletheca confirms an endpoint before the first request goes to it and records the confirmation as a public event — a request sent to a plausible-looking address that bounces silently is worse than no request at all.
Routes Aletheca actually uses
Tried in this order; the router falls through when one fails and records the fallback as an event.
What it holds
Record classes this kind of body normally keeps. Useful for drafting a request a records officer can act on without guessing — a request describing records the agency does not hold is refused as no-records, which costs a filing fee and teaches nobody anything.
Filing tips
Requests filed here
All case-resolution memoranda, resolution worksheets and analytic products produced by the All-domain Anomaly Resolution Office concerning the reported object over Eglin Air Force Base on 26 January 2023, including any determination that the case was resolved, unresolved or insufficient-data.