← the record

Proof: ‘Came close at high speed’: What led to India-Pakistan naval collision at Arabian Sea

The record — the exact bytes that were hashed

{"first_seen":"2026-09-16T09:31:21Z","headline":"‘Came close at high speed’: What led to India-Pakistan naval collision at Arabian Sea","kind":"front-page-headline","rank":1,"source":"timesofindia","url":"https://timesofindia.indiatimes.com/india/came-close-at-high-speed-what-led-to-india-pakistan-naval-collision-at-arabian-sea/articleshow/134281629.cms","v":1}

Download headline-4ba5e7cfcc64.json

SHA-256

4ba5e7cfcc64222ef6737490e6230b3d7ea3b11697e423018ead6f91c65701fa

OpenTimestamps

Not sealed.

Wayback Machine

• The record pageNot sealed — no capture of this page was requested.
• The story pageNot sealed — no capture of the story page was requested.

Check it yourself — none of this needs this site

1. Hash the record: sha256sum headline-4ba5e7cfcc64.json prints 4ba5e7cfcc64222ef6737490e6230b3d7ea3b11697e423018ead6f91c65701fa. Its first twelve characters are the end of this record's address.
2. There is no OpenTimestamps receipt for this record yet.
3. Open the Wayback Machine's captures above: the capture of the record page shows this hash as it stood then, and the capture of the story page shows the newsroom's own page.

This headline has not been sealed. Headlines are sealed automatically within minutes of first being seen; older ones are sealed on request, and are then marked as a backfill.