Warrant Canary

Q: How do I verify the PGP signature?

Fetch our master public key from /pgp/, import it with gpg --import, confirm the fingerprint matches the one published on this page, then run gpg --verify canary.asc against the clearsigned text above. The output must contain “Good signature” and the matching fingerprint — anything else means the canary is invalid.

Eine wöchentliche PGP-signierte Erklärung, die bestätigt, wozu wir nicht gezwungen wurden. Automatisch jeden Montag mit dem veröffentlichten Schlüssel neu signiert. Falls sie veraltet, ohne dass ein entsprechendes Incident-Post-Mortem vorliegt, ist davon auszugehen, dass sich etwas Wesentliches geändert hat.

Canary ist aktuell. Vor 6 Tags signiert · nächste Signierung in 6d Tag6s · Veralterungsschwelle in sd Tagen.

Signiert 2026-07-06 Woche W28-2026 Schlüssel 0xA62AEDAF647EE3E6

Aktuell signierte Erklärung

Wortgetreu, PGP-clearsigned mit dem veröffentlichten BitVPS-Schlüssel. Die Signatur wird über genau die Bytes berechnet, die du unten siehst — kopiere sie und gpg --verify sie selbst.

Signiert 2026-07-06 · Woche W28-2026 · Schlüssel 0xA62AEDAF647EE3E6

.asc herunterladen Öffentlicher Schlüssel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

BitVPS Ltd — Warrant Canary
Week  : W17-2026
Signed: 2026-04-20 (Monday)
Period: 2026-04-13 through 2026-04-19 inclusive (UTC)

STATEMENTS

1. BitVPS Ltd has NOT received, as of the date of this signing:
   - any National Security Letter from any jurisdiction;
   - any gag order or prior-restraint order from any jurisdiction;
   - any bulk-metadata retention or bulk-surveillance order from any jurisdiction;
   - any order requiring BGP route injection, DNS hijack, or active tampering with
     customer traffic;
   - any request to install surveillance equipment or to provide a backdoor into
     our hypervisor, control panel, billing, or support systems.

2. BitVPS Ltd has NOT been compelled to transfer ownership or operational
   control of any Infrastructure to any third party.

3. BitVPS Ltd's signing key (the key whose fingerprint appears on the
   published signature below) remains in the sole custody of the original two
   founding engineers, unmodified, and has NOT been replaced, compromised or
   surrendered since its publication on 2026-04-22.

AGGREGATE REPORTING (period 2026-04-13 to 2026-04-19 UTC)

- - DMCA-style take-down notices received .............. 147
- - DMCA-style take-down notices actioned ..............   0    (see /dmca)
- - Court orders received (Saint Kitts and Nevis) ......   0
- - Court orders received (Iceland) ....................   0
- - Court orders received (Netherlands) ................   1
- - Court orders received (Romania) ....................   0
- - Court orders received (Switzerland) ................   0
- - Court orders complied with .........................   1    (narrow scope)
- - Abuse reports received (all categories) ............ 312
- - Abuse reports actioned .............................  28    (see /abuse)

NEXT SIGNING

This canary is renewed every Monday. The next signing is scheduled for
2026-04-27. If no successor signature has appeared by 2026-05-04 (14 days after
this one) and no publicly-announced infrastructure incident explains the delay,
assume something material has changed and act accordingly.

The current public key is fingerprint:
  4DCF 5D6D 10AF F2AA 47E2  070E A62A EDAF 647E E3E6

Archived signed statements are available under /canary/archive/.

- -- BitVPS Ltd
   [email protected]
   Charlestown, Saint Kitts and Nevis
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQRNz11tEK/yqkfiBw6mKu2vZH7j5gUCaemx3QAKCRCmKu2vZH7j
5g5EAP468WfyWd0bnmPFdZq0YCDVvUpDUa2cgANJ8AneBTVDmgD+OhdZmbaolYUo
Xe8pqjxWTn6XAO5iJa9LoO7BBy6agg4=
=+4fd
-----END PGP SIGNATURE-----

So geht's: verifizieren

Du brauchst GnuPG installiert. Der ganze Vorgang dauert etwa zehn Sekunden.

Unseren öffentlichen Schlüssel importieren

Laden Sie bitvps-pubkey.asc herunter und führen Sie gpg --import bitvps-pubkey.asc aus

Fingerabdruck bestätigen

Der Schlüssel-Fingerabdruck MUSS 4DCF 5D6D 10AF F2AA 47E2 070E A62A EDAF 647E E3E6 sein. Gegenkontrolle über _openpgpkey.bitvps.io-DNS und keys.openpgp.org.

Den Canary herunterladen

Speichern Sie den signierten Block: curl -o canary.asc https://bitvps.io/canary/current.asc

Signatur verifizieren

Führen Sie gpg --verify canary.asc aus. Die Ausgabe muss “Good signature” und den Fingerabdruck aus Schritt 2 enthalten. Andernfalls — stoppen Sie und behandeln Sie den Canary als kompromittiert.

Frühere Signierungen

Jeder vergangene Canary ist herunterladbar. Die aktuelle Woche steht oben; ältere Wochen füllen sich auf, wenn der Kalender voranschreitet.

Signiert	Woche	Abgedeckter Zeitraum	DMCA eingegangen	Bestellungen eingegangen	Archiv
aktuell 2026-07-06	W28-2026	2026-06-29 / 2026-07-05	178	1	noch nicht
2026-06-29	W27-2026	2026-06-22 / 2026-06-28	112	0	noch nicht
2026-06-22	W26-2026	2026-06-15 / 2026-06-21	146	0	noch nicht
2026-06-15	W25-2026	2026-06-08 / 2026-06-14	170	0	noch nicht
2026-06-08	W24-2026	2026-06-01 / 2026-06-07	172	0	noch nicht
2026-06-01	W23-2026	2026-05-25 / 2026-05-31	128	0	noch nicht
2026-05-25	W22-2026	2026-05-18 / 2026-05-24	139	0	.asc
2026-05-18	W21-2026	2026-05-11 / 2026-05-17	167	1	noch nicht
2026-05-11	W20-2026	2026-05-04 / 2026-05-10	141	0	.asc
2026-05-04	W19-2026	2026-04-27 / 2026-05-03	187	0	.asc
2026-04-27	W18-2026	2026-04-20 / 2026-04-26	158	0	.asc
2026-04-20	W17-2026	2026-04-13 / 2026-04-19	121	0	.asc

Mit “noch nicht” markierte Zeilen sind zukünftige oder noch nicht eingetretene Wochen — jede wird beim ersten Seitenaufruf nach dem jeweiligen Montag zu einem herunterladbaren .asc.

Warum wir das veröffentlichen

A warrant canary is not a cryptographic proof of anything positive — it is a ritual of negative disclosure. In jurisdictions where a legal order can compel a provider not to speak about the order itself, the order cannot compel the provider to continue to publish a signed statement that the order has not occurred. The absence of the expected signature therefore communicates information that the issuing authority cannot lawfully block.

Our canary is renewed every Monday. If the W28-2026 signing is not followed by a 2026-07-13 signing (or a same-week infrastructure-incident post-mortem on /status that explains the delay), the reasonable inference after 2026-07-20 is that BitVPS Ltd has received a category of order described above and has been compelled to remain silent about it. You should then migrate away, rotate credentials, and treat our infrastructure as hostile until the canary returns with a fresh post-mortem.

This document is governed by the Terms of Service and the operational policies at /privacy, /abuse, and /dmca. It is not legal advice; it is an operational signal.

Warrant Canary FAQ

Wie der Canary funktioniert, wie man ihn verifiziert, was eine fehlende Signatur bedeutet und welche Jurisdiktionen er abdeckt.

Was ist ein Warrant Canary?

A warrant canary is a routinely published statement asserting that the publisher has not received certain classes of secret legal process — typically a National Security Letter, a gag-bound subpoena, or a bulk-surveillance order. If the statement disappears or fails to renew, the inference is that such an order has been received and the publisher has been compelled to remain silent about it.

What does a missing canary mean?

If the canary is more than seven days late and there is no infrastructure post-mortem on /status explaining the delay, treat BitVPS as compromised: migrate workloads, rotate credentials and assume any data on our infrastructure is at risk. Latency alone is not proof of compulsion, but it is the only signal we are legally able to give.

How do I verify the PGP signature?

Fetch our master public key from /pgp/, import it with gpg --import, confirm the fingerprint matches the one published on this page, then run gpg --verify canary.asc against the clearsigned text above. The output must contain “Good signature” and the matching fingerprint — anything else means the canary is invalid.

Why weekly and not daily?

Weekly cadence balances signal freshness against operational risk: signing requires a human operator to physically reach an offline keystore. Daily signing increases the chance of a benign miss (travel, illness, hardware failure) being misread as compulsion. Seven days gives readers a clear staleness threshold while keeping the signing ritual sustainable.

Has the canary ever been late?

No. Every weekly signing since the canary was established has been published on schedule with a valid PGP signature. The full archive is available below — each entry is independently verifiable against the public key, and historical signings remain on the site permanently so the chain cannot be silently rewritten.

What jurisdictions does this canary cover?

The canary covers BitVPS Ltd. and its operating subsidiaries in every jurisdiction where we hold infrastructure: Iceland, the Netherlands, Romania and Switzerland. It explicitly disclaims receipt of any National Security Letter, gag order, bulk-surveillance order or equivalent compelled-silence instrument from any government in those jurisdictions or their mutual legal assistance partners.