Quick answer
The best OSINT tools for journalists depend on the evidence problem.
A good newsroom stack is not a giant bookmark list. It is a sequence: preserve the source, identify the evidence type, run the smallest useful checks, and write only the conclusion the evidence can support.
- For images or video: InVID, TinEye, ExifTool, Google Earth, SunCalc, and satellite context.
- For web claims: Wayback Machine, archive.today, Perma.cc, Hunchly, and direct screenshots before pages change.
- For companies and networks: OpenCorporates, Aleph, OpenSanctions, LittleSis, Companies House, SEC EDGAR, and source filings.
- For domains: urlscan.io, SecurityTrails, crt.sh, WHOIS/RDAP checks, and archive captures as separate evidence layers.
Recommended newsroom stack
Visual claims
InVID Verification Toolkit + TinEye
Use first when a photo or short video may be old, reused, clipped, or attached to the wrong event. Keyframes and reverse matches are leads; they do not prove origin by themselves.
Best for: reuse checks, keyframe extraction, first-pass visual triage
Preservation
Wayback Machine, archive.today, Perma.cc
Use before contacting a subject or publishing. Pages, captions, prices, bios, job posts, and product claims can disappear once attention arrives.
Best for: source trail, editorial review, legal defensibility
Entities
OpenCorporates, Aleph, OpenSanctions
Useful for turning names, companies, officers, addresses, sanctions mentions, and public-record leads into a research map. Always check jurisdiction and source date.
Best for: company identity, networks, sanctions context
Infrastructure
urlscan.io, SecurityTrails, crt.sh
Use when a story starts with a website, suspicious landing page, email domain, or public claim hosted on a changing domain.
Best for: redirects, certificates, DNS history, web footprint
How to choose under deadline pressure
If the claim is visual
Preserve the post, extract frames, reverse-search key images, test location clues, then separate what is confirmed from what is only plausible.
If the claim is about a person or company
Confirm exact names and jurisdictions first. A matching name is not enough. Look for registration numbers, role labels, dates, direct filings, and independent records.
If the claim is about a website
Capture the page, check archives, look at redirects, certificates, DNS, and public scans. Treat infrastructure overlap as a lead, not attribution.
If the claim is already viral
Use Google Fact Check Explorer, GDELT, and Media Cloud to understand who has repeated it, but still verify the original evidence yourself.
Editorial caveat
A tool result is not a publishable conclusion. Good newsroom OSINT says exactly what was checked, what the result showed, what it did not show, and what remains unresolved. Avoid exposing private people just because a tool found personal data.
Where to go next
Open OSINT for Journalists, the curated journalist collection, the visual verification workflow, or the OSINT tools directory.
