FolioVRRecords
As at
Sun 22 Nov 2026
Entries
9
Not yet
16
Page seal 724C, 228°22′. Drawn from the SHA 256 of this page’s source text724C
Page seal724C, 228°22′

How to check a record

What the fingerprint, signature, daily root and seal on a Marsadel record mean, and how to check record MSD 0001, the firm's first real record, in your own browser.

Test a record

The touchstone

Test record MSD 0001 in your own browser

This is the firm’s first real record: the receipt file of our own read only assessment of marsadel.com, sealed on 22 Nov 2026. Your browser recomputes its receipt hash, draws the seal from it, checks each signature against the key shown on this page, and follows the Merkle path to the signed daily root, step by step. Change any value in record MSD 0001 and the file signature fails; change one inside the receipt and its seal becomes a different seal. Spaces and line breaks between fields do not count, as in the register.

Receipt file, editable

Or paste any firm-receipt/6 receipt.json here, or drop the file on this slip. It is read in this page and sent nowhere.

MSD 0001 Sealed 22 Nov 2026, at entry 23 of the register.

  • A real record: Marsadel’s own read only assessment of its own domain, marsadel.com (Unit 1, Stage A). It is not a client record.
  • No change was applied. The record says so itself (change_applied: false).
  • It found 3 tests passing and 4 failing: SPF, DMARC, the lock for a domain that sends no mail, and DNSSEC. marsadel.com has no mail or parking records yet.
  • Checked by our rule based inspector only. No second model vendor and no human reviewer have checked it.1
  • Signed with the register’s ledger key, a local file on our machine standing in for a key service.2
  • Its daily root of 22 Nov 2026 is sealed and signed, but not anchored outside the firm yet.3
  • The key on this page comes from this same site. A match shows that the file and this page agree; it is not independent proof of who made the file until a keys page and outside anchors exist.4

Download receipt.jsonDownload the public key

Seal drawn from the text as it is nowABE8782F FD7F17E1 D1ADD28E A4228504 8102C9FB 43989F92 C95BB8C9 C8C14EE4 MSD 0001ABE8
MSD 0001, ABE8, 169°00′
Sealed hashabe8782f fd7f17e1 d1add28e a4228504 8102c9fb 43989f92 c95bb8c9 c8c14ee4
Computed nowabe8782f fd7f17e1 d1add28e a4228504 8102c9fb 43989f92 c95bb8c9 c8c14ee4
Receipt hashChecking
KeyChecking
File signatureChecking
Register entryChecking
Merkle pathChecking
Daily rootChecking

Not checked here: the receipt file alone cannot show these
  • The earlier entries of the register. The page takes the link from entry 23 to the entry before it (prev_hash) as given; the rest of the chain is not published.
  • The other roots of that day. The root’s signature covers one hash of every account’s root in the register (tenant_roots_hash); the file carries only this record’s own root, so that hash is not rebuilt here.
  • The salted inputs. The salt is secret, so inputs_hash and the salted ids cannot be tied to a domain here, by design.
  • The runbook and report files. Their SHA 256 values are listed under files, but the files name the domain and are not published, so they are not checked here.
  • Outside anchors. There are none yet: the root of 22 Nov 2026 is held on our own machine and printed on this page only.3
The key this page checks against
  • fr-ed25519-44c30cd1ccb504cc7166fc504f08cde5f7d5aecf9b0ecd5bf4e8f311dcd2fa98839286e7d93841fdThe register’s ledger key, created 22 Nov 2026 and valid from then, with no end date yet. Its private half is a local file standing in for a key service. This same site serves it, so it is not independent proof yet.

Every Marsadel unit is built to end in a Proof of Fix record. This page explains how anyone can check that record: the business owner, the agency that ordered it, an insurer, or a buyer of the business. You do not need an account. The check runs in your own browser, so you do not have to take our word that the record is unchanged.

Status today, 22 Nov 2026. The software for our record log (the Register) runs on our own machine: it writes signed, chained entries, builds daily roots and has a verify command. On 22 Nov 2026 it sealed our first four real records: read only assessments of four domains the founder owns, one of them marsadel.com itself. No change was applied. Only our rule based inspector checked them; no second model vendor and no human reviewer has yet. Their daily root is sealed and signed, but not anchored outside the firm, and the signing key is a local file standing in for a key service.5 Record MSD 0001, the assessment of marsadel.com, is in the touchstone above; the other three are not published. No client record exists. This site has been live on marsadel.com since 22 Nov 2026, in English, with this page. The public per record verify lookup and the roots and keys pages follow.4

How to read a seal

How to read a sealABE8782F FD7F17E1 D1ADD28E A4228504 8102C9FB 43989F92 C95BB8C9 C8C14EE4 MSD 0001ABE8

A seal is a file’s SHA 256, struck so that it can be read back by eye. This one is the seal of record MSD 0001, the firm’s first real record. Two seals from two files differ from across a room, and in every one of their 256 marks.

  1. The notchThe fire V at the top. Digits are numbered 1 to 64, clockwise from it.
  2. The rimThe 64 hex digits of the hash, then the record number. Struck on seals of 220 px and up.
  3. The bit tracksFour rings of 64 columns: the 256 bits. Column i is digit i; the outer ring is 8, then 4, 2, 1. A bar is 1, a dot is 0.
  4. The punchOne of eight hallmark outlines, from digits 1 and 16, struck last and solid, with the first four digits as the record’s code.
  5. The rosette5, 7, 9, 12 or 16 points from digit 2, cut to one of four depths (digit 3), as a star, a scallop, a double star or engine turned (digit 4); a shallow one may be struck solid (digit 21), and digit 22 may add an inner ring or a fire bead.
  6. The needleAn arrow, a lance, a crossed, a barbed or a ringed needle (digits 9 and 17) at the bearing of digits 5 to 8, printed in degrees and minutes.
  7. The eccentric ringA small whole ring set well off the centre, like the sub dial of a watch: its direction, size and reach from digits 10 to 12. The rim edge and the track spacing come from digits 18 to 20.
  8. The nameMSD, the record number, the code and the bearing: a short name a person can say.
NameMSD 0001, ABE8, 169°00′

Every record carries four marks, the way a hallmark does

  • Sponsor’s markWho did the work. Ours is the Marsadel punch: the Latin M and the Arabic mim in one strike.
  • Standard markWhich unit was run, and every test it passed or failed, line by line.
  • Office markWho checked it. The record names the reviewer, or says plainly that no one has yet.
  • Date letterWhen it was struck. Assay offices letter the year. Our letter for 2026 is A, the first.

What a check tells you

A passing check tells you three things:

  1. The record has not changed since the day it was sealed.
  2. It was signed with a Marsadel key that was valid on that day.
  3. It is part of the daily summary we published that day, and a copy of that summary sits in public places outside our control.6

Record MSD 0001 in the touchstone on this page has no outside anchors yet, so a check of it cannot show the third point. The key it is checked against comes from this same site, so for now a passing check shows that the record and this page agree, not who made the record.

How to check, step by step

  1. Open the record.

    Record MSD 0001 is already in the touchstone above. To check another receipt, press Open a receipt.json, drop the file on the slip, or paste its text there. The file is read in this page and sent nowhere. Each client record will also get its own link, and a code printed on your "after" Domain Passport, the file that holds the evidence for your unit.7

  2. Read it.

    The receipt file lists each test and whether it passed, the checker that read it, whether a human reviewed it and, if one did, that reviewer's name, and the day it was sealed. Record MSD 0001 says that only our rule based inspector read it.1

  3. Let it run.

    There is no button to press: the check runs when the page opens and again each time the text changes. Your own browser does the math, using the file, the key shown on this page and the daily root the file carries.8

  4. Read the result.

    The touchstone shows six lines: the receipt hash, the key, the file signature, the register entry, the Merkle path and the daily root. When all six pass, as they do for record MSD 0001, the first two points hold for the key shown, and the record is in that day's root. For the third, the outside anchors will be listed beside the root; record MSD 0001 has none yet. A line struck in fire means something does not match. Once the written desk opens, write to us about it and quote the record id. What you can do until the desk opens

What the words mean

Fingerprint (hash)

A fingerprint is a short code worked out from a piece of text. The same text always gives the same code. Change one letter and the code changes completely. You cannot rebuild the text from the code. We use a standard method called SHA256.

Before we take a fingerprint of a domain name or a personal detail, we mix in a secret that belongs to that client only. We call it a salt. Without the salt, anyone could take a list of all domains, fingerprint each one, and match it to ours. With the salt, they cannot. We can still match it, while the salt exists. So your order files are deleted 12 months after your order, or at exit if that comes first, and your salt is destroyed at the same time, and we seal the date we destroyed it.9 After that, the fingerprint can no longer be read back to the domain.

Signature

A signature shows that a record was signed by the key shown and was not changed after. We sign with a private key that stays with us. Anyone can check the signature with the matching public key. Today that key is shown on this page, which this same site serves. We will publish each key on a keys page with the dates it is valid, and when a key is replaced, the old one will stay listed with its end date, so old records still check.2

The Register

The Register is our record log, with an entry for every event in every job: order paid, control proved, change applied, test passed, reviewer signed, record issued. Each entry carries the fingerprint of the entry before it. So the entries form a chain. If anyone removed or edited an old entry, every fingerprint after it would stop matching.

The chain holds fingerprints only. Your domain, your files and your personal details sit in a separate store that can be deleted.10 Is your data used to train AI? No, unless you tick a consent box that allows it.

Daily root

At 00:05 UTC each day, a job will combine all of the day's entries for each client into one code, then combine all of those into one code for the whole firm.11 That last code is the daily root. It is a single fingerprint of everything sealed that day. We publish only that one code. It reveals nothing about any client.

When the check runs, your browser walks from your record up to the daily root the file carries, and checks that root's signature. If the path leads exactly to that root, your record was part of that day. Once roots are published and anchored, the same root can also be matched against the published copy.12

Anchors

A root we publish on our own site could, in theory, be swapped by us later. So each day's root will also be copied to places outside our control:

  • OpenTimestamps, a free public service that ties the root into the Bitcoin ledger, a public record that is very hard to change after the fact. No coin is bought, sold or held; only the code is written;
  • a public GitHub commit, dated by GitHub;3
  • later, an independent timestamp service under the RFC 3161 standard, and storage that cannot be overwritten, even by us, for a set time.13

The verify page will list each anchor for the day, with a link.

Seal

A record is sealed when it has been signed, written into the Register, and included in a daily root that has been anchored. Sealed does not mean secret. It means fixed in time. From that day on, the record can be checked, and any change to it would show.

Witnesses

A witness is a second party that keeps its own copy of each daily root and signs it. If we ever showed two different roots for one day, the witness copy would expose it. We start with a witness on our own separate cloud account, then add partner witnesses as partners agree.14

What a check does not tell you

A record is only as good as the tests written on it. So be clear about the limits.

  • It does not prove the tests were the right ones for your case. Read the list of tests on the record. Each test has a version, and the test text is published.
  • It does not tell you the domain is still in good shape today. The record shows the state on the day it was sealed. Our rechecks at 30, 90 and 365 days, and Domain Watch, our monthly watch on a domain (not on sale yet), cover what happens after. Recheck results are shown only to the verified owner and the partner who ordered the unit.
  • It is our own record. The verify page is run by Marsadel. It is not a neutral party, and it says so on every page.

Each record also shows

  • Unit origin: whether the unit was run for a client, on our own domain, or on a test domain. Own and test runs are counted apart and are not mixed into client numbers.
  • Continuous sealed history since: the first day of the Register with no gap. A gap would show.
  • Witness count: how many parties signed that day's root.

Checking without our website

You should not have to rely on our own page to check our own record. You can download the record, the day's root and our public keys, and check them against the public anchors yourself. We plan to publish a small offline checking tool and its test files under an open format called Proof of Fix.15

Machine readable

Software agents can call the same check. The verify call takes a record id or fingerprint and returns the result.16

Not yet in place16
  1. 1second model vendor connected; two contracted reviewers, target Mon 30 Nov 2026
  2. 2signing key created and listed on /keys
  3. 3daily root and both anchors (OpenTimestamps, public GitHub commit) running, planned from the week of 23 Nov 2026
  4. 4public per record verify lookup, roots and keys pages live on marsadel.com
  5. 5production signing key created in a key service; first daily root anchored outside the firm, target the week of 23 Nov 2026
  6. 6daily anchors running
  7. 7a page and a printed code for each record
  8. 8keys page and published daily roots live on marsadel.com
  9. 9retention rule checked against the 365 day recheck, which falls after 12 months; rule confirmed before the first paid order
  10. 10per client salts checked in the record log before the first client record
  11. 11daily root job running, planned from the week of 23 Nov 2026
  12. 12daily roots published on marsadel.com and anchored outside the firm
  13. 13RFC 3161 timestamps and write once storage live
  14. 14own second cloud witness running; first partner witness signed
  15. 15offline verifier and Proof of Fix profile published, planned Feb 2027
  16. 16verify_record tool and openapi.json live

Each item is also marked where it stands on this page.