Geist
Inter
Inter
Mono
Your courier wrote down how long
you have to complain. Did you read it?
Blue Dart says 30 days, and starts the clock when they accept the parcel. DTDC says 30 days, and starts it when you hand the consignment over. Delhivery says 3 days, and starts it at delivery. Same country, same parcel, and one window is ten times shorter than the others. ShipSense reads those pages on a schedule, quotes them exactly, fingerprints what it read, and timestamps the record into Bitcoin — so if a window quietly gets shorter, both versions are dated and on the record.
Is your claim window still open?
Two inputs. Nothing leaves your browser — this runs entirely on your device, and no date you type is sent anywhere.
Every carrier starts its clock somewhere different, so the date this field wants changes with the carrier you pick. Read the label above it before you type.
Three carriers publish a window we can read today. What is missing, and why, is listed further down — including the terms page that no longer exists at all.
What they published, word for word.
Loaded live from the ledger every time you open this page. These are the carriers' own statements — not ShipSense measurements. Nothing here comes from any merchant's shipments.
SNAPSHOT — the live ledger is unreachable from your browser right now, so this is the copy taken 19 Aug 2026, 08:51 IST. It is not live and we would rather say so.
BLUEDART — delivery standard
Domestic Priority 1030 A guaranteed door-to-door time definite delivery of shipments by air the next possible business day by 10:30 hours, targeted at time-critical business-to-business needs. An Express time definite service with Money Back Guarantee* (MBG) to the select Pin codes in Chennai, Delhi, Ahmedabad, Mumbai, Bangalore, Navi Mumbai and Gurgaon by 10:30 hrs on the next possible business day. Pickup service is available from
BLUEDART — dispute window
CLAIMS 11.1. Any claim must be brought by the shipper and delivered, in writing to the office of BD nearest to the location at which the shipment is accepted within 30 days from the date of such acceptance. No claim can be made against BD beyond this time limit. 11.2.
DELHIVERY — dispute window
Is there any timeline for creating a claim? Damaged, Mismatched, or Missing Item If your shipment is delivered but found to be damaged, contains different items,or has missing contents, you must submit a claim within 72 hours of delivery. Lost Shipments If the shipment is secured with Protect VAS , a claim will be automatically raised upon confirmation of loss within the Delhivery network. How can i get help and support
DTDC — dispute window
All claims in respect of loss or damage of consignment shall be made within a period of 30 days from the date of tendering a consignment to DTDC. Any claim requests received after this period shall not be entertained. Freight Refund:
What is missing, and exactly why.
A courier missing from a board with no explanation reads as a courier with nothing to disclose. So the gaps get published too, with the exact reason and the address, and you can check every one of them yourself in about ten seconds. Not every gap is a failure on the carrier's side, and not every one is a failure on ours — the reason says which.
DELHIVERY — dispute window
not sealedNot sealed, but NOT unreadable: the page renders fully in a browser (~34,000 characters, "Updated on 13th October, 2025") and states "Complaints/claims/queries for damages and mis-delivery have to be raised within 3 days from the date of delivery." A scheduled SERVER-SIDE fetch still returns a JavaScript shell, so we cannot re-fetch it identically tomorrow. We only seal what the scheduler can reproduce on its own, so this clause is recorded as read by a human on 18 Aug 2026 and is not part of the hash chain.
https://www.delhivery.com/tnc-direct — open it yourself and see what your browser does.
ECOMEXPRESS — dispute window
not sealedThe terms page no longer exists. As of 18 Aug 2026 https://www.ecomexpress.in/terms-conditions/ serves a 96-character splash reading "Better Together — Delhivery and Ecom Express Unite to Serve a Growing India", with every link pointing to delhivery.com. Delhivery completed its acquisition of Ecom Express (CCI approved June 2025). A merchant with a live Ecom Express consignment cannot read the terms that governed it at this address. Separately, a TLS certificate error (NET::ERR_CERT_DATE_INVALID) was reproduced on this URL in Chrome on 18 Aug 2026.
https://www.ecomexpress.in/terms-conditions/ — open it yourself and see what your browser does.
These describe what our fetcher found at a public address on a given date. They are observations, not statements about a carrier's service or its intentions. Two things get recorded here and they are not the same: a page we can read but cannot re-fetch identically on a schedule is quoted and dated but left out of the hash chain, while a page that no longer serves terms at all is recorded as exactly that.
The record is timestamped into Bitcoin.
Every entry above is hash-chained. Once a day the head of that chain is written to a public repository, submitted to OpenTimestamps, and stamped by an independent RFC-3161 timestamp authority. When the OpenTimestamps proof completes, the head is provably older than a specific Bitcoin block. We hold the database credentials, so we could edit a row — what we cannot do is edit it and still match a hash that a block miner sealed before we touched it.
The head of the chain is provably older than this block.
Change one character anywhere in the ledger and this stops matching.
Written to a public repository anyone can read without asking us.
The anchor file contains hashes and counts only — no shipment, merchant, courier or personal data. Read it yourself: this day's anchor or the whole public repository.
A record is only worth something if it started before the argument.
The value is the history, not the scrape
Anyone can read a courier's terms page today. Nobody can read what it said on 8 August 2026 — unless somebody was already watching and could prove when they looked. That is the whole asset, and it only gets more valuable the longer it runs.
A shortened window is retroactive, quietly
If a claim window changes, the parcel that shipped under the old one still shipped under the old one. Without a dated record, you have no way to show which version applied to your consignment. With one, you do.
Exoneration is symmetric
This board records that the carriers we can read have changed nothing in the period observed. That is a finding in their favour and it is published exactly as prominently as anything else here.
Nothing here is about your data
Every word on this page comes from a courier's own public website. No merchant's shipments, no customer records, no personal data of any kind touches this board.
The limits, before you ask.
- It watches a small number of pages. It is not a complete map of every clause every Indian courier publishes.
- The quoted clauses are recorded exactly but marked unparsed where no human has yet extracted structured values. The quote is the record; the summary is convenience.
- A public terms page is not necessarily your contract. Negotiated agreements override it and we cannot see yours.
- ShipSense has filed no courier disputes and recovered no money to date. This board is a record, not a result.
- “Changes seen: 0” means zero changes since we started watching — not zero changes ever.
Now do the same thing to your own shipment book.
This page shows what your courier promised. The audit shows what actually happened — your true RTO rate against what couriers reported, your worst pincodes ranked by rupees lost, and which failed deliveries won't survive a timestamp check. Your own data, your own number, no card.
Get my free RTO audit →A math-first logistics intelligence layer for Indian D2C. We score RTO before you ship, catch fake NDRs, and recover what couriers owe you.
Founder & Creator, ShipSense