Making 2IA the Definitive Directory of OSINT and Hacktivist Organizations

Full report

On this page

Executive summary

2IA already has the editorial foundation that a high-trust directory needs. The current public site frames itself as a civil-liberties and public-intelligence project; it already foregrounds methodology, lawful public contact, corrections, and anti-recklessness boundaries. What it does not yet have is a normalized, indexable, and regularly updated organization directory. In the already-available crawl findings, 2IA appears as a framework site with issue hubs, dossier stubs, and trust pages, but no dedicated “organizations” section and no live organization-profile system; the public archive also still exposes a default WordPress placeholder post.

The most important strategic move is to make 2IA entity-centric. That means a new Organizations vertical with stable canonical URLs such as https://2ia.org/org/{slug}/, one profile per organization, visible verification dates, controlled tags, JSON-LD, and a public corrections path. Formal institutions such as investigative newsrooms, evidence labs, digital-rights groups, and secure-tech nonprofits should be treated as ordinary directory entries. Historically important but politically contentious hacker, leak, or hacktivist entities should be profiled with more context and tighter moderation. Leaderless banners such as Anonymous should not be treated as ordinary organizations; they should remain contextual explainer pages or special-case “movement/banner” entries rather than standard “official organization” profiles.

The opportunity is unusually strong because the current public surface is still thin. The crawl-based materials show empty category archives, a largely framework-like research archive, and source-controlled virtual/public fallback routes in the theme itself. That means a carefully built directory can become the most useful and most distinctive part of the site faster than a traditional publication backlog would. If built correctly, the directory could let 2IA own the “who’s who” layer for the OSINT, civil-liberties, transparency, and hacktivist-adjacent ecosystem.

Current site crawl and inventory

The already-available crawl data shows a site organized around Home, Start Here, Research Archive, Methodology, Support, and About, plus issue hubs such as Surveillance Systems, Open-Source Intelligence, and Anonymous Hacktivist Collective, along with trust and utility pages such as Public Records And FOIA, Ethics And Civil Liberties, Contact, Lawful Contact, Newsletter, Volunteer, Privacy Policy, and Corrections And Right Of Reply. The uploaded source-controlled PHP file further suggests that several of these routes are implemented as fallback or virtual public pages, which helps explain why the site feels architecturally complete while remaining content-light. Crawl access beyond linked HTML and the already-captured route set is still unspecified; direct sitemap/robots confirmation was not available in the prior research materials.

The key finding for task one is straightforward: no live organization-directory entries were found in the accessible crawl dataset. The site today is a publication framework and issue-map, not a “who’s who” directory. The closest thing to organization entries are contextual outbound citations to institutions such as FOIA.gov, DOJ OIP, the FTC, NIST, NARA, RCFP, and MuckRock. That is useful, but it is not yet a browsable organization index.

The page inventory below consolidates the known linked-page crawl from the already-available research materials. For pages whose own meta descriptions were not separately exposed in the prior crawl, the “description” field uses the observed lede or lead summary captured in the earlier report. Where crawl status is uncertain beyond linked HTML, that is stated explicitly.

No live organization-directory entries were found in the above inventory. In practical terms, 2IA currently has zero directory entries and zero organization profile pages in the ordinary sense.

The only organization-like items currently present are contextual outbound references used as supporting citations inside issue pages and archive materials. Those are useful seed signals for a future “related organizations” block.

These outbound references underscore the strategic gap: 2IA already points toward the right kinds of institutions, but it does so incidentally, not through a dedicated directory layer.

Missing organizations and editorial scope

Because 2IA already defines OSINT as accountable public-intelligence work and already treats Anonymous as a loose banner rather than a stable institution, the directory should launch by prioritizing formal, durable, official-source organizations first. That means investigative newsrooms, evidence labs, human-rights documentation groups, digital-rights NGOs, secure-tech projects, public-records infrastructure, and formal hacker associations. Historically important but contested leak or hacktivist entities should still be included, but with tighter editorial notes and a higher moderation tier.

The table below identifies the highest-priority missing entries to add immediately. The goal is not to exhaust the ecosystem on day one; it is to create the strongest possible first-release spine.

A crucial editorial rule follows from this list: “high-priority” does not mean “endorsed.” In the OSINT and hacktivist-adjacent space, some of the most important entities are also the most controversial. 2IA should therefore differentiate between “important to map” and “safe to normalize.” That distinction is especially important for leaderless banners, leak brands, and historically significant hacker collectives.

Taxonomy, metadata, and source model

A definitive directory should not behave like a loose tag cloud. It should separate institution type, topic/method, and risk/moderation status. The strongest organizing principle for 2IA is a two-layer taxonomy: one primary category per entity, then controlled secondary tags for method, issue area, geography, and organizational form. That directly matches the broader OSINT demand signals in the uploaded background materials, which emphasize accountable workflows, verifiable methods, evidence preservation, and discoverability rather than random link accumulation.

flowchart TD
    A[2IA Organizations Directory]
    A --> B[OSINT and Investigations]
    A --> C[Public Records and Transparency]
    A --> D[Digital Rights and Civil Liberties]
    A --> E[Secure Tech and Measurement]
    A --> F[Hacker Associations and History]
    A --> G[Leak and Transparency Collectives]

    B --> B1[Investigative newsroom]
    B --> B2[Evidence lab]
    B --> B3[Training community]
    B --> B4[Research nonprofit]

    C --> C1[FOIA platform]
    C --> C2[Open-government guide]
    C --> C3[Archive and records group]

    D --> D1[Privacy advocacy]
    D --> D2[Free-expression advocacy]
    D --> D3[Internet-rights NGO]

    E --> E1[Censorship measurement]
    E --> E2[Anonymity tooling]
    E --> E3[Security research lab]

    F --> F1[Formal hacker association]
    F --> F2[Historic collective]
    F --> F3[Community infrastructure]

    G --> G1[Leak publisher]
    G --> G2[Transparency collective]

The primary controlled categories should be: OSINT and Investigations, Human Rights Evidence, Public Records, Digital Rights, Privacy, Secure Communications, Internet Censorship, Security Research, Hacker Association, Hacktivist History, Leak / Transparency, and Community Infrastructure. Secondary tags should be tightly governed and finite, such as geolocation, video-verification, foia, spyware, surveillance, censorship, anonymity, public-records, open-data, cross-border-journalism, archive, forensics, secure-messaging, and protest-rights. The directory should not allow uncontrolled free-form tags. That creates clutter, weakens internal search, and produces thin archive pages.

The metadata layer should be richer than the current site’s issue pages because a directory entry is both a webpage and a dataset row. These are the fields I recommend as the minimum publishable schema.

A strong canonical rule is essential. Every organization should have one internal canonical URL, with alias redirects. For acronym-first entities, use the shortest unambiguous slug, such as /org/eff/, /org/epic/, /org/icij/, /org/occrp/, and /org/ooni/, then 301-redirect long-name variants. For entities better known by full names, use the full hyphenated slug, such as /org/forensic-architecture/ or /org/freedom-of-the-press-foundation/. This is cleaner for users and much better for search than multiple competing internal URLs.

The source-priority model should be explicit and public. OSINT literature and the user-needs materials both stress that no single source is sufficient, and that verifiable workflow matters more than volume. For a directory, that means official identity first, code second, low-volatility social third, volatile social fourth, and methods literature as context rather than identity.

Seed directory and structured data

The fastest way for 2IA to look definitive is to publish a seed set of fifty profiles that cover the main strata of the ecosystem: OSINT newsrooms and evidence labs, public-records infrastructure, digital-rights NGOs, secure-tech and measurement projects, formal hacker associations, community infrastructure, and transparency or leak collectives. The table below pairs each exact suggested link text with the preferred official URL and the recommended internal canonical URL on 2IA. This is the launch spine I would build first.

The profile-level structured-data pattern should pair a ProfilePage with a nested Organization. The example below uses Bellingcat, but the same structure should be reused for all seed entries, changing only the organization-specific fields and verified sameAs[] links. For controversial or historical profiles, keep the same shape but use more cautious descriptions and omit unverified social handles.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "@id": "https://2ia.org/org/bellingcat/",
  "url": "https://2ia.org/org/bellingcat/",
  "name": "Bellingcat",
  "description": "2IA directory profile for Bellingcat.",
  "isPartOf": {
    "@type": "CollectionPage",
    "@id": "https://2ia.org/organizations/",
    "url": "https://2ia.org/organizations/",
    "name": "2IA Organizations Directory"
  },
  "mainEntity": {
    "@type": "Organization",
    "name": "Bellingcat",
    "url": "https://www.bellingcat.com/",
    "description": "Investigative outlet and training community focused on open-source investigations, verification, and collaborative reporting.",
    "sameAs": [
      "https://www.bellingcat.com/"
    ],
    "keywords": [
      "OSINT",
      "investigations",
      "verification",
      "geolocation",
      "training"
    ]
  },
  "additionalProperty": [
    {
      "@type": "PropertyValue",
      "name": "last_verified",
      "value": "2026-05-17"
    },
    {
      "@type": "PropertyValue",
      "name": "risk_tier",
      "value": "Green"
    },
    {
      "@type": "PropertyValue",
      "name": "correction_url",
      "value": "https://2ia.org/corrections-and-right-of-reply/"
    }
  ]
}
</script>

The directory index should use an ItemList that points to the internal 2IA profile URLs. That lets search systems understand the page as a directory and also decouples 2IA’s canonical pages from the organizations’ external homepages.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ItemList",
  "name": "2IA Directory of OSINT, digital-rights, and hacktivist-related organizations",
  "url": "https://2ia.org/organizations/",
  "itemListOrder": "https://schema.org/ItemListOrderAscending",
  "numberOfItems": 50,
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "item": {"@type": "ProfilePage", "name": "Bellingcat", "url": "https://2ia.org/org/bellingcat/"}},
    {"@type": "ListItem", "position": 2, "item": {"@type": "ProfilePage", "name": "Global Investigative Journalism Network", "url": "https://2ia.org/org/gijn/"}},
    {"@type": "ListItem", "position": 3, "item": {"@type": "ProfilePage", "name": "Centre for Information Resilience", "url": "https://2ia.org/org/centre-for-information-resilience/"}},
    {"@type": "ListItem", "position": 4, "item": {"@type": "ProfilePage", "name": "C4ADS", "url": "https://2ia.org/org/c4ads/"}},
    {"@type": "ListItem", "position": 5, "item": {"@type": "ProfilePage", "name": "Mnemonic", "url": "https://2ia.org/org/mnemonic/"}},
    {"@type": "ListItem", "position": 6, "item": {"@type": "ProfilePage", "name": "WITNESS", "url": "https://2ia.org/org/witness/"}},
    {"@type": "ListItem", "position": 7, "item": {"@type": "ProfilePage", "name": "Forensic Architecture", "url": "https://2ia.org/org/forensic-architecture/"}},
    {"@type": "ListItem", "position": 8, "item": {"@type": "ProfilePage", "name": "Berkeley Human Rights Center", "url": "https://2ia.org/org/berkeley-human-rights-center/"}},
    {"@type": "ListItem", "position": 9, "item": {"@type": "ProfilePage", "name": "Amnesty International Crisis Evidence Lab", "url": "https://2ia.org/org/amnesty-crisis-evidence-lab/"}},
    {"@type": "ListItem", "position": 10, "item": {"@type": "ProfilePage", "name": "OCCRP", "url": "https://2ia.org/org/occrp/"}},
    {"@type": "ListItem", "position": 11, "item": {"@type": "ProfilePage", "name": "ICIJ", "url": "https://2ia.org/org/icij/"}},
    {"@type": "ListItem", "position": 12, "item": {"@type": "ProfilePage", "name": "ProPublica", "url": "https://2ia.org/org/propublica/"}},
    {"@type": "ListItem", "position": 13, "item": {"@type": "ProfilePage", "name": "Airwars", "url": "https://2ia.org/org/airwars/"}},
    {"@type": "ListItem", "position": 14, "item": {"@type": "ProfilePage", "name": "The Sentry", "url": "https://2ia.org/org/the-sentry/"}},
    {"@type": "ListItem", "position": 15, "item": {"@type": "ProfilePage", "name": "Open Measures", "url": "https://2ia.org/org/open-measures/"}},
    {"@type": "ListItem", "position": 16, "item": {"@type": "ProfilePage", "name": "OSINT Combine", "url": "https://2ia.org/org/osint-combine/"}},
    {"@type": "ListItem", "position": 17, "item": {"@type": "ProfilePage", "name": "OSINT Curious", "url": "https://2ia.org/org/osint-curious/"}},
    {"@type": "ListItem", "position": 18, "item": {"@type": "ProfilePage", "name": "Trace Labs", "url": "https://2ia.org/org/trace-labs/"}},
    {"@type": "ListItem", "position": 19, "item": {"@type": "ProfilePage", "name": "SANS Institute", "url": "https://2ia.org/org/sans-institute/"}},
    {"@type": "ListItem", "position": 20, "item": {"@type": "ProfilePage", "name": "MuckRock", "url": "https://2ia.org/org/muckrock/"}},
    {"@type": "ListItem", "position": 21, "item": {"@type": "ProfilePage", "name": "Reporters Committee for Freedom of the Press", "url": "https://2ia.org/org/rcfp/"}},
    {"@type": "ListItem", "position": 22, "item": {"@type": "ProfilePage", "name": "National Security Archive", "url": "https://2ia.org/org/national-security-archive/"}},
    {"@type": "ListItem", "position": 23, "item": {"@type": "ProfilePage", "name": "Freedom of the Press Foundation", "url": "https://2ia.org/org/freedom-of-the-press-foundation/"}},
    {"@type": "ListItem", "position": 24, "item": {"@type": "ProfilePage", "name": "Citizen Lab", "url": "https://2ia.org/org/citizen-lab/"}},
    {"@type": "ListItem", "position": 25, "item": {"@type": "ProfilePage", "name": "Open Technology Fund", "url": "https://2ia.org/org/open-technology-fund/"}},
    {"@type": "ListItem", "position": 26, "item": {"@type": "ProfilePage", "name": "OONI", "url": "https://2ia.org/org/ooni/"}},
    {"@type": "ListItem", "position": 27, "item": {"@type": "ProfilePage", "name": "Tor Project", "url": "https://2ia.org/org/tor-project/"}},
    {"@type": "ListItem", "position": 28, "item": {"@type": "ProfilePage", "name": "Access Now", "url": "https://2ia.org/org/access-now/"}},
    {"@type": "ListItem", "position": 29, "item": {"@type": "ProfilePage", "name": "Electronic Frontier Foundation", "url": "https://2ia.org/org/eff/"}},
    {"@type": "ListItem", "position": 30, "item": {"@type": "ProfilePage", "name": "EPIC", "url": "https://2ia.org/org/epic/"}},
    {"@type": "ListItem", "position": 31, "item": {"@type": "ProfilePage", "name": "Center for Democracy & Technology", "url": "https://2ia.org/org/cdt/"}},
    {"@type": "ListItem", "position": 32, "item": {"@type": "ProfilePage", "name": "Privacy International", "url": "https://2ia.org/org/privacy-international/"}},
    {"@type": "ListItem", "position": 33, "item": {"@type": "ProfilePage", "name": "Open Rights Group", "url": "https://2ia.org/org/open-rights-group/"}},
    {"@type": "ListItem", "position": 34, "item": {"@type": "ProfilePage", "name": "ARTICLE 19", "url": "https://2ia.org/org/article-19/"}},
    {"@type": "ListItem", "position": 35, "item": {"@type": "ProfilePage", "name": "Fight for the Future", "url": "https://2ia.org/org/fight-for-the-future/"}},
    {"@type": "ListItem", "position": 36, "item": {"@type": "ProfilePage", "name": "Tactical Tech", "url": "https://2ia.org/org/tactical-tech/"}},
    {"@type": "ListItem", "position": 37, "item": {"@type": "ProfilePage", "name": "Front Line Defenders", "url": "https://2ia.org/org/front-line-defenders/"}},
    {"@type": "ListItem", "position": 38, "item": {"@type": "ProfilePage", "name": "DefendDefenders", "url": "https://2ia.org/org/defenddefenders/"}},
    {"@type": "ListItem", "position": 39, "item": {"@type": "ProfilePage", "name": "Internet Freedom Foundation", "url": "https://2ia.org/org/internet-freedom-foundation/"}},
    {"@type": "ListItem", "position": 40, "item": {"@type": "ProfilePage", "name": "Wikimedia Foundation", "url": "https://2ia.org/org/wikimedia-foundation/"}},
    {"@type": "ListItem", "position": 41, "item": {"@type": "ProfilePage", "name": "Chaos Computer Club", "url": "https://2ia.org/org/chaos-computer-club/"}},
    {"@type": "ListItem", "position": 42, "item": {"@type": "ProfilePage", "name": "Cult of the Dead Cow", "url": "https://2ia.org/org/cult-of-the-dead-cow/"}},
    {"@type": "ListItem", "position": 43, "item": {"@type": "ProfilePage", "name": "Riseup", "url": "https://2ia.org/org/riseup/"}},
    {"@type": "ListItem", "position": 44, "item": {"@type": "ProfilePage", "name": "Telecomix", "url": "https://2ia.org/org/telecomix/"}},
    {"@type": "ListItem", "position": 45, "item": {"@type": "ProfilePage", "name": "Distributed Denial of Secrets", "url": "https://2ia.org/org/ddosecrets/"}},
    {"@type": "ListItem", "position": 46, "item": {"@type": "ProfilePage", "name": "WikiLeaks", "url": "https://2ia.org/org/wikileaks/"}},
    {"@type": "ListItem", "position": 47, "item": {"@type": "ProfilePage", "name": "Cryptome", "url": "https://2ia.org/org/cryptome/"}},
    {"@type": "ListItem", "position": 48, "item": {"@type": "ProfilePage", "name": "The Yes Men", "url": "https://2ia.org/org/the-yes-men/"}},
    {"@type": "ListItem", "position": 49, "item": {"@type": "ProfilePage", "name": "FIRST", "url": "https://2ia.org/org/first-org/"}},
    {"@type": "ListItem", "position": 50, "item": {"@type": "ProfilePage", "name": "Shadowserver Foundation", "url": "https://2ia.org/org/shadowserver-foundation/"}}
  ]
}
</script>

Implementation plan and governance

The lowest-risk technical path is to treat the directory as an extension of the current WordPress/public-framework architecture rather than a rebuild. The uploaded site analyses and theme route file indicate a WordPress-based publication scaffold with source-controlled route definitions and a still-thin public content layer. That makes a custom post type and taxonomy approach much more attractive than a platform migration.

The implementation work should be prioritized around entity creation, crawlability, cleanup, and governance. 2IA will not become definitive by adding one long “links” page. It becomes definitive by treating directory entries as durable editorial objects, each with ownership, metadata, revision history, and a public correction mechanism.

The moderation policy is as important as the CMS work. The uploaded Anonymous and hacktivism analyses make the structural problem clear: some of the most salient entities in this space are not conventional institutions at all. 2IA should therefore publish a visible policy that distinguishes between stable organizations, contentious but formal groups, leak/transparency entities, and claimant banners or movements.

The timeline below is aggressive but realistic for a first public release. It front-loads architecture and cleanup, then seeds the first fifty profiles, then adds governance and SEO hardening.

gantt
    title 2IA directory launch plan
    dateFormat  YYYY-MM-DD
    section Foundations
    Create organization post type, fields, templates :a1, 2026-05-18, 14d
    Build /organizations/ hub and archive pages :a2, 2026-05-18, 14d
    Remove placeholder content and hide thin archives :a3, 2026-05-18, 10d

    section Seed content
    Build first 20 critical profiles :b1, 2026-06-01, 10d
    Build remaining 30 seed profiles :b2, 2026-06-08, 14d
    Add related-organization blocks across issue hubs :b3, 2026-06-08, 10d

    section SEO and structured data
    Add per-profile structured data :c1, 2026-06-12, 7d
    Add ItemList schema to indexes and category pages :c2, 2026-06-12, 7d
    Canonicals, sitemap, breadcrumbs, internal-link QA :c3, 2026-06-19, 10d

    section Governance
    Publish moderation and source-priority policy :d1, 2026-06-22, 5d
    Add update requests and corrections workflow :d2, 2026-06-27, 7d
    Stand up editorial review calendar :d3, 2026-06-27, 7d

    section Launch
    Public launch of organizations directory :e1, 2026-07-07, 1d
    Post-launch re-verification and gap fill :e2, 2026-07-08, 21d

If I had to rank the single biggest wins, they would be these: launch /organizations/, create fifty excellent profiles with verification dates, remove thin/empty public noise, and publish the moderation/source-priority rules before adding controversial entities. That is the path from “interesting site” to “definitive directory.”

Open questions and limitations

This report uses the already-available crawl findings and uploaded background materials as its starting dataset. That dataset is strong enough to support a rigorous architecture and seed-plan recommendation, but it also has clear limits. Direct sitemap or robots access was not confirmed in those earlier materials, so crawl completeness beyond linked HTML remains unspecified. In addition, some public routes may be generated through the theme’s source-controlled virtual-page system rather than ordinary authored pages, which is relevant when deciding how much of the current public surface reflects finished editorial intent.

A second limitation is volatility. Official homepages are usually stable enough to serve as canonical external references, but social handles and contact endpoints change more often. That is why the tables above prioritize official URLs first and treat many social/contact entries as “verify at publication.” For a site that wants to be definitive, inventing unstable social metadata is more harmful than leaving it blank until verified from the official site footer. That same caution is especially important for leaderless or claimant-style banners in the hacktivist space.