Açık anahtarımızı içe aktarın
bitvps-pubkey.asc dosyasını indirin ve gpg --import bitvps-pubkey.asc komutunu çalıştırın
Ne yapmaya zorlanmadığımızı doğrulayan haftalık PGP imzalı bir beyan. Yayınlanan anahtarla her Pazartesi otomatik olarak yeniden imzalanır. Bir olay sonrası raporu olmaksızın geçerliliğini yitirirse önemli bir şeyin değiştiğini varsayın.
Yayınlanan BitVPS anahtarıyla PGP clearsign ile imzalanmış, bire bir metin. İmza aşağıda gördüğünüz tam baytlar üzerinden hesaplanmıştır — kendiniz kopyalayıp gpg --verify ile doğrulayın.
-----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-----
GnuPG yüklü olması gerekir. Tüm işlem yaklaşık on saniye sürer.
bitvps-pubkey.asc dosyasını indirin ve gpg --import bitvps-pubkey.asc komutunu çalıştırın
Anahtar parmak izi 4DCF 5D6D 10AF F2AA 47E2 070E A62A EDAF 647E E3E6 OLMALI. _openpgpkey.bitvps.io DNS ve keys.openpgp.org aracılığıyla çapraz doğrulayın.
İmzalı bloğu kaydedin: curl -o canary.asc https://bitvps.io/canary/current.asc
gpg --verify canary.asc komutunu çalıştırın. Çıktı “Good signature” ve 2. adımdaki parmak izini içermelidir. İçermiyorsa — durdurun ve canary'yi güvenliği ihlal edilmiş olarak değerlendirin.
Geçmişteki her canary indirilebilir. Mevcut hafta en üstte yer alır; takvim ilerledikçe eski haftalar dolar.
| İmzalandı | Hafta | Kapsanan dönem | Alınan DMCA | Alınan siparişler | Susturma kararları | Arşiv |
|---|---|---|---|---|---|---|
| mevcut 2026-07-06 | W28-2026 | 2026-06-29 / 2026-07-05 | 178 | 1 | 0 | henüz değil |
| 2026-06-29 | W27-2026 | 2026-06-22 / 2026-06-28 | 112 | 0 | 0 | henüz değil |
| 2026-06-22 | W26-2026 | 2026-06-15 / 2026-06-21 | 146 | 0 | 0 | henüz değil |
| 2026-06-15 | W25-2026 | 2026-06-08 / 2026-06-14 | 170 | 0 | 0 | henüz değil |
| 2026-06-08 | W24-2026 | 2026-06-01 / 2026-06-07 | 172 | 0 | 0 | henüz değil |
| 2026-06-01 | W23-2026 | 2026-05-25 / 2026-05-31 | 128 | 0 | 0 | henüz değil |
| 2026-05-25 | W22-2026 | 2026-05-18 / 2026-05-24 | 139 | 0 | 0 | .asc |
| 2026-05-18 | W21-2026 | 2026-05-11 / 2026-05-17 | 167 | 1 | 0 | henüz değil |
| 2026-05-11 | W20-2026 | 2026-05-04 / 2026-05-10 | 141 | 0 | 0 | .asc |
| 2026-05-04 | W19-2026 | 2026-04-27 / 2026-05-03 | 187 | 0 | 0 | .asc |
| 2026-04-27 | W18-2026 | 2026-04-20 / 2026-04-26 | 158 | 0 | 0 | .asc |
| 2026-04-20 | W17-2026 | 2026-04-13 / 2026-04-19 | 121 | 0 | 0 | .asc |
“henüz değil” olarak işaretlenen satırlar gelecekteki veya henüz gerçekleşmemiş haftaları temsil eder — her biri o Pazartesiden sonraki ilk sayfa yüklemesinde indirilebilir bir .asc haline gelir.
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.
Canary'nin nasıl çalıştığı, nasıl doğrulanacağı, eksik bir imzanın ne anlama geldiği ve hangi yargı bölgelerini kapsadığı.
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.