war.gov/ufo Portal Architecture: The Pentagon’s Public-Facing UAP Disclosure Platform

The Pentagon’s war.gov/ufo portal is a centralized, browser-accessible disclosure platform that hosts the PURSUE document tranches under a Department of War subdomain, supersedes the older AARO public page on defense.gov, and went live on May 8 2026 with an initial release of roughly 160 files, more than 100 of them carrying redactions [1][2].

Published: 2026-05-18. Last reviewed: 2026-05-18.

What war.gov/ufo Actually Is

The war.gov/ufo portal is the public-facing distribution layer for the Trump administration’s interagency Project on Unidentified and Anomalous Phenomena, Research, Synthesis, and Unified Evaluation — known as PURSUE — and it launched May 8 2026 with a first tranche of about 160 files [1].

Domain choice matters. The address sits on the war.gov hostname, the recently rebranded Department of War web property, not defense.gov, which until that morning had hosted the All-domain Anomaly Resolution Office’s smaller standing collection. The move centralizes UAP releases under a single, top-level subdomain rather than scattering them across AARO’s defense.gov page, the Director of National Intelligence transparency portal, and individual service FOIA reading rooms. Researchers covering the rollout, including Al Jazeera’s May 8 dispatch and DefenseScoop’s May 14 follow-up, treated the launch as the operational debut of a platform rather than a one-time document drop [1][2].

PURSUE itself is not a Senate-mandated body in the AARO sense. It is an executive-branch interagency activity, tasked with reviewing legacy holdings, coordinating equity reviews across the Office of the Director of National Intelligence, the Central Intelligence Agency, the National Reconnaissance Office, and the service branches, and then releasing material to the public on a recurring cadence [1][2]. The portal is the deliverable.

Domain, Hosting, and the Optics of war.gov

Hosting a UAP transparency platform on war.gov is a deliberate optical choice that signals departmental ownership at the cabinet level, places the disclosure pipeline outside AARO’s smaller institutional footprint, and routes search traffic to a domain explicitly tied to the rebranded Department of War rather than to a research office whose acronym most readers cannot expand [1][3].

The previous architecture relied on a single page at aaro.mil and a mirror under defense.gov, both of which catalogued AARO’s case-resolution reports, Historical Record Reports Volume I (2024) and Volume II (2025), and a public reporting form for current or former U.S. government personnel [3]. Neither domain hosted bulk releases. The largest single drop in that era was AARO’s October 2024 case-resolution batch, which the office published as a downloadable PDF index rather than as a browseable file tree.

War.gov/ufo flips that pattern. The landing page presents the PURSUE tranche as a paginated batch listing with file-level metadata — title, originating component, classification marking summary, date of origination, date of release — exposed at the row level rather than buried inside each PDF. That is closer in form to the National Archives’ JFK Assassination Records Collection page than to the older AARO model [4]. The user does not need to open a document to learn what it is.

Document Pipeline: UAP Report to Public Release

A document arrives on the portal only after passing through a four-stage pipeline that begins with a witness or sensor report, routes through AARO’s secure ingestion system, undergoes PURSUE equity review across affected agencies, and terminates in a war.gov/ufo batch upload — a chain that explains why the May 8 release totaled 160 files rather than the tens of thousands rumored in advance of launch [1][2].

Stage one is intake. Active reporting still flows through AARO’s secure portal at aaro.mil, available to current and former U.S. government personnel with relevant observations [3]. Legacy reports, including pre-2017 incident files retrieved from service archives, enter through bilateral records-management requests rather than through the public form.

Stage two is equity review. Each document is circulated to the agencies whose equities it touches — meaning any office whose sources, methods, personnel, or ongoing operations might be exposed by release. ODNI coordinates the review on contested files [2]. This is the stage where redactions are applied. DefenseScoop’s May 14 reporting on the launch noted that researchers parsing the tranche counted more than 100 of the 160 files as carrying visible redaction blocks, ranging from single-name removals to multi-page blackouts [2].

Stage three is conversion. Files arrive at PURSUE in a mix of TIFF scans, native PDFs, and image-only PDFs of paper originals. The portal currently serves PDFs only — no original-format files, no machine-readable text layers for the older scans. Stage four is the batch upload itself, signed off at the PURSUE coordinator level and posted to war.gov/ufo with a release-date stamp [1].

Access Controls, Bulk Download, and What Is Not Documented

War.gov/ufo serves files through standard HTTPS without authentication, account creation, or per-IP rate-limiting that researchers parsing the May 8 release have publicly described, and offers no documented bulk-download endpoint — a notable absence given that the National Archives, the CIA’s CREST system, and the Department of Energy FOIA library all expose either zip-archive downloads or scripted-access endpoints for the same workload [4][5][6].

On the documentary record, the portal documentation as of May 18 2026 describes a browser-first interaction: navigate to the tranche page, click a file row, view or download the individual PDF. No publicly documented API exists. No torrents, no S3-style bucket index, no rsync mirror. Researchers including The Black Vault’s John Greenewald Jr., whose archive of more than three million pages of declassified material runs on a bulk-pull workflow, have publicly noted that the absence of a programmatic interface multiplies the labor required to mirror, hash, and cross-reference the corpus [5].

The release contains roughly 160 files; the popular framing claims a mass declassification event. Stripped of the framing, the load-bearing math is that the initial tranche is smaller than a single AARO Historical Record Report and that more than 60 percent of its files arrive with visible redactions [2]. That is a recurring release platform’s opening salvo, not a single moment of universal disclosure.

What is not documented: whether subsequent tranches will follow a fixed cadence (monthly, quarterly, statutory) or land at PURSUE’s discretion; whether a third-party hash manifest will accompany each batch to detect post-release edits; whether the portal will expose change logs when a file is re-released with different redaction levels; and whether files removed from view will retain a permanent stub at their original URL. As of May 18 2026, none of these capabilities are described in the portal’s published documentation, and reporters covering the rollout have not been able to confirm them [1][2].

How war.gov/ufo Compares to Other Federal Mass-Release Platforms

The closest federal cousins to war.gov/ufo are the National Archives’ JFK Assassination Records Collection, the Central Intelligence Agency’s CIA Records Search Tool (CREST), and the Department of Energy’s OpenNet FOIA library, and each one exposes capabilities — bulk download, OCR’d text layers, programmatic search — that the Pentagon portal does not yet match [4][5][6].

Platform Comparison Table

What war.gov/ufo gets right at launch: a single canonical URL, a top-level subdomain branding that signals departmental ownership, file-level metadata exposed on the index page, and a release-date stamp per batch. These are the same architectural choices NARA made when it rebuilt the JFK Records page in 2017, and they substantially lower the barrier for journalists and researchers approaching the corpus cold [4].

What is underbuilt as of May 18 2026: no full-text OCR layer on scanned originals, no bulk-download endpoint, no published API, no third-party hash manifest, no documented release cadence, and no public change-log for re-released files. CREST, in contrast, was a closed kiosk system for nearly two decades and only opened to the web in 2017; the public-web migration took years and is still incomplete [5]. DOE OpenNet, by contrast, has shipped batch-download since the mid-2000s and exposes per-record metadata in machine-readable form through OSTI.gov [6]. War.gov/ufo is closer to early CREST than to mature OpenNet.

Why the Architecture Matters More Than the First 160 Files

The Pentagon’s commitment to recurring UAP release lives or dies in the portal’s infrastructure choices — release cadence, redaction-markup discipline, hash manifests, full-text accessibility, and programmatic access — not in any single tranche’s contents, because each subsequent batch will compound the indexing problem and any architectural debt incurred at launch becomes an obstacle every researcher will hit for years [1][4].

Two precedents are worth holding in mind. The JFK Records collection took roughly six years from initial public posting to reach a state where journalists could reliably cross-reference documents across batches; the CREST migration, two decades. PURSUE’s portal sits in the position those programs occupied at year one. The architectural decisions ratified at launch — single-document download, no OCR layer, no API — will set the friction floor for every researcher and journalist working the file for the rest of the program’s lifetime.

When the public record is silent, the right move is to say so. As of May 18 2026, war.gov/ufo’s published documentation does not specify a release cadence, a hash-manifest policy, an API roadmap, or a retention policy for re-released files [1][2][3]. Those are the load-bearing questions for the platform’s second year. The first 160 files are a starting condition. The architecture is the program.

Reading List: Primary Documents and Authoritative Sources

• Al Jazeera staff. “Trump administration releases first batch of UFO records on war.gov/ufo portal.” Al Jazeera, May 8 2026 [1].
• DefenseScoop reporting on PURSUE tranche analysis. May 14 2026 [2].
• All-domain Anomaly Resolution Office (AARO). Public site at aaro.mil — case-resolution reports, Historical Record Reports Volume I (2024) and Volume II (2025) [3].
• National Archives and Records Administration. JFK Assassination Records Collection at archives.gov/research/jfk [4].
• Central Intelligence Agency. CIA Records Search Tool (CREST) at cia.gov/readingroom; The Black Vault archive at theblackvault.com [5].
• Department of Energy. OpenNet FOIA library at osti.gov/opennet [6].

For broader background on the program lineage that produced PURSUE, see the Alien and Extraterrestrial Mysteries pillar, the companion piece AATIP, AAWSAP, AARO: How Pentagon UAP investigation programs evolved 2007 to 2026, the May 8 tranche walkthrough PURSUE Release 01: Inside the Pentagon’s first mass UAP declassification, the community-reception analysis Data alone is not disclosure: how the UAP research community read the May 14 PURSUE batch, and the intercept context in NORTHCOM and NORAD UAP intercepts 2004 to 2026.