FAQ

I'm one person - Node-1. alien-contact.me is a personal, noncommercial, evidence-first UAP/NHI node: an open invitation, a labeled archive, and an optional secure uplink.

This site is not a government authority, not an emergency service, and not a professional investigation organization. It does not run as with others, community's, groups, events, trainings, or "contact sessions" under this (or any other) name(s).

If you only read one thing: preserve originals, separate observation from interpretation, then route via official tools first. (Workflow lives in Handbook).

I built this site to be readable and accessible (including for screen readers), not to look flashy. It uses static HTML and minimalist CSS to ensure high performance and low data overhead.

Scripts are used exclusively for interface functions (search, toggles, copy-to-clipboard) and are not required to access the core information. No trackers, no frameworks, no bloat.

I want this to stay useful whether you lean believer, skeptic, or somewhere in between. The goal is a calm record, not a side.

Labels describe source type (Official / Testimony / Culture), not proof of NHI. This site can be wrong: sources get updated, context changes, and interpretation drifts.

Ground rules: I don't claim proof, there are no ads or trackers, and I don't share private messages without asking first. Privacy details (retention/deletion/warrant canary) are on Transparency.

Official UAP reports are usually written to document scope, process, and what can be stated in public. They rarely read like one big theory, because the goal is traceability: definitions, sources, assumptions, and limitations.

Start with the frame: identify who published the document, the date/version, and the intended audience (policy oversight, aviation safety, scientific recommendations, historical review).

If you want a quick way to skim these reports, try this approach:

1. Executive summary: what is actually being stated, and what is explicitly not stated.
2. Scope: what time period, what domains, and what kinds of cases/data are included.
3. Assumptions: what the analysis assumes about sensors, observers, reporting, and reliability.
4. Definitions: what "UAP" means in this document, and how key terms are used.
5. Data sources: what types of data exist in this pipeline (and what is missing).
6. Limitations: redactions, missing metadata, sensor artifacts, collection bias, and why cases remain unresolved.
7. Findings vs. interpretation: separate what is supported by cited facts from what is commentary or inference.

Keep two columns: (1) what the document directly supports (data, citations, defined terms), (2) what people add on top (interpretation, speculation, narrative).

UAP vs. NHI: "UAP" is an identification status (unresolved after analysis), not a synonym for "non-human". When origin is discussed in official writing, it is usually cautious and bounded by what can be supported.

Quick shortcut: search the PDF for "scope", "assumptions", "definitions", "limitations", "data", "appendix/annex".

Many UAP stories return in cycles: a clip gets reposted, a quote gets reframed, or a case is revived with a new headline. The fastest way to stay accurate is to anchor on primary documents and original files.

A quick way to check:

1. Locate the primary: original PDF/transcript/official release, or the earliest known source file.
2. Check what is actually new: new primary material, or only a new edit/narration/repost.
3. Confirm definitions: terms and labeling can shift across time and institutions.
4. Look for stated limits: missing metadata, sensor constraints, redactions, and out-of-scope boundaries.
5. Test the headline claim: find the exact sentence/table/appendix that allegedly supports it.
6. Watch for circular reporting: repeated references that never reach a primary source.

If you cannot trace a statement to a primary source, label it as "claim" rather than "finding".

Testimony is a real category of evidence, but it is not automatically "proof" of a claim. In practice, testimony can be challenged, rebutted, and weighed for credibility.

What "under oath" changes:
"Under oath" increases legal stakes and signals that the statement is being taken in a formal setting. It can reduce casual lying, but it does not guarantee accuracy or completeness.

What it does not change:
People can be mistaken, misremember details, interpret limited information, or describe events outside direct observation. An oath does not automatically provide corroboration.

How to log testimony professionally (UAP / NHI context):

• Separate observation from interpretation: what the person directly saw/did versus what they believe it means.
• Identify proximity: first-hand involvement, second-hand report, or "I heard / I was told".
• Look for corroboration: primary documents, logs, sensor data, and original media with intact metadata.
• Track limits: what the witness explicitly says they do not know, cannot say, or did not verify.

In this archive, "Testimony" is treated as meaningful context that can guide where to look next, but it is not treated as confirmation by itself.

You don't have to "trust" any single institution or community to handle a UAP claim well. This node treats official statements, testimony, and public media as different source types, and keeps uncertainty explicit when evidence is incomplete.

Practical approach: treat every claim (official or not) as one input, then triangulate across independent sources and check what is directly supported versus what is interpretation.

• Separate observation vs. interpretation: log what you directly saw first; add "what I think it was" second.
• Preserve originals: keep one untouched original file (metadata intact) before any sharing or edits.
• Use independent checks: aircraft/satellite/balloon/planet tools can resolve many cases without anyone's "authority".
• Prefer primary material: original files, original documents, original transcripts — avoid circular reporting.

If you want independent, public-document-oriented research, there are long-running FOIA-based archives (example: The Black Vault's document archive). Example archive.

If you want independent case review/investigation outside government channels, some civilian groups do take submissions (example: The Black Vault's TBV Investigations). Example investigation intake. Always read their scope and rules first.

Headlines, podcasts, threads, and documentaries are often the fastest way to discover a story. They are also usually secondary layers: summary, interpretation, and narrative on top of a smaller set of underlying sources. A quick "source check" keeps you accurate without dismissing anyone's work.

Five quick checks (practical):

• Separate claim vs. source: What is being claimed, and what is the closest available primary source behind it (PDF, transcript, official release, original file)?
• Attention vs. validation: High reach means many people saw it; it does not, by itself, tell you whether the underlying evidence is strong.
• Testimony vs. corroboration: A witness statement can be meaningful; treat it as a data point and look for independent corroboration.
• Check definitions: Make sure "UAP" is used as "unidentified after analysis", not as a synonym for origin.
• Keep uncertainty explicit: If the best label is "unresolved", write it that way instead of forcing a conclusion.

When in doubt, use the archive labels as a navigation aid (source type), and try to trace the story back to the earliest and most direct material available.

A crystal-clear 4K video is no longer automatically the gold standard for evidence. We have to distinguish between true optical resolution (a large sensor or DSLR with a real lens) and synthetic resolution (AI generation or aggressive smartphone processing).

1. Generative fakes:
Photorealistic video can now be generated from prompts. If a striking clip appears with no exact date, no location, no known witness, and no original file, treat it as a claim rather than evidence. Without provenance, high resolution is a dead end.

2. Smartphone processing vs. real optics:
Modern phones do more than record light. Noise reduction, sharpening, interpolation, and heavy digital zoom can reshape a small distant light into something that looks structured or metallic. This is why an ordinary-looking wide clip with context is often more useful than a dramatic close-up.

The practical filter:
A shaky video with an exact time, location, direction, and original file is usually more valuable than a cinematic clip with no backstory. Start with provenance first, image quality second.

A quick check

• Context: Who posted it first, when did it appear, and can you trace it to an original upload or source file?
• Consistency: Do lighting, motion, reflections, shadows, audio, and scene details behave in a physically coherent way?
• Integrity: Is there an original file, metadata, or any chain of custody, or only reposts, edits, and compressed copies?

Technical clue, not proof:
Content Credentials (C2PA) can sometimes help show where a file came from or whether participating tools recorded edits. They are useful when present, but absence does not prove a file is fake.

If you cannot establish source, date, location, or original file integrity, label the material as unverifiable and move on. The goal is not to dismiss unusual footage, but to keep attention on material that can actually be checked.

Sometimes material does not move cleanly through official channels: institutional dead ends, retaliation concerns, or handling restrictions can freeze legitimate disclosure. If you decide to route outside formal hierarchies, basic technical hygiene may reduce exposure, but it cannot make the process safe.

First, verify the recipient: Reporters, lawyers, researchers, and advocacy groups do not operate under the same rules. Verify identity and contact details independently, review how they handle sources, and understand their retention and cooperation policies before sending anything.

Basic handling principles:

• Do not use employer, school, contractor, or government systems for outside disclosure.
• Remove unnecessary metadata and redact names, faces, locations, and identifiers that are not essential to the claim.
• If encryption is used, separate the file from the access details rather than sending everything through one channel.

Operational discipline: Keep your story, timeline, and file history straight. Avoid mixing sensitive communication with day-to-day accounts and devices where possible. What you send may be copied, forwarded, retained, or disclosed later.

Limits: These steps help mainly against ordinary exposure, not against targeted state actors, internal forensics, or legal process. If legal or physical risk is real, speak to a lawyer before acting. For government or contractor personnel, classified material has specific handling rules and unauthorized disclosure can carry serious penalties.

Pareidolia is the tendency to see faces, craft shapes, or symbols in random patterns clouds, lights, compression blocks, or sensor noise.

Treat these impressions as "hypotheses", not data points. If the pattern disappears when zoom, contrast, or angle change, it is likely an artifact of perception or processing.

When you expect to see UAPs, drones, or spacecraft, ambiguous lights are more likely to be interpreted that way.

A helpful habit is to write down exactly what you saw before adding what you think it might be.

Human memory is reconstructive, not a video recording. Details like distance, speed, and shape can drift with re‑telling or exposure to new narratives.

Preserve contemporaneous notes and original files. Later edits, captions, and discussions should be logged separately from the initial observation.

In groups, interpretations can converge quickly one confident statement can shape how others remember and describe the same event.

When logging a "multi‑witness" case, invite each person to write a separate description before comparing notes. Divergences are information, not failure.

In historical UFO and modern UAP studies, the majority of investigated cases end up attributed to identifiable sources aircraft, balloons, atmospheric effects, planets, satellites, or sensor artifacts.

A smaller fraction remains unresolved, often because data quality is low missing metadata, no original files, limited sensor coverage rather than because a non‑human explanation was demonstrated.

"Unresolved" usually means that the available data are insufficient to choose between ordinary explanations, not that an extraordinary cause was confirmed.

Without reproducible measurements and primary data, science cannot assign a specific origin. Keeping "unresolved" separate from "extraordinary" protects both believers and skeptics from over‑claiming.

UAP: Unidentified anomalous phenomenon — unidentified after analysis, not automatically "alien".

NHI: Non-human intelligence — a hypothesis label that avoids jumping to conclusions.

Every entry in the Archive carries one of three labels. Labels describe source type and context, not proof of NHI.

Official: Primary documents, official releases, or institutional records (traceable baseline).

Testimony: Individual claims, whistleblower allegations, and witness statements (unverified by default; see "Testimony" above for how to interpret).

Culture / public discourse: Public-facing coverage and widely circulated material included for context, history, and traceability of the conversation.

AARO

All-domain Anomaly Resolution Office (U.S. DoD). The primary office for UAP investigation.

AAV

Anomalous Aerial Vehicle. Navy-specific term for craft with unconventional flight characteristics (Nimitz-era).

ASRS

Aviation Safety Reporting System (NASA). Confidential incident reporting for civil aviation.

ATC

Air traffic control.

BVR

Beyond Visual Range. Encounters or tracking occurring solely via sensors without the pilot's naked-eye confirmation.

CAP

Controlled Access Program. The intelligence community equivalent to a military SAP (Special Access Program).

CE-5

Pop term for human-initiated contact; treated here as personal practice, not evidence.

Clutter / Airborne Clutter

Official analysis category for weather balloons, birds, airborne trash, or drones causing sensor anomalies.

CPA

Closest Point of Approach. The point of closest proximity between two objects during a near miss (crucial in NMAC reports).

Chain of custody

The chronological documentation of who held the original file and any changes made.

COMINT

Communications intelligence — a SIGINT subtype derived from intercepted communications.

Disclosure

A broad label for policy changes, declassification, or public claims regarding UAP.

DOPSR

Defense Office of Prepublication and Security Review. Clears DoD personnel statements/books for classified info; clearance does not verify truthfulness, only the lack of classified data.

ELINT

Electronic intelligence — a SIGINT subtype derived from non-communication electronic signals.

FAA

Federal Aviation Administration (U.S.).

FISINT

Foreign instrumentation signals intelligence.

Five Observables

Key anomalous traits: 1) Anti-gravity lift, 2) Sudden acceleration, 3) Hypersonic velocities, 4) Low observability, 5) Transmedium travel.

FLIR

Forward-Looking Infrared. Thermal imaging sensors used to track objects via heat signatures.

FOIA

Freedom of Information Act (U.S.).

GEIPAN

French public-facing unit under CNES handling UAP reports.

GEOINT

Geospatial intelligence — imagery and geospatial information.

HUD

Head-Up Display. The transparent display in a cockpit showing flight data and sensor targets.

HUMINT

Human intelligence — intelligence derived from human sources.

ICIG

Intelligence Community Inspector General. Independent oversight body and official reporting channel for intelligence whistleblowers.

IRAD

Independent Research and Development. Internal defense contractor funding (often cited in debates over congressional oversight of unacknowledged material).

ISR

Intelligence, Surveillance, and Reconnaissance. Military operations/systems that routinely collect high-fidelity sensor data on anomalies.

IMINT

Imagery intelligence — intelligence derived from imagery.

Kinematics

The standard term used in official reports to describe the (anomalous) flight behavior, acceleration, and physical movement of tracked objects.

MASINT

Measurement and signatures intelligence.

Metadata

Embedded file information (time, device, settings) essential for validation.

METI

Messaging to extraterrestrial intelligence (deliberate signaling).

NARA

National Archives and Records Administration (U.S.).

NDAA

National Defense Authorization Act (U.S.).

Near Miss / NMAC

Near Mid-Air Collision. A safety hazard where craft pass within a dangerous distance (usually <500ft).

NOTAM

Notice to Air Missions. Official alerts to pilots regarding hazards or changes in airspace.

ODNI

Office of the Director of National Intelligence (U.S.).

OSINT

Open-source intelligence — intelligence derived from public information.

Primary document

The closest available original source (PDF, transcript, official release).

Reupload

A copied file; often lacks metadata and contains compression artifacts.

SA

Situational Awareness. A pilot's mental model of their environment and potential hazards.

SAP / USAP

Special Access Program / Unacknowledged SAP. Highly classified programs with restricted oversight.

SCIF

Sensitive Compartmented Information Facility. A secure room for briefing classified data.

Sensor Fusion

Combining data from multiple sources (radar, IR, visual) for a consistent track.

SETI

Search for Extraterrestrial Intelligence (passive listening).

SIGINT

Signals intelligence (umbrella for COMINT/ELINT/FISINT).

Signature Management

The ability of a craft to mask or alter its visibility to sensors.

TCAS

Traffic Collision Avoidance System. Automated aircraft warning system; whether it triggers or not is a key data point in UAP encounters.

TFR

Temporary Flight Restriction. Short-term airspace closure, sometimes enacted during intercepts or when unidentified objects are detected.

Title 10 / 50

U.S. legal authorities for military (Title 10) vs. intelligence (Title 50) operations.

Transmedium

Objects moving across space, atmosphere, and water without structural failure.

UAPTF

Unidentified Aerial Phenomena Task Force (predecessor to AARO).

UAS

Unmanned Aircraft System. The official aviation and government term for drones.

UFO

Older term used for the "unidentified" concept. Unlike UAP, it implies a physical "object" rather than including broader "phenomena" (e.g., sensor glitches, weather anomalies).

USO

Unidentified Submerged Object. Anomalous objects tracked or seen underwater.

USS

United States Ship (e.g., USS Nimitz).