Opening note
A pivot gives you a new lead. It does not prove the original claim.
This is where many OSINT investigations go wrong. Two domains share infrastructure, so both are treated as part of one operation. Two accounts use the same image, so they are assumed to belong to the same person. An older copy appears, so the oldest indexed page is described as the original source.
- Record the claim.
- Pivot from a known detail.
- Validate the new result independently.
- Stop when the evidence runs out.
One method: tracing the Blue Marble photograph
Imagine that someone posts NASA's Blue Marble image with this caption:
The original Blue Marble photograph was taken by Harrison Schmitt during Apollo 17 on 7 December 1972.
The caption contains separate claims about the image, mission, date, photographer, and file version. Test them separately.
Step 1: preserve the starting point
Record the page URL, visible caption, publication date, and image. If possible, save the file and calculate its SHA-256 hash. The hash identifies the exact file you examined. It does not identify every resized or edited copy.
Step 2: run a visual search
Upload the image to Google Lens and TinEye. Results will include cropped, rotated, compressed, and colour-adjusted copies. This is the first pivot, not validation. TinEye's oldest result is the oldest copy in its index, not necessarily the original publication.
A strong result is the Wikimedia Commons file page. It connects the photograph to Apollo 17 and gives us a more useful pivot: AS17-148-22727.
Step 3: pivot on the identifier
Search the exact identifier, then restrict the search to NASA:
"AS17-148-22727"
site:nasa.gov "AS17-148-22727"NASA's History of the Blue Marble connects the identifier to the Apollo 17 crew and 7 December 1972. A separate NASA visualisation page supports the mission, date, and photograph number. Those parts of the caption now have independent support.
Step 4: inspect the file history
The Commons history records later colour balancing, noise reduction, and defect removal. An original-orientation version also shows that the familiar image is distributed in more than one orientation.
We can say the shared image is based on AS17-148-22727. We cannot call every similar copy the original file. The subject may be the same while the file provenance differs.
Step 5: reach the failure point
Now test the claim that Harrison Schmitt personally pressed the shutter. One Commons record names Schmitt or Apollo 17. Other records attribute the photograph to the Apollo 17 crew. The NASA pages checked here support the crew and mission, but do not establish which astronaut pressed the shutter.
Stop. Do not select the most specific attribution because it makes the report sound complete. The supported conclusion is:
NASA photograph AS17-148-22727 was taken during Apollo 17 on 7 December 1972. The public sources checked attribute it to the Apollo 17 crew. They do not establish which crew member pressed the shutter.
Field exercise: a ten-minute image check
Choose a public image attached to a harmless claim. Do not use a private person's photograph. Use Google Lens, TinEye, Google Search, Wayback Machine, and Wikimedia Commons when relevant.
- Write the claim in one sentence.
- Run the image through Google Lens and TinEye.
- Open one older or more authoritative result.
- Record its URL, date, publisher, and caption.
- Search an exact phrase, filename, or identifier.
- Find one independent source.
- Write what is supported, inferred, and still unknown.
Stop after ten minutes. The goal is a result another researcher can check, not a complete history of the image.
Tool notes
- Google Lens helps find visually similar and cropped copies.
- TinEye helps compare indexed copies and transformations. Its dates are not a complete publication history.
- Wayback Machine can show that a page existed by a capture date. It does not prove authorship or first publication.
One case worth studying
Compare the commonly circulated Blue Marble with its original-orientation version. Rotation, restoration, and file history change what can be claimed about a specific copy. Content identity and file identity are not the same thing.
From my desk
I use one test before adding a conclusion to my notes:
Which source supports this exact sentence?
If the answer is a search result, a visual resemblance, or an unsourced summary, the sentence is not ready. I find stronger support, reduce the confidence, or remove the claim.
Before you go
- One thing to try
- Document the path from one shared image to an authoritative source.
- One limitation to remember
- The oldest search result is not necessarily the original publication.
- One relevant CSINT resource
- Image verification workflow
- One question to reply to
- Which is harder for you: finding leads or deciding when the evidence is strong enough?