cryptoservers.io

Talk to the humans

Eight role-specific inboxes, staffed by the engineers and operators running the infrastructure — not by an outsourced helpdesk. PGP-signed replies for anything sensitive; our public key is published and cross-verifiable.

First response < 15 min · T1 PGP-signed No-KYC support EN · FR

Open a ticket

Pick the inbox on the left, compose on the right. Your reply-to is the only thing we route on — no account required.

Technical support

[email protected]
< 15 min · T1
public-key.asc
ASCII-armored We verify the fingerprint against your next signed reply before the first encrypt. Leave empty for an un-encrypted response.
Reply comes from [email protected], signed with our PGP key. We never share reply addresses with third parties.

Registered office and encryption

Legal paperwork goes to a real, published address. Sensitive mail goes through our PGP key — the same one we use to sign our warrant canary.

Registered office

Cryptoservers Ltd.
PO Box 556
Charlestown, Nevis
KN-1 4321
Federation of Saint Kitts and Nevis
Company registration
C 59284-2024
Jurisdiction
Saint Kitts and Nevis
Incorporation
2024-01-12

Encrypt sensitive mail

For anything involving credentials, identifiable persons, legal claims or security vulnerabilities, please encrypt with our published PGP key. Fingerprint:
4DCF 5D6D 10AF F2AA 47E2 070E A62A EDAF 647E E3E6

Verify the key against four independent channels — see the PGP key page. Our replies are signed with the same key so you can confirm authenticity.

Not getting a reply? Escalate.

If we miss our stated SLA, this is how to punch through the queue — in order.

Escalation ladder

  1. Reply to your existing ticket with ESCALATE — over SLA. A senior engineer sees it at the next queue sweep (every 15 min, business hours).
  2. Email [email protected] with the ticket ID. Reaches the on-call manager; acknowledged within < 1 h, 24/7.
  3. Network-wide incident? Page our NOC at [email protected]. Adds the on-duty network engineer; cc security@ if adjacent.
  4. Unreachable altogether? Check /status for an infrastructure incident. As a last resort, the weekly warrant canary is an out-of-band sign of life.

No support phone number — by design. Voice calls make bad audit trails, don't enforce identity verification, and encourage social engineering. Every exchange with us is written, and — for anything sensitive — PGP-signed.