First, who controls the domain, hosting and website?
If your business has a website, there are at least four separate things to manage: the right to use the domain, the hosting service, the website files and database, and the access permissions and licences. They may appear on a single invoice, but that does not make them the same thing.
With .hu domains, precise language is especially important: you do not 'own' one like a physical asset. Instead, you hold the rights of the registered domain holder under the applicable rules. The registrar is the service provider handling registration. A developer having access to the domain control panel does not prove that your business is the registered holder.
A domain is not hosting
A domain is an address, such as a name ending in .hu. The hosting service provides the infrastructure that serves your website. You can move to another host while keeping the same domain.
Login access is not complete control
A WordPress administrator account lets you edit content, but it does not necessarily provide access to DNS, the server, backups, licences or domain registration details.
The overall aim is simple: your business should not depend entirely on one outside contractor's personal account. An external developer can of course manage these things under contract. What matters is that your business retains the appropriate rights to control and transfer them.
What should be registered to your business for a .hu domain?
Domain holder and registrar: different roles
The domain account, notification email address and renewal process should all be easy to verify. This means your business can still access its website essentials if you change providers.
What happens if you want to switch providers?
Changing registrars, configuring DNS and migrating hosting are separate technical tasks. First, establish exactly what you want to transfer and which permissions are available.
Review the contact details associated with your accounts regularly. An outdated email address could cause you to miss important provider notifications.
Ten-point checklist: who controls what?
Open your contract, domain and hosting invoices, and the list of managed accounts. For each item, record who holds the rights, who pays, who manages it and who can hand over access when you leave. This table shows who needs access to what and which areas you should keep under control.
| Item | Business control | Main risk |
|---|---|---|
| 1. .hu domain | Registered domain holder, known registrar and reachable contact | Only the contractor manages registration |
| 2. Renewal | Named person responsible for expiry and payment, with renewal notifications received | Missed renewal |
| 3. DNS | List of records, authorised editor and documented configuration | A broken MX record could also stop your email |
| 4. Hosting | Clear contracting party, billing and login permissions | Accessible only through an outside account |
| 5. Files and database | An export and backup that actually work | Admin login exists, but no way to restore the site |
| 6. Website administrator | Appropriate role and separate developer access | Shared password or a deactivated user |
| 7. Code and plugins | Documented handover, licences and permitted uses | A new contractor cannot modify or update the site |
| 8. Business email | Review mailbox management and MX/SMTP settings | Email stops working during website migration |
| 9. Analytics | Business-owned permissions for Search Console and analytics accounts | Loss of access to historical reporting |
| 10. Images, logos and fonts | Retained usage rights and licences | An invoice does not settle reuse rights |
Practical rule: not every service contract necessarily has to be in your business name. Managed hosting, for example, can be a perfectly reasonable solution. However, handover, exports, access and cancellation terms must be documented in writing. For help budgeting ongoing costs, see the website maintenance costs guide.
What do the rights to use source code and images mean?
The assumption 'I paid for the website, so I automatically own all copyright' is not safe. Your contract determines which rights you have to use code, branding, graphics, photographs or licensed components. Third-party terms may apply to some elements.
Ask your contractor whether you will receive exportable website files, the database and the required documentation; whether the next developer can use the delivered work; whether any licences are non-transferable; and what happens when the engagement ends. Custom code and commercial plugins are not the same thing. Rather than a general promise of unrestricted use, you need a specific contract clause.
If it is unclear who has access or who is responsible for the services, start by preparing a technical inventory of the domain, hosting and related accounts.
When it's your own business
Keep your business's digital foundations under your control
You don't need to manage DNS yourself to have clear permissions. Agree who will manage the domain, hosting and transferred access rights when your website launches.
How can you keep access secure when working with a specialist?
You don't need to change servers or DNS records yourself. When commissioning the work, agree that access can be revoked, your business retains control, and all important handovers are documented.
- Have a primary administrator associated with the business. Access and recovery must not work only through the contractor's personal email account.
- Give separate users or roles. Where the service supports it, do not share one common password.
- Enable multi-factor authentication. Check recovery options, and don't send passwords in public messages.
- Record why each person has access. DNS management, billing and content editing may require different permissions.
- Revoke access you no longer need when changing providers. First test the business login and a working backup; only then reduce permissions.
The principle is similar to managing Google Business Profile ownership: your business can retain ongoing control while an external partner handles day-to-day work.
Five-point test: could you change providers tomorrow?
Don't just ask 'Have I received all the logins?' Work through the following checks before handover and record anything missing.
- Domain identity: you know the registered domain holder and registrar, and have verified the contact details.
- Renewals: you know the next renewal dates for the domain, hosting and licences, and can access the invoices.
- Backups: you can obtain the required files and data, and know how to restore them successfully.
- DNS and email: you have a list of essential records and know who will test outgoing and incoming email after changes.
- A new specialist: can safely receive their own suitable permissions without using the previous contractor's login.
If even one of these five points is missing, add it as a documented handover task. Within the full website development and handover process, treat it as a milestone in its own right rather than a nasty surprise at the end.
What if the previous developer still controls everything?
| Situation | First check | Safe next step |
|---|---|---|
| Domain tied to the developer's name | Registered holder and contract | Arrange access and management transfer with the registrar |
| Hosting is in the contractor's account | Contract, billing, exports and exit conditions | Plan backups and a replacement service; do not cancel automatically |
| Same domain, different hosting needed | Inventory of DNS, email, SSL, backups and URLs | Schedule migration and functional testing without unnecessarily changing domain ownership |
| You only have CMS administrator access | Files/database export, DNS and licence access | Request a separate handover list and test restoration |
Begin with a calm written request: list the access rights, backups and contractual documents you need. Don't change DNS records at random, and don't delete the old hosting before testing email and backups. If you change the URL structure or domain, address the SEO risks of website migration separately.
Frequently asked questions
If my business holds the domain, does hosting also have to be in my name?
Not necessarily. Other contractual arrangements can work. What matters is knowing who provides the service and having access, data transfer, backups and termination agreed in your contract.
Is changing registrars the same as changing hosting providers?
No. The registrar manages domain registration; the host serves the website. DNS changes can be independent of both and may affect email.
Is a WordPress administrator account enough?
It may be enough for editing content, but not necessarily for a complete handover. Also check the registered domain holder, DNS, hosting, backups, licences and analytics.
Can I buy a .hu domain forever?
Not quite. The .hu registry governs rights to use domains and the conditions for maintaining them. The current rules and renewal obligations matter.
Can I change DNS immediately if I have the password?
Authentication and authorisation are only the first considerations. Changes can bring down your website or email. Take a configuration snapshot, plan the changes and prepare tests first.
Sources and professional references
Open official sources
Related guides
Next step · Kaluzsa
Want a new website with clear ownership arrangements?
Let's discuss a website development process that makes technical responsibilities and your essential access rights clear from the start.