Where to Find OSINT Tools for Aviation and Maritime Tracking in Legendary OSINT

Aviation and maritime OSINT tools in the Legendary_OSINT repository are organized in dedicated markdown files under the docs/ directory, specifically docs/aviation.md for aircraft tracking and docs/maritime.md for vessel intelligence.

The Legendary_OSINT repository by K2SOsint structures its open-source intelligence resources as subject-specific markdown references. Rather than scattering links throughout the codebase, the project centralizes aviation and maritime tracking tools in dedicated documentation files that are indexed from the main README. This architecture allows investigators to quickly locate live trackers, historical archives, and specialized registries without searching through unrelated code.

Aviation OSINT Tools Location

Aviation tracking resources are compiled in docs/aviation.md. According to the source code analysis of the repository, this file serves as the centralized index for aerial surveillance and aircraft identification tools.

Contents of docs/aviation.md

The aviation documentation includes:

• Live tracking platforms such as ADS-B Exchange and Flightradar24 for real-time global aircraft positioning
• Historical flight data archives enabling retroactive route analysis and pattern-of-life studies
• Aircraft registry databases containing tail numbers, ownership records, and manufacturer details
• Military and civilian aviation tools covering both commercial airliners and specialized government or private aircraft operations

Each entry in docs/aviation.md contains direct hyperlinks to the external service, allowing immediate access to the tracking interface.

Maritime OSINT Tools Location

Maritime intelligence resources are maintained in docs/maritime.md, which functions as the definitive reference for vessel tracking and maritime domain awareness.

Contents of docs/maritime.md

This file aggregates:

• Global AIS trackers including MarineTraffic and VesselFinder for real-time vessel positioning and voyage history
• Regional AIS portals offering localized coverage of specific coastlines, ports, or territorial waters
• Vessel ownership registries linking ships to their registered owners, operators, and flag states
• Cargo container tracing services for supply chain monitoring and logistics investigations
• Naval defense intelligence sites covering military maritime assets and defense-related vessel movements

The docs/maritime.md file is referenced from the repository's main README.md, ensuring it appears in the primary index alongside other OSINT disciplines.

Programmatically Extracting OSINT Tool URLs

You can programmatically harvest the tool URLs from these markdown files for integration into automated workflows or custom toolkits. The following Python script parses the markdown link syntax to extract all external URLs from either the aviation or maritime documentation:

import pathlib
import re

def load_links(section: str) -> list[str]:
    """Return a list of URLs from a given markdown section."""
    doc_path = pathlib.Path("docs", f"{section}.md")
    urls = []
    for line in doc_path.read_text(encoding="utf-8").splitlines():
        # Look for markdown links or bare URLs

        match = re.search(r'\((https?://[^)]+)\)', line)
        if match:
            urls.append(match.group(1))
    return urls

# Example: retrieve all aviation tool URLs

aviation_links = load_links("aviation")
print("Aviation OSINT tools:")
for u in aviation_links:
    print("-", u)

# Example: retrieve all maritime tool URLs

maritime_links = load_links("maritime")
print("\nMaritime OSINT tools:")
for u in maritime_links:
    print("-", u)

For command-line extraction without Python, use grep to pull raw URLs directly from the source files:

grep -Eo 'https?://[^ )]+' docs/aviation.md   # aviation URLs

grep -Eo 'https?://[^ )]+' docs/maritime.md   # maritime URLs

Both methods assume you have cloned the K2SOsint/Legendary_OSINT repository locally and are executing commands from the repository root.

Summary

• Aviation tools are located in docs/aviation.md, containing live trackers like ADS-B Exchange and Flightradar24 alongside historical databases and aircraft registries.
• Maritime tools are located in docs/maritime.md, featuring AIS trackers such as MarineTraffic and VesselFinder, plus cargo tracing and naval intelligence resources.
• Both files are indexed in the main README.md and contain direct hyperlinks to external OSINT services.
• You can extract URLs programmatically using Python regex parsing or standard grep commands to build automated tool inventories.

Frequently Asked Questions

Where exactly are aviation tracking tools documented in Legendary_OSINT?

Aviation tracking tools are documented in docs/aviation.md at the repository root. This file contains curated links to live flight trackers, historical flight data archives, and aircraft registry databases for both civilian and military aviation investigations.

What types of maritime tracking resources are available in the repository?

The docs/maritime.md file contains vessel-ownership registries, global AIS trackers like MarineTraffic and VesselFinder, specialized regional AIS portals, cargo-container tracing services, and naval-defense intelligence sites for comprehensive maritime domain awareness.

Can I extract the tool URLs automatically from the repository files?

Yes. Since the resources are stored in standard markdown files, you can extract URLs using the Python re module to parse markdown link syntax, or use the command-line tool grep with the pattern https?://[^ )]+ to isolate hyperlinks from docs/aviation.md or docs/maritime.md.

How is the OSINT documentation organized in Legendary_OSINT?

The repository organizes resources by subject area under the docs/ directory, with each markdown file (such as aviation.md and maritime.md) dedicated to a specific intelligence discipline. The main README.md serves as the master index, linking to these subject-specific pages for navigational clarity.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}