Chain of custody receipt

Source #60078

Cryptographic attestation that the document below was captured in Goblin House's archive at the timestamp shown, with the hash listed. If the original URL goes dark or its content changes, this receipt remains as evidence of what the public record looked like at capture time.

TitleSEC EDGAR: filing — Google (2006-07-28)
Original URLhttps://efts.sec.gov/LATEST/search-index?q=%22Google%22&dateRange=custom&forms=4,SC%2013D,SC%2013G,DEF%2014A,10-K,10-Q
PublicationSEC EDGAR
Source typesec_filing
Date2006-07-28
EntityGoogle
Captured1970-01-01T00:00:00.000Z UTC
Hash computed at2026-05-23T00:13:06.668Z UTC
SHA-256d06e5f93ec7383a68a1c23673c20e7b0801b271f9b59b3e54e6e6bc6830c3c2b
Content length548 bytes
Content preview (first 800 chars) 
{
  "ciks": [
    "0001342960"
  ],
  "period_ending": null,
  "file_num": [
    "333-133855"
  ],
  "display_names": [
    "DIVX INC  (CIK 0001342960)"
  ],
  "xsl": null,
  "sequence": 6,
  "root_forms": [
    "S-1"
  ],
  "file_date": "2006-07-28",
  "biz_states": [
    "CA"
  ],
  "sics": [
    "7371"
  ],
  "form": "S-1/A",
  "adsh": "0001047469-06-010061",
  "film_num": [
    "06987754"
  ],
  "biz_locations": [
    "San Diego, CA"
  ],
  "file_type": "EX-10.17",
  "file_description": "EXHIBIT 10.17",
  "inc_states": [],
  "items": []
}

Verifying this receipt

The hash above was computed as:

sha256( coalesce(url, '<no-url>') || '\n' || raw_content )

Anyone with a copy of the original document can verify the match:

  1. Take the URL field and the original document content.
  2. Concatenate url + '\n' + content and SHA-256 it.
  3. Compare to the SHA-256 row above.

Or POST the candidate content to /source/60078/verify and our server will compare for you:

curl -X POST https://www.goblinhouse.net/source/60078/verify \
  -H "Content-Type: text/plain" \
  --data-binary @document.txt

Companion machine-readable receipt: /source/60078/receipt.json