atdomain
atdomain.at / Domain guides / Domain & responsibility
Domain & responsibility

Domain holder, billing and account access: who handles what?

Who should hold your .at domain, who pays and who changes DNS? Separate holder details, account access and agency tasks for your Austrian project.

The essentials

Separate the registered domain holder from billing, the customer account and technical maintenance. A paid invoice or website login alone does not confirm the holder details. Before registration, agree which person or organisation should hold the domain, then document account responsibility and the tasks assigned to your technical contact.

Blue globe with three separate cards showing a person, receipt and gear
The domain holder, billing arrangements and technical maintenance serve different purposes. Record each responsibility separately even when one person handles several roles.

1. Decide who should be listed as the domain holder

For a .at domain, the registered holder is the relevant role for the rights and responsibilities arising from registration. Before ordering, consider whether an individual or an organisation should hold the domain. Official .at information requires individuals’ first and last names and, for organisations with their own legal personality, the complete name including legal form. Do not confuse the person filling in an order with the intended holder. Resolve uncertain organisation details before ordering instead of entering whichever name is readily available. The fact that someone designed the website does not answer this separate question about the registration.

Prepare a .at domain for your own business

2. Payment and technical work are separate responsibilities

An invoice identifies a billed service and its recipient. Check the registered holder details separately. Technical access also initially tells you what someone can edit, rather than proving that a documented holder change has taken place. For example, a joinery business might commission an agency to build its website. The agency can prepare the connection and invoice its working time without being the intended domain holder. Record that agreement before the project starts. For an existing domain, consult order documents and confirmed registration details instead of drawing conclusions from a single receipt. Keep the evidence for each question distinct.

3. Make a small responsibility record for the project

Create a project record that will still make sense a year from now. Include names, tasks and a reachable contact channel, but no passwords. Even where one person handles several roles, list the responsibilities separately. When an employee or agency changes, you can then see which details need checking. The table is an organisational aid, not a description of extra access permissions in the customer account. An internal title such as “project owner” does not replace the actual registered holder details or any required confirmation. Also agree who will keep this record current as the project develops.

3. Make a small responsibility record for the project
AreaWhat to record
Registered holderIntended person or organisation and checked details
Invoices and renewalResponsibility for records, dates and payment
Customer accountResponsible person and reachable account email
Technical maintenanceSpecific website, mail or DNS task
Open pale-blue project folder with a globe card beside a receipt, blue checklist and pencil
A project record should identify holder details, recurring costs and technical tasks. Passwords and private access keys do not belong in a generally shared list.

4. Give an agency a clearly defined task

Describe the technical work specifically: for example, enter the supplied DNS values for an existing website and check its connection. That task is not a reason to change holder details as a precaution. Agree whether you will enter the values yourself or go through the work together with your technical contact. Do not assume every customer account offers separate agency roles or a restricted guest login. Ask for a clear record of changes and results. A useful handover also includes the services being connected and their instructions, allowing the project to be maintained later without relying on the same individual.

Understand the purpose of technical DNS tasks

5. Protect account access and keep its email reachable

Use a strong, unique password for your domain account rather than reusing one from another service. A password manager can help manage it securely. The account email must remain reachable because important confirmations and recovery messages may depend on it. For a new project, check that you can already access this address; a mailbox beneath the new domain that has not yet been configured is unsuitable. Do not put credentials in an openly shared project record or a support ticket. Record who manages account access and how an authorised change will be arranged, without including the password itself in that record.

Manage account email and password changes
Cobalt padlock beside an envelope, key with yellow tag, globe and shield
Account access and a reachable recovery email are separate responsibilities. A working website login does not replace domain-account access or checking the registered holder.

6. Distinguish profile edits, holder changes and DNS work

At atdomain.at, editing a profile does not automatically change the registered holder of an existing domain. Request a holder change separately through support and wait for the required checks and confirmations. Similarly, changing nameservers is a technical change, not a substitute for transferring the holder role. Describe exactly what you need: correct contact details, name a different person or organisation as holder, or connect the website technically. After completion, check the area concerned. Successful sign-in or a reachable website alone does not confirm that a different requested process has already been completed. Keep the individual requests and their confirmations identifiable.

Request a change of registered domain holderPlan a nameserver change as a separate task

7. Check access and working services separately at handover

Go through a handover together before the previous contact becomes unavailable. Can you open the right customer account and identify the domain? Are the website and required email connections still working after the agreed task? Do you have the current DNS instructions and a contact for follow-up questions? Avoid modifying working records just to demonstrate that a handover happened. If holder details are unclear or access is missing, use a known support channel to ask about the appropriate verification procedure. A dispute about entitlement needs separate review; a practical handover checklist does not decide it. Preserve relevant documents for that review.

8. Record domain costs and the next review date

A standard new .at domain at atdomain.at currently costs €12.99 total price for the first year. Renewal is €15.99 total price per additional year. Record who checks ongoing charges and notices even when an agency built the website. Working time, website services and mailboxes are separate cost items; we do not currently sell hosting or email mailboxes. With our default nameservers, manage DNS in the customer account; custom nameservers are supported too. After a change of technical contact or changes within your organisation, review whether the recorded contacts, access arrangements and responsibilities are still appropriate for the project.

Search for a .at domain and prepare registrationCurrent registration and renewal total pricesPlan recurring domain costs clearly

An idea needs an address.

Search .at domains ↗