Migrate to RunxBuild today!! Deploy More while Spending Less

Calculate your savings
unxBuild
Back to Blog Explainer

The .hu Domain: Who Can Register Hungary's ccTLD, and What to Set Up After

Sean

Platform Writer

Sep 20, 2026
8 min read

The .hu domain is Hungary’s country-code top-level domain, run by the registry Nic.hu and opened to overseas registrants years ago, so there is no residency requirement to buy one. What still applies is a short trademark priority window when a new name overlaps an existing mark, and the usual registrar-mediated process rather than registering directly with the registry. Once it is yours, a .hu domain does nothing until you set the A/AAAA and CNAME records, add a CAA record, and get a certificate — the part every registrar’s checkout page skips.

The .hu Domain: Who Can Register Hungary's ccTLD, and What to Set Up After

Every top result for this phrase is a registrar’s product page, which is fine for finding a price and unhelpful for understanding what you are actually buying. Hungary’s ccTLD has a couple of real rules worth knowing before you register — the priority window, the registrar-only process — and then a completely generic set of steps once the domain exists that has nothing to do with it being Hungarian. This post covers both halves.

Table of contents

What .hu is and who runs it

.hu is Hungary’s ISO 3166 country-code domain, administered by Nic.hu, the registry operated under the Council of Hungarian Internet Providers. Like most ccTLDs, you do not register directly with the registry — an accredited registrar handles the transaction and pushes your registrant details into the Hungarian zone.

Second-level structure matters here more than with a .com. Alongside plain name.hu registrations, Hungary also runs organizational second-level categories inherited from an older naming convention. For a commercial project, a direct name.hu registration is almost always what you want; the categorized second-level domains are aimed at specific organizational types, not general businesses. Two-letter names are generally reserved, following the pattern most ccTLDs use to keep administrative abbreviations out of general circulation.

The zone itself is DNSSEC-capable, and Hungary has been steadily increasing signed-domain adoption. If you do sign the zone, treat any nameserver change as a two-step process — remove the old DS record, wait out its TTL, move nameservers, then publish the new DS — because a stale DS record does not degrade gracefully; it takes the domain fully offline for anyone behind a validating resolver.

Who can register one, and the priority window

Hungary opened .hu registration to individuals and companies without a residency or local-presence requirement some years ago, which is why the domain shows up on plenty of projects with no Hungarian connection at all. You supply standard registrant contact details through your registrar; there is no separate application to the registry itself. The same open-registration pattern shows up elsewhere — the .ch domain runs a similarly residency-free process with its own registry quirks.

The detail worth knowing before you register a name that might overlap someone’s trademark: Hungary runs a priority claim process for new registrations that match an existing registered mark, giving the trademark holder a window to assert a prior claim before the registration is finalized to anyone else. If your name is generic or already your own brand, this rarely matters. If you are registering a name close to an established mark, expect it to be contested rather than assume first-come, first-served settles it.

Registrars vary on what they collect beyond contact details — some ask for a company registration number if you register as a business entity, which is a registrar convenience rather than a registry mandate. Keep the registrant email current regardless of what is collected, since expiry and transfer notices go there first. Transfers between registrars use the standard authorization-code process; check the lock status before starting one, since a locked domain fails the transfer silently at some registrars.

Renewal price, and the number that actually matters

Like most ccTLDs, .hu pricing has a first-year number and a renewal number, and registrars are more consistent about advertising the first than the second. Compare renewal prices across registrars before committing to multi-year discounts, because the renewal is what you pay every year the domain exists, and the first-year rate is a promotion, not the product.

There is no bundled hosting requirement tied to .hu registration — you can register the name at one registrar and host the site anywhere, which is worth confirming before you buy if a registrar’s checkout tries to bundle a hosting plan by default.

The records that make the domain do anything

A registered .hu domain answers nothing until you create records at whichever DNS provider you point its nameservers to. The minimum set for a website:

  • A or AAAA on the apex, pointing at your host’s address.
  • CNAME on www, pointing at the same target, with a redirect so one form is canonical.
  • CAA, naming the certificate authority allowed to issue for the name, closing the door on anyone else issuing a certificate for it.
  • MX only if you are actually receiving mail on the domain — an MX-less domain with a null SPF record is safer than one left half-configured.

If your DNS provider does not support an ALIAS/ANAME record and your host only gives you a hostname rather than a static IP for the apex, use a redirect from the bare domain to www instead of forcing an A record at the apex — a common workaround for hosts that publish CNAME-style targets. Drop the TTL to a few minutes before a planned change and put it back afterward; that turns a multi-hour propagation wait into a predictable few minutes, since nothing propagates except resolver caches expiring on their own schedule.

Certificates, and the step people forget

A .hu name gets a certificate the same way any other domain does: an ACME challenge proves control of the domain, and a certificate authority issues accordingly. On a managed platform this happens automatically the moment DNS resolves to it. On a server you run yourself, it is a client you install and a renewal timer you are responsible for actually verifying.

The browser warning that shows up months after launch, when a manually managed certificate quietly expires, is the single most common failure mode for domains people configured once and never looked at again. Automated renewal is not a nice-to-have; it is the difference between the domain working in six months or not. Wildcard coverage for subdomains works the same as anywhere else — one certificate covering all of a site’s subdomains, issued through the same ACME flow, rather than a certificate per subdomain.

When .hu is worth it, and when it is a naming tax

The honest case for .hu is a Hungarian audience: it reads as local in a way .com does not, and for a market where that signal matters, it is worth the ccTLD premium most registrars charge over a generic domain.

The weak case is buying it purely because a word or brand ends in the letters h and u for a domain hack — it works, but you are paying a country-code renewal price indefinitely for a pun with no connection to the market. The case nobody makes but should: a .hu domain says nothing about where your server lives or what law governs a request for your logs. Registrant data follows Hungarian and EU rules; your hosting jurisdiction is a completely separate decision, made when you pick where the site actually runs.

How this fits the rest of the stack

A .hu domain is the cheapest, most fixed line in the whole stack; the server, database, storage, and bandwidth behind it are the ones that grow and actually decide the bill. Before committing to a setup, put those together in the RunxBuild hosting calculator so the monthly number is something you chose. Once the domain resolves, custom domains and certificates on RunxBuild covers how the record and the certificate are handled without a renewal timer to babysit, and the dashboard is where you point the record.

Useful related references:

FAQ

Do I need to live in Hungary to register a .hu domain?

No. Hungary opened .hu registration to individuals and companies worldwide, so there is no residency or local-presence requirement. You register through an accredited registrar and supply standard registrant contact details. Some registrars ask for a company registration number if you register as a business, but that is a registrar convenience rather than a registry requirement.

What is the trademark priority window on .hu?

When a new .hu registration matches an existing registered trademark, Hungary’s registry gives the trademark holder a window to assert a prior claim before the registration finalizes to someone else. It rarely comes up for a generic name or your own established brand, but it matters if you are registering a name close to an existing mark.

How much does a .hu domain cost, and why does it renew higher?

Pricing varies by registrar, and like most ccTLDs the renewal price typically sits above the promotional first-year rate. A country-code registry sets its own wholesale price, usually higher than a generic .com. Compare the renewal figure across registrars rather than the headline price, since that is the number you pay every year after the first.

What records do I need to set up after registering a .hu domain?

At minimum: an A or AAAA record on the apex pointing at your host, a CNAME on www, a CAA record naming your certificate authority, and MX records only if you are receiving mail on the domain. None of this is Hungary-specific — it is the same checklist for any domain.

Does a .hu domain help SEO for a Hungarian audience?

A country-code domain is a geotargeting signal, so it can help for Hungarian-intent searches and works against you for queries aimed elsewhere. It is one signal among many — content in Hungarian and a host that answers quickly from the region matter more than the extension itself.

#hu domain#hungarian cctld#domain registration#dns records#point domain at hosting