WHY YOU CAN TRUST IT

TRUST

A signed Moonmark is proof anyone can check for themselves, without taking Moon's word for it. Here are the keys, why a signature can't be faked, what Moon promises, and how it stays strong as cryptography changes.

01

THE KEYS

Every signed Moonmark is signed with Moon's key and carries a value from a public beacon Moon doesn't control. Both public keys are below. They're all anyone needs to check a receipt.

MOON'S SIGNING KEYSACTIVE
KEY ID8efd3211b23533ed
ALGORITHMEd25519
PUBLIC KEY5jDbxW9WcpFMgLIjmu0QKtaDpzHzh1MqcNFCR3levJ0
THE BEACON MOON USESNOT MOON'S

drand is public randomness run by the League of Entropy, a group of independent organizations including Cloudflare and Protocol Labs. A new value every 3 seconds that no one can predict, signed with the group's key below. Moon doesn't run it and can't fake it.

NETWORKdrand quicknet
NEW VALUEEvery 3 seconds
SIGNATURESBLS12-381
PUBLIC KEY83cf0f2896adee7eb8b5f01fcad3912212c437e0073e911fb90022d3e760183c8c4b450b6a0a6c3ac6a5776a2d1064510d1fec758c921cc22b0e17e63aaf4bcb5ed66304de9cf809bd274ca73bab4af5a6e9c76a4bc09e76eae8991ef5ece45a
MOON'S TIMESTAMP AUTHORITYRFC 3161

PDF signing tools, code signing and Content Credentials can timestamp with Moon at api.moon369.org/v1/tsa. To trust those timestamps, add Moon's root certificate to the tool. The revocation list lets a document checked decades from now confirm the timestamp certificate was never revoked.

ROOT CERTIFICATEmoon-root.cer · PEM
ROOT SHA-2564B:B0:02:FD:4F:1F:37:59:97:12:D5:29:89:D7:40:44:5B:25:18:C1:12:D8:1C:39:A5:DA:B3:20:0B:C4:7F:D7
TIMESTAMP CERTIFICATEmoon-tsa.pem · with root
REVOCATION LISTmoon-root.crl · nothing revoked · renewed yearly
VALID UNTILRoot 2051 · timestamp certificate 2046
02

WHY IT CAN'T BE FAKED

A signature is math, not a promise. Here is what makes it hold.

Only Moon can sign

Signing needs Moon's private keys, which no one else has. Every receipt carries two signatures, Ed25519 and ML-DSA-65, NIST's post-quantum standard, so forging one means breaking both.

Change one bit, it breaks

The signature covers the file's fingerprint, the exact moment and the key together. Edit any of them and the check fails.

Can't be signed early

Every receipt includes the latest value from drand, a public randomness beacon run by the League of Entropy. No one can know it in advance, so a receipt provably wasn't signed before it.

Nothing hidden

The signing and checking code is open source on GitHub. Anyone can read exactly what a signature means and how it's made.

03

WHAT IT PROVES

A signed Moonmark is precise about what it says. That's what makes it strong.

IT PROVES

This exact file existed by the Moonmark, and the receipt was signed after the drand round inside it. Every receipt sits in a window a few seconds wide, bounded on both sides. Change a single pixel or character and the proof no longer matches.

IT DOES NOT PROVE

Who made the file, or that it's original. Pair a signed Moonmark with your name, your account or your contract for that.

04

VERIFY ONE THREE WAYS

The same answer every way. The third needs nothing from Moon at all.

01 · WEBSITE
Open the link

Every signed Moonmark has a link. Open it and Moon checks the signature in front of you. Drop in the file to confirm it's the exact one that was signed.

Sign a file to try it →
02 · API
Ask Moon

Send the receipt to /v1/verify. Add the file's fingerprint and Moon also confirms it matches.

curl -X POST https://api.moon369.org/v1/verify \
  -d '{"receipt": {...}}'
# { "valid": true, ... }
03 · OFFLINE
Check it yourself

With the public key, anyone can check a receipt on their own machine. No Moon servers, no network, no trust in Moon's word.

import { verify } from 'moon369';
await verify(receipt, { content: file });
// { valid: true, ... }
05

MOON'S PROMISES

What you can rely on, for every receipt Moon has ever signed.

Receipts never expire

If Moon ever moves to a new key, the old one stays published as retired, so every receipt it signed keeps checking.

Changes are public

Any new key is listed at /v1/keys and announced before it signs anything.

Your file stays yours

Moon only ever receives a fingerprint. It can't see, store or rebuild your file from it.

Checking is free, forever

Verifying a signed Moonmark costs nothing, needs no account, and works offline.

06

BUILT TO UPGRADE

Cryptography ages. Quantum computers will one day break the signatures most of the internet uses today. Moon is designed to upgrade its cryptography without breaking anything it has already signed. How Moon is quantum ready.

Two signatures today

Every receipt is signed twice over the same bytes: Ed25519, today's standard, and ML-DSA-65, NIST's post-quantum standard (FIPS 204). A receipt counts only when both check out, so forging one means breaking both.

Every receipt names its method

Each receipt starts with its version, like moonmark-receipt/3. That tells anyone exactly how to check it, so Moon can adopt new cryptography without breaking a single old receipt.

Old receipts keep working

Every version Moon has ever issued stays verifiable. Retired keys stay published, and checkers accept every past version.

Re-sealed over time

Send any receipt to POST /v1/reseal and Moon signs it again with today's algorithms and logs it on the Tideline. Re-seal again as algorithms change, and a receipt from 2026 stays provable in 2056. How.

07

THE KEY PROMISE

A signed Moonmark is only as good as the key behind it. These are Moon's commitments about its signing keys, for anyone who relies on a receipt years from now.

Every key, published forever

Every public key Moon has ever signed with stays published, here and at /v1/keys, marked active or retired. A key is never removed, so every receipt it signed can always be checked.

Retired keys never sign again

When a key is retired it stops signing for good. Receipts it signed before stay valid, and checkers keep accepting them.

Changes announced ahead

Moon announces a planned key change on this page and in the API at least 30 days before it happens, with the date the new key takes over.

If a key is ever exposed

Moon retires it at once and publishes the time it believes the key was exposed. Receipts signed before then, with their drand beacon and their place in the Tideline, remain evidence of when they were made.

Keys stay secret

Moon's private keys are kept as encrypted secrets on its servers. They never appear in its public code, its logs or its answers.

Two algorithms at once

Receipts are signed with Ed25519 and ML-DSA-65 together, so one weakened algorithm is not enough to forge a receipt. When either is retired, the other carries on while a replacement is added.

Questions about a key, or a report that one may be exposed: moon369org@proton.me.

08

STILL LOCKED TO THE MOON

Moon divides time into equal lunations, each as long as the average lunar month. The real Moon runs a little fast or slow from month to month, because its orbit is an ellipse tugged by the Sun. That wobble is expected. Moon would only be drifting if the average gap moved over the years.

EACH REAL NEW MOON MINUS MOON'S GRID, 1900 TO 2100

Could not reach Moon.

THE AVERAGE, CENTURY BY CENTURY, 2000 BCE TO 3000 CE

Could not reach Moon.

Loading the Moon's new moons…

Real new moons from Meeus, Astronomical Algorithms, chapter 49, checked against every solar eclipse from 1000 to 3000. The same test runs with every change to Moon, and fails if the average ever drifts. Data: /v1/drift.

SIGN SOMETHING

Choose a file and get a signed Moonmark in seconds. Your file never leaves your device.

TRY IT