Hetzner

What Is Hetzner?

Hetzner is a German hosting company that provides cloud servers, dedicated servers, colocation, and related infrastructure, and it is widely known for delivering strong performance at notably low prices. Founded in 1997 and headquartered in Gunzenhausen, Germany, Hetzner operates its own data centers in Germany and Finland and has expanded its cloud offering to additional regions, building a large following among developers, startups, and cost-conscious teams across Europe and beyond.

Hetzner's reputation rests on a simple proposition: capable, reliable infrastructure at a fraction of the cost of the large hyperscale clouds. Where providers like AWS and Google Cloud compete on breadth of managed services, Hetzner competes primarily on raw value, offering generous CPU, memory, bandwidth, and storage allocations for the money. This has made it a favorite for anyone running self-managed workloads who does not need the vast managed-service catalog of the hyperscalers and would rather not pay hyperscaler prices.

It is important to position Hetzner correctly. Hetzner is closer to infrastructure-as-a-service and bare-metal hosting than to a fully managed platform-as-a-service. When you use Hetzner Cloud, you get a virtual machine (a "cloud server") with an operating system, and you are responsible for configuring the web server, runtime, database, and security yourself. When you rent a dedicated server, you get an entire physical machine. This is powerful and economical, but it assumes you are comfortable administering Linux and the rest of your stack, which is a different audience from shared-hosting or PaaS customers.

Hetzner is not a browser extension, a CDN, or a website builder. It is the underlying place where servers physically run, identifiable from the outside primarily through the IP addresses and reverse-DNS records of its network. When you detect Hetzner behind a site, you are identifying the data center and network that ultimately serve the application, which is exactly the kind of infrastructure insight a server-side URL analysis is built to surface. Our guide on how to find out where a website is hosted describes the general method, and it applies cleanly to IaaS providers like Hetzner.

How Hetzner Works

Hetzner's product line spans several layers of the hosting stack. Hetzner Cloud provides on-demand virtual servers billed by the hour or month, created in seconds through a web console, an API, or infrastructure-as-code tools. Each cloud server is a Linux (or Windows) virtual machine with dedicated vCPU and RAM options, attachable block storage (volumes), private networks, floating IPs, snapshots, and firewalls. This is the modern, elastic part of Hetzner's catalog and the part most comparable to other cloud providers, though deliberately leaner.

Dedicated servers are physical machines rented in full, offering maximum performance and isolation for workloads that justify a whole box. Hetzner's server-auction marketplace lets customers rent older hardware at steep discounts, which is part of why the company is associated with exceptional price-to-performance. Colocation rounds out the offering for organizations that own hardware and need rack space, power, and connectivity in Hetzner's data centers.

Because Hetzner is infrastructure rather than a managed platform, the application stack lives entirely in the customer's hands. After provisioning a server, you install and configure the web server (commonly Nginx or Apache), the application runtime, and the database. You manage operating-system updates, TLS certificates, firewalls, and monitoring. Many teams layer a control panel, a container orchestrator, or an automation tool on top to make this more manageable, but none of that is imposed by Hetzner itself.

Networking and storage are central to the value story. Hetzner provides generous included bandwidth, IPv4 and IPv6 addressing, private networking between servers, and load balancers for distributing traffic across multiple machines. Object storage and block volumes handle persistent data. Crucially, all of this runs inside Hetzner's own autonomous network, which means the public IP addresses assigned to Hetzner servers fall within Hetzner's registered IP ranges, a fact that becomes the single most reliable way to detect the provider from the outside.

A useful way to picture a typical Hetzner deployment is to follow a small team setting one up. They create a cloud server in the console, choosing a region and a machine size. They SSH in, install Nginx and their application runtime, point a domain's DNS A record at the server's IP, and obtain a TLS certificate. As traffic grows they might add a second server and a Hetzner load balancer in front, or move to a larger machine. Throughout, they own every layer above the bare virtual machine. That hands-on model is why Hetzner appeals to engineers who want control and value, and why it looks so different from a one-click managed host. For the server-software side of that stack, our guide on how to find out what server software a website runs explains how to identify the Nginx or Apache layer that Hetzner customers configure themselves.

How to Tell if a Website Uses Hetzner

Hetzner is an infrastructure provider, so its fingerprints look different from those of a PaaS or a CMS. There is usually no "Hetzner" header or generator tag; instead, the decisive signal is the network the site's IP address belongs to. StackOptic resolves a URL to its IP and inspects ownership server-side, and you can reproduce that analysis manually.

IP ownership and reverse DNS. This is the strongest signal. Resolve the domain to its IP, then look up who owns that IP. Hetzner servers sit in IP ranges registered to Hetzner Online (within the AS24940 autonomous system), and reverse-DNS records frequently resolve to Hetzner-style hostnames such as static.<ip>.clients.your-server.de or *.your-cloud.host. A WHOIS lookup on the IP that returns Hetzner is close to definitive.

Data-center geography. Hetzner's primary locations are in Germany (Nuremberg, Falkenstein) and Finland (Helsinki). An IP that geolocates to those facilities and belongs to Hetzner's network reinforces the conclusion.

Absence of CDN/PaaS signals plus a direct origin. When a domain's A record points straight at a single IP in Hetzner's range, with no intervening CDN headers, you are very likely talking directly to a Hetzner-hosted origin. The self-managed web server (often Nginx or Apache) sits on that machine.

Here is how to check each signal yourself:

Method	What to do	What Hetzner reveals
dig / nslookup	Run dig example.com +short to get the IP	The origin IP address to investigate
whois (IP)	Run whois <ip-address>	Ownership listed as Hetzner Online / AS24940
Reverse DNS	Run dig -x <ip-address>	Hostnames like *.clients.your-server.de
curl -I	Run curl -I https://example.com	The web server (Nginx/Apache) the customer configured
BuiltWith	Look up the domain	Hosting attributed to Hetzner where IP data is available

A fast workflow is dig example.com +short to get the IP, then whois that IP and run dig -x for reverse DNS. If ownership comes back as Hetzner, you have your answer. For a step-by-step treatment, see how to find out where a website is hosted, and to identify the web server running on the Hetzner box, how to find out what server software a website runs is the natural follow-up.

The major caveat is the same one that applies to all origin hosting: a CDN or reverse proxy in front of the site will mask Hetzner entirely. If a domain sits behind Cloudflare, Fastly, or a similar edge network, dig returns the CDN's IP addresses, not Hetzner's, and the response headers reflect the CDN rather than the origin. In that common arrangement, external analysis can confidently identify the CDN but cannot see through it to a Hetzner origin without an unproxied subdomain or other leak. This is why infrastructure detection is fundamentally about IP ownership and why it is most reliable for sites that expose their origin directly. When the origin is visible, Hetzner is one of the easier providers to confirm because its IP ranges and reverse-DNS conventions are so distinctive; when it is hidden behind a CDN, no external tool can pierce a correctly configured proxy with certainty. To learn what a CDN layer does and why it obscures the origin, our explainer on what a CDN is and whether you need one is a helpful companion.

Key Features

• Hetzner Cloud servers. On-demand Linux/Windows VMs with hourly or monthly billing, created in seconds via console, API, or infrastructure-as-code.
• Dedicated servers and auctions. Full physical machines, including discounted older hardware through the server-auction marketplace, for maximum performance per euro.
• Generous bandwidth and storage. Large included traffic allowances, block volumes, and object storage at low cost.
• Networking primitives. Private networks, floating IPs, load balancers, firewalls, and dual-stack IPv4/IPv6.
• Own data centers. Facilities in Germany and Finland operated by Hetzner itself, with EU data-residency appeal.
• API and automation. A clean cloud API plus first-class support for Terraform and similar tools.
• Snapshots and backups. Image-based snapshots and scheduled backups for cloud servers.

Pros and Cons

Pros

• Outstanding price-to-performance, often dramatically cheaper than hyperscale clouds for comparable compute.
• Full control over the server and stack, ideal for engineers who want to self-manage.
• EU-based data centers that appeal to organizations with European data-residency needs.
• A clean API and strong infrastructure-as-code support for automated provisioning.

Cons

• Far fewer managed services than AWS, Google Cloud, or Azure, so you assemble more yourself.
• You are responsible for security, patching, and operations, which assumes Linux expertise.
• A smaller global region footprint than the hyperscalers, concentrated in Europe.
• No built-in PaaS abstraction, so getting an app live takes more setup than a one-click host.

Hetzner vs Alternatives

Hetzner competes on the infrastructure tier, where the choice is mostly about price, control, and managed-service breadth. The table clarifies where it fits.

Provider	Model	Managed services	Standout strength
Hetzner	IaaS + dedicated/colocation	Minimal	Exceptional price-to-performance, EU data centers
AWS	Hyperscale cloud (IaaS/PaaS)	Vast	Breadth, global reach, enterprise ecosystem
Google Cloud	Hyperscale cloud	Vast	Data, ML, and global network strengths
DigitalOcean	Developer-friendly IaaS + apps	Moderate	Simplicity with a gentle learning curve
Azure	Hyperscale cloud	Vast	Enterprise and Microsoft-stack integration

If a site needs the deep managed-service catalog Hetzner deliberately omits, the hyperscalers fill that gap; compare with AWS, Google Cloud, or Azure. For a closer match in spirit, a developer-friendly IaaS like DigitalOcean sits between Hetzner's bare-metal value and a fully managed platform, and the PaaS-style Heroku in this set shows the opposite end of the management spectrum.

Use Cases

Hetzner is the natural choice for teams that want serious compute at a low price and are comfortable managing their own servers. Developers and startups run application backends, databases, and web servers on Hetzner Cloud, scaling vertically or adding machines as needed while keeping infrastructure costs predictable and low.

It also suits self-hosting enthusiasts running everything from game servers to private cloud applications, companies with European data-residency requirements that value Hetzner's German and Finnish facilities, and compute-heavy workloads, such as CI runners, rendering, or batch processing, where the price-to-performance ratio matters most. Agencies and consultants frequently provision Hetzner servers for client projects that do not require a hyperscaler's managed services.

Consider a few concrete patterns. A bootstrapped SaaS company might run its entire stack, several Hetzner Cloud servers behind a Hetzner load balancer, plus a managed or self-hosted database, at a monthly cost a fraction of what an equivalent hyperscaler setup would run. A European business bound by data-protection expectations might choose Hetzner specifically so that its data physically resides in Germany. A developer running resource-intensive background jobs might rent a discounted dedicated server from the auction to get many cores cheaply. In each case the organization is trading managed-service convenience for control and cost efficiency.

From a competitive-research standpoint, detecting Hetzner behind a site is a useful signal. It often indicates a technically sophisticated, cost-conscious team that self-manages its infrastructure, frequently a startup, an indie developer, or a European business. For vendors selling monitoring, backups, managed databases, or security tooling, that profile is valuable context, because Hetzner customers assemble those capabilities themselves rather than buying them bundled. Surfacing the hosting provider automatically across many domains, instead of running WHOIS lookups by hand, is precisely the kind of insight automated stack detection delivers.

Frequently Asked Questions

Is Hetzner a cloud provider like AWS?

Partly. Hetzner Cloud is a genuine infrastructure-as-a-service offering with on-demand virtual servers, volumes, networks, and load balancers, comparable to the basic compute layer of AWS. The key difference is breadth: AWS offers hundreds of managed services across databases, analytics, machine learning, and more, while Hetzner focuses on cost-effective core infrastructure. Hetzner also provides dedicated servers and colocation, which positions it closer to traditional bare-metal hosting than the hyperscalers.

How do I tell if a website is hosted on Hetzner?

Resolve the domain to its IP with dig example.com +short, then run whois on that IP and dig -x <ip> for reverse DNS. If WHOIS attributes the IP to Hetzner Online (autonomous system AS24940), or reverse DNS returns hostnames like *.clients.your-server.de, the site is hosted on Hetzner. Note that a CDN in front of the site will return the CDN's IPs instead, masking the Hetzner origin.

Why is Hetzner so much cheaper than the big clouds?

Hetzner concentrates on efficient, no-frills core infrastructure rather than a sprawling catalog of managed services, operates its own data centers, and offers discounted hardware through its server auctions. It does not bundle the extensive managed databases, analytics, and platform services that hyperscalers charge a premium for. The trade-off is that you take on more operational responsibility, so the lower price reflects a more hands-on, self-managed model.

Does Hetzner host outside Europe?

Hetzner's roots and the bulk of its capacity are in Germany and Finland, which is part of its appeal for European data residency. The company has expanded its cloud regions to additional locations over time, so availability changes; the authoritative source is Hetzner's current region list. For workloads needing many global edge locations, teams often pair a Hetzner origin with a CDN rather than relying on Hetzner's footprint alone.

Can I detect Hetzner if the site uses Cloudflare?

Usually not from the outside. When a site sits behind Cloudflare or another CDN, DNS resolves to the CDN's IP addresses and the response headers reflect the CDN, not the origin. The Hetzner origin is hidden behind the proxy. You might still confirm it through an unproxied subdomain, a DNS record that leaks the origin, or other configuration slips, but a correctly configured proxy prevents external tools from seeing the Hetzner machine directly.

Curious which provider, server, and CDN a given site uses? Analyze any URL with StackOptic at https://stackoptic.com.