Why use a virtual number for Hetzner
Server consoles are high-trust. If OTP is routed to a personal SIM, you risk lockouts during travel, staff changes, or carrier issues. A virtual number for Hetzner supports clearer ownership and a recovery-first workflow.
Benefits
- Team continuity: documented OTP ownership and escalation.
- Reduced lockouts: stable verification across regions.
- Privacy: keep personal SIMs off infrastructure accounts.
Best practices
- Prefer authenticator/passkeys where available; store backup codes securely.
- Run a quarterly recovery drill for the console account.
- Avoid repeated OTP retries and region switching during verification.
Hetzner's signup verification — the strictest in mainstream hosting
Hetzner, the German provider beloved for absurdly good price-performance, runs one of the most aggressive new-account screening processes in the industry. Because its cheap compute is a magnet for abuse, new signups face a risk-scoring gauntlet: phone verification, sometimes a €20 pre-payment, and — for accounts its system distrusts — a request for government ID. Many perfectly legitimate developers get bounced at first attempt. Understanding how the phone step fits into that scoring is the difference between a smooth signup and a frustrating rejection.
Realistic expectations with virtual numbers
- The SMS itself is standard: a one-time code to confirm the number you enter. Virtual numbers receive it normally.
- Coherence beats everything: Hetzner's fraud scoring weighs the whole picture — number country, IP geolocation, billing address, and payment method should tell one consistent story. A German or EU number with an EU address and matching card sails; a mixed bag of countries invites manual review. Pick your number country to match your billing identity, not the other way around.
- If flagged, don't fight the bot: failed signups usually escalate to Hetzner's manual review, which is responsive and human. Replying with genuine details clears legitimate users faster than repeated fresh signup attempts, which look like exactly the abuse pattern they screen for.
After activation
Once through, the phone number's job is done — Hetzner's ongoing security runs on email, password, and TOTP two-factor (enable it in the account settings immediately). Recovery never depends on SMS, so an expired temporary number costs nothing. The durable-account checklist: TOTP on, recovery email confirmed, billing profile accurate, and the server's SSH keys and firewall configured before you put anything real on it. Hetzner's strictness at the door is precisely why its network stays clean and cheap once you're inside.
Setting up Hetzner access for a team rather than one person
The phone number is rarely the long-term risk with Hetzner. The bigger problem is a console account that belongs, in practice, to whoever signed up, with the TOTP secret on their personal phone. When that person is away or leaves, the team discovers it cannot reach its own servers.
A sturdier arrangement:
Once a quarter, run a recovery drill: a second team member signs in from a clean device using only the shared vault. If that fails, fix it while nothing is on fire. Note how long it took and what was missing.
Also agree what happens with the phone number used at signup. If it was a short-term rental, write that down, so nobody later assumes it can receive a code. Day-to-day security does not depend on it, but future support conversations might ask what number is on file.
- Register the account with a role address on your company domain, such as an infrastructure mailbox, not a personal email.
- Store the account password and TOTP seed in a shared team password manager, so at least two people can generate codes.
- Use Hetzner's project and member features to give colleagues their own logins with appropriate permissions, instead of sharing the main account.
- Keep SSH keys per person and remove them when someone leaves, rather than sharing one key.
- Record the billing contact, payment method owner and the date TOTP was last checked.
Lawful SMS verification only. Follow each platform’s terms. Ucode is not for bulk account farming or ban evasion.
Key takeaways
- Coherence counts: align number country, billing address, payment method and IP.
- Work with review: honest replies clear a flagged signup faster than new attempts.
- Secure early: turn on TOTP and confirm the recovery email before deploying servers.
In short
Hetzner screens new accounts closely, and the phone check is one signal among several. Use a number consistent with your real billing details, cooperate with manual review if flagged, and protect the active account with TOTP, a confirmed email and properly configured servers.
