Overview

The search page at https://www.truestamp.com/search is the single place to find anything on Truestamp: your timestamped items, Truestamp blocks, public randomness beacons, and the entropy observations captured from external sources. You do not tell it what kind of thing you are looking for. It detects the format of whatever you type or paste (an identifier, a hex hash, or plain words), runs every lookup that format could match in parallel, and returns the results grouped by kind. The page works without an account: anonymous visitors can search all public data, and signed-in users additionally search the items in their own teams. A search is a shareable URL (/search?q=...), so a result set can be linked directly.

What you can paste into search

Search classifies the query by shape, then runs only the lookups that shape can match. The input is trimmed and matching is case-insensitive. A hint under the search box updates as you type, telling you which format was detected.

Two identifier notes. Item IDs and block/entropy IDs use different formats on purpose (see ULID and UUIDv7 identifiers), which is what lets search tell them apart. And a block and a beacon are two views of the same underlying record, so a UUID or a 64-character block hash returns both a Blocks group and a Beacons group, letting you choose the block explorer view or the beacon permalink for the same record.

The 32-to-128 hex range covers the hexadecimal form of common digests, from MD5 (32 characters) through SHA-256 (64) to SHA-512 (128). A query of fewer than 3 characters that matches no structured format runs no search at all; the page just asks for at least 3 characters.

How results come back

Results are grouped by kind: Items, Blocks, Beacons, and Entropy Observations. Each group shows a match count, duplicates are removed, and empty groups are not rendered. Because one query can fan out to several independent lookups, the lookups run in parallel and each has a five-second budget; a lookup that fails or times out is reported in a warning banner while every other group still renders.

Where a result row leads depends on what it is and who you are:

• Items in your current team open the item detail page when you are signed in. Anonymous visitors are routed to the item’s public verification page instead, since the item detail page is a team-scoped management view.
• Items in your other teams appear behind a collapsed “Found more in your other teams” section, each with a “Switch & open” action that switches your active team and then opens the item.
• Public items in teams you do not belong to open the item’s public verification page.
• Blocks open the block detail page when you are signed in; see the public explorer for the block pages themselves.
• Beacons open the beacon permalink, which is public for everyone.
• Entropy observations open the observation detail page when you are signed in, and every row carries a public verify action.

Find an item by a hash it contains

When you submit an item, the claims you provide typically include a hash, the fingerprint of the file or data you are timestamping (see the item’s composite fingerprint for how claims are hashed and bound). Pasting that hex digest into search matches items whose claims contain exactly that hash value. This is the fastest “do I already have a timestamp for this file?” check: hash the file locally, paste the digest, and see which items carry it.

This lookup searches the hash value inside an item’s claims, not the item’s own derived hashes. Block hashes and entropy hashes are separate lookups that only fire for exactly 64 hex characters.

Anonymous visitors match public items across all of Truestamp. Signed-in users additionally match items they can read in their currently selected team.

Free-text search over items

Any query of at least 3 characters that is not an identifier or a hex digest is treated as free text and searched against item names, descriptions, and tags.

• Matching is word-based with web-search semantics: multiple words narrow the match, and a phrase can be wrapped in quotes (“like this”) to match exactly.
• Tags are matched as whole words: each whitespace-separated word in the query is compared against item tags, case-insensitively.
• Redacted and deleted items never appear in results (see the item lifecycle).
• Results are returned newest first, capped at 25 matches per source (up to 50 combined from your other teams).

Who sees what follows item visibility: anonymous visitors match public items only, while signed-in users match items in their current team, items in their other teams, and public items in teams they do not belong to, merged without duplicates.

Team boundaries and public items

Signed-in item results are partitioned into three buckets so a match never silently crosses a team boundary: items in your currently selected team are listed first and open directly; items in your other teams are collapsed and require an explicit “Switch & open”; and public items in teams you are not a member of are collapsed and open the public verification page rather than any team view. Anonymous visitors only ever see the third kind, public items, and are always routed to public verification pages.

Before you search anything, the page also shows signed-in users their five most recent items as a starting point.

Limits

• Searches are rate limited to 60 per minute per IP address, and free-text searches are further limited to 20 per minute per IP address. Exceeding either shows a “too many requests” message.
• Free-text queries must be between 3 and 128 characters.
• Each parallel lookup has a five-second budget; a slow or failed lookup is surfaced as a warning without blocking the rest of the results.
• Free-text results are capped (25 per source, newest first), so a very broad query shows only the newest matches; narrow the words or paste an identifier for an exact find.