Onyx Mail Warrant Canary

A periodic PGP-clearsigned statement. Trust state is current only when the artifact is present, within its validity period, signed, and linked to a valid canonical hash-chain state.

Trust State

Current

Fail-closed canonical assessment

Validity Window

27 days

Next update: 2026-11-21

Signing Key

F60C F128 EE34 35F9 A4D5 3850 3421 FCA1 7ADF 0933

Compare all 40 hexadecimal characters

Recent Hash-Chain Records

The latest five rotation records are shown. Local PGP verification of the clearsigned artifact remains the authoritative user procedure.

Rotation Ledger

Most recent record first
#182026-10-2200:00:01 UTCrotation
Current record
Key ID:3421FCA17ADF0933
Hash:f6a6e41f319360761e418a3ce5e06775...
Previous:5cdfddc0b61d72bae9f59ce4ea945f60...

Exact Current Clearsigned Artifact

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Onyx Mail Warrant Canary
========================
Status Date: 2026-10-22 00:00:01 UTC
Next Update: 2026-11-21
Rotation: 13

As of October 22, 2026, Onyx Mail affirms:

1. We have received 0 National Security Letters
2. We have received 0 FISA court orders
3. We have received 0 gag orders preventing disclosure
4. We have received 0 law enforcement data requests
5. No backdoors have been installed in our systems
6. We maintain full control of our infrastructure

This statement will be updated monthly.
Absence of update should be considered a dead canary.

VERIFICATION DATA:
Signing Key: 7ADF0933
Current Hash: 284b8725f113aff3
Previous Hash: 5cdfddc0b61d72ba
Chain Position: 13 of 13

Contact: [email protected]
Timestamp: 1792627201
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE3KS/uLAo5zWWQhD/i7SThF7ReqwFAmrZUgEACgkQi7SThF7R
eqyHnQ//V+w8lbIZzWQ7X2HQI4p8PWupzOOk5omgpSN3C+eT9nTeFKz4hwxrJlKN
iSHWK0J2VO2K1eDWs2UdwZRlxYfnzC//jWqnWPSqdF/B1k7ssogfpM8udlu663U5
1a801+kaTsBHxRu+bDTNGC7GvanlBd6obqfOEisyBISWG1sVoMvX+hbCbgSXZhxS
5OcVxDsEpx4RPhLSAWEWl0vs1vhfWbRcjquvfsWS9fmBFHkgABBzH7nprSTM6adO
Cm39136REzgjx748wOKn/o49uuEs4d7jyYSkCcziBGeRouRTPhe7+FtBztrMi08Z
mz1EAVABeQXT+ffPYGOpeFHMfqtkQX29cQ2FZUFJjflqW+7RiCpjUwInSnk9LPls
nRUMizy1TUWKLNFxQ0d1HclqBihsZhnMpT38BaDxuSxPCmFjh2hHP6Pv0d/fGxLt
qizryBm8TJNgoBZj/alTq6akUnFmevP/P4RU6xZN6k5oM1MaJf2+ZjmyTj9OwdJv
ZP8PCcJShMFqlrTZxe2atB0LTz+Vc8uFzoRtgUu4LCqfJJiXB1nSkX/IZPRJ7Bam
lp/xzSgqJAlplRy5oN8IDgIOeoP0u7vMxEU5pbZfXFwXfet6ButlT+GcDSv/CxWo
qCA7ypWNS2sR3MYq5wiBwQJwamgfFFgmFI9UPZCu5rOztg8vIDs=
=mOcL
-----END PGP SIGNATURE-----

Verify with GnuPG

1

Retrieve the key

curl -fSLo onyxmail-canary-public.asc https://onyxmail.net/canary/public.asc gpg --show-keys --fingerprint onyxmail-canary-public.asc

Compare the complete fingerprint shown above through another trusted path before import.

2

Retrieve the artifact

curl -fSLo current_clearsigned.asc https://onyxmail.net/.well-known/canary/current_clearsigned.asc

Do not alter whitespace or line endings before verification.

3

Verify locally

gpg --import onyxmail-canary-public.asc gpg --verify current_clearsigned.asc

Confirm a good signature from the expected full fingerprint, then inspect the status and next-update dates inside the signed text.