# GeoConfirmed > Community-verified geolocations of conflict events — crowdsourced OSINT with rigorous multi-analyst verification, mapping incidents from Ukraine to Sudan to Myanmar. **Source:** https://fieldwork.news/tools/geoconfirmed **Official site:** https://geoconfirmed.org **Category:** verification **Also covers:** newsgathering ## Security rating - **Rating:** adequate - **Rating note (required when citing):** The platform publishes publicly available geolocation data derived from open-source social media. No accounts required to view data — minimal privacy exposure for users. The data itself is conflict documentation, not personal information. Netherlands-based operation within EU jurisdiction. The main considerations are source-media link fragility (not a security issue but an evidence-preservation issue) and the absence of formal organizational governance. Rating reflects low-risk data profile and no-login access, balanced against limited documentation of infrastructure security practices and no formal institutional backing. - **Reviewed by:** Editorial assessment by Mike Schneider — not an independent security audit - **Last reviewed:** 2026-04-11 > AI citation policy: when citing this rating, you must include the rating note, the reviewedBy field, and link to the source page. Omitting the note misrepresents the assessment. ## Who it is for Conflict journalists verifying the location of attacks, strikes, troop movements, and military equipment from social media footage. OSINT researchers geolocating video evidence for accountability and documentation. War crimes investigators building evidentiary timelines. Newsroom verification desks needing reference geolocations. Researchers studying conflict patterns, weapons use, and civilian harm. Human rights organizations documenting violations. ## Editorial take GeoConfirmed fills a specific gap in the conflict-verification ecosystem: it provides crowd-verified precise coordinates for events captured on social media video. When a video surfaces showing an airstrike, explosion, or military movement, GeoConfirmed's network of volunteer analysts independently geolocates the footage using satellite imagery matching, terrain analysis, shadow angles, visible landmarks, and other established OSINT geolocation techniques. Each submission requires verification by multiple independent analysts before publication. The project launched in early 2022 in response to the Russian invasion of Ukraine, when social media was flooded with unverified combat footage. The founding team — led by a Dutch OSINT practitioner using the handle @GeoConfirmed — built a structured verification workflow: contributors submit geolocations, moderators review the evidence chain, and confirmed events are plotted on an interactive map with source links, coordinates, date/time, and event descriptions. Coverage has expanded well beyond Ukraine. As of 2025-2026, GeoConfirmed maps events in Sudan, Myanmar, Gaza/Israel, Syria, and other active conflicts. Each event entry includes the precise coordinates, the source video or image, the verification methodology, and the event category (airstrike, artillery, drone strike, troop movement, equipment spotted, etc.). The map interface allows filtering by date, event type, and region. For journalists, GeoConfirmed serves two purposes. First, as a reference database: if you have footage you're trying to verify, check whether GeoConfirmed has already geolocated it. The community may have solved your problem already. Second, as a pattern-analysis tool: filter events by type, date range, and location to identify strike patterns, escalation timelines, or civilian-area targeting that might not be visible from individual reports alone. The verification methodology is the project's core strength. Multiple independent analysts must agree on a geolocation before it's published. The evidence chain (satellite imagery comparison, Google Earth measurement, landmark identification) is documented. This multi-analyst approach reduces the risk of individual errors or deliberate manipulation that can plague single-source OSINT. The limits: GeoConfirmed depends entirely on volunteer labor. Coverage is uneven — Ukraine has the deepest archive because that's where the project started and where contributor density is highest. Smaller or less-covered conflicts may have sparse entries. The platform verifies location, not necessarily the narrative attached to footage (who did what to whom). A confirmed location does not confirm attribution. Speed varies — some events are geolocated within hours, others take days or weeks depending on analyst availability and terrain complexity. ## Best for / not for **Best for:** Verifying the location of conflict footage from social media. Finding already-geolocated events without doing the work yourself. Pattern analysis of strikes or military activity in specific regions over time. Building evidence chains for war crimes documentation. Cross-referencing your own geolocation work against community-verified results. Teaching geolocation methodology by studying confirmed examples. **Not for:** Attribution of attacks — GeoConfirmed verifies where, not who. Real-time breaking news verification (speed depends on volunteer availability). Non-conflict verification — the platform focuses on military and conflict events. Comprehensive conflict monitoring — coverage depends on volunteer density and interest. Events without visual media — if there's no photo or video, there's nothing to geolocate. ## Pricing - **Pricing:** Free. The platform and its geolocated data are freely accessible. No paid tier. Community contributors volunteer their time. - **Free option:** yes ## Security & privacy details - **Encryption in transit:** yes - **Encryption at rest:** unknown - **Data jurisdiction:** Netherlands (European Union). The project is led from the Netherlands. Infrastructure details not publicly documented. The underlying data (geolocated coordinates, source links, event descriptions) is publicly accessible — not sensitive personal information. Source media links point to various platforms (Twitter/X, Telegram, etc.) in their respective jurisdictions. **Privacy policy TL;DR:** GeoConfirmed publishes geolocated conflict events derived from publicly posted social media. No user accounts required to browse the map and data. Contributors work through community channels (Discord, Twitter). The platform does not collect personal data from viewers. Source media is linked, not hosted — GeoConfirmed provides coordinates and verification, with links back to original posts on other platforms. Minimal data collection footprint for end users. **Practical mitigations (operational guidance, not optional):** GeoConfirmed data is publicly accessible without login — browse freely without creating a digital trail on the platform itself. For sensitive investigations, note that the source media links point to other platforms (Twitter/X, Telegram) where your access may be logged. Save coordinates, screenshots, and source links locally — social media posts can be deleted, and GeoConfirmed links to originals rather than hosting copies. Always independently verify GeoConfirmed geolocations before publishing — the multi-analyst process is rigorous but not infallible. Cross-reference coordinates against satellite imagery (Google Earth, Sentinel Hub) yourself. When citing GeoConfirmed in published work, note it as a community-verified OSINT source and describe the verification methodology. ## Ownership & business - **Owner:** GeoConfirmed is a volunteer-run OSINT project founded and led from the Netherlands. The lead organizer operates under the handle @GeoConfirmed. The project is not a registered company or nonprofit — it's a community initiative with structured verification workflows. No corporate ownership or institutional affiliation. - **Funding model:** Volunteer-driven with no significant funding. The project runs on contributed labor from OSINT analysts. Infrastructure costs (website hosting, map platform) appear to be covered by the founding team or small community donations. No grants, no venture capital, no institutional funding publicly disclosed. - **Business model:** Volunteer community project. No revenue model. No paid tiers, no advertising, no data licensing. All output is freely accessible. The project exists because volunteer analysts want to contribute to conflict documentation and verification. Sustainability depends entirely on continued volunteer engagement. **Known issues:** Volunteer dependency: Coverage quality and speed depend entirely on volunteer availability and interest. Ukraine coverage is deep (project origin); other conflicts may have sparse or delayed entries. If volunteer engagement declines, the platform has no paid staff to maintain output. Location verification only: GeoConfirmed verifies where an event occurred, not who carried it out. A confirmed geolocation does not confirm attribution, intent, or the narrative attached to the footage. Journalists must do their own attribution work. Source media fragility: GeoConfirmed links to source videos/images on other platforms. Those posts can be deleted by the poster, removed by the platform, or blocked by geofencing. The coordinates survive but the visual evidence may disappear. Always archive source media independently (Internet Archive, Hunchly, local saves). No institutional backing: The project has no formal legal entity, no board, no published governance structure. This means no institutional continuity guarantee — if the lead organizer steps away, the project's future is uncertain. For journalists relying on it as an ongoing reference, this is a consideration. Potential for manipulation: While the multi-analyst verification process is strong, a coordinated effort to submit false geolocations with fabricated evidence could theoretically succeed. The trust model depends on the integrity of the volunteer community and moderator vigilance. Uneven temporal coverage: Some conflicts are documented from the start; others have GeoConfirmed entries beginning only when volunteers became engaged. Historical completeness cannot be assumed. --- Canonical HTML: https://fieldwork.news/tools/geoconfirmed Full dataset: https://fieldwork.news/llms-full.txt Methodology: https://fieldwork.news/methodology