Introduction #

It’s important to know the responsibilities you carry for your domain(s) and to know who actually owns the domain(s). In this doc we’ll explain the basics you need to know for your ProRedLine domain(s).

---

Domain Ownership #

When a domain is registered through ProRedLine, the domain belongs to the customer, not to ProRedLine. In other words, ProRedLine provides the registration-related service and technical handling, but does not become the owner of the domain itself.

The owner of the domain is the individual or company for whom the domain is registered. This means the customer remains the party with the ownership interest in the domain and the right to decide what should happen with it.

The Role of ProRedLine #

For domains registered through ProRedLine, ProRedLine acts as the technical service provider and intermediary in the registration process. This means ProRedLine may be involved in the technical management of the domain, such as DNS-related handling, registrar communication, technical support, and certain administrative processes.

ProRedLine may also be listed in technical or service-related contact roles where relevant, but those roles do not transfer ownership of the domain away from the customer.

What This Means in Practice #

Although the customer remains the domain owner, direct technical access at registrar level is not handled by the customer independently through the registrar in the normal ProRedLine setup. Instead, requests that affect the technical or administrative handling of the domain are managed through ProRedLine.

This means:

• the customer remains the owner of the domain
• the customer decides what should happen with the domain
• technical handling and execution take place through ProRedLine

So while the customer does not directly manage the registrar relationship themselves in day-to-day practice, the domain is still theirs and not owned by ProRedLine.

Ownership and Control #

Because ownership remains with the customer, ProRedLine does not claim legal ownership over customer domains and does not treat registered customer domains as company-owned assets.

At the same time, certain changes or actions involving the domain must still be requested through ProRedLine, since ProRedLine acts as the technical intermediary for the service.

---

WHOIS Data and Contact Information #

WHOIS data refers to the official contact information linked to a domain registration. This information is stored at registrar and registry level and is used to identify the party connected to the domain, together with the relevant contact roles involved in its registration and management.

For domains registered through ProRedLine, the contact information used for the domain is normally based on the customer information provided with the ProRedLine order. If changes are needed later, those updates can be requested through ProRedLine support.

What WHOIS Data Includes #

WHOIS-related registration data can include information such as the registrant name or company, registrant email address, administrative contact details, technical contact details, abuse-related contact information, and domain registration or expiration dates.

Depending on the domain extension and applicable privacy rules, some of this information may not be publicly visible in WHOIS lookups. However, that does not mean the information is absent. The full registration data still exists at registrar level as required for the domain registration.

Contact Roles #

WHOIS and registrar records can include different contact roles, each with a different purpose.

The registrant is the party connected to ownership of the domain.
The administrative contact is typically relevant for ownership-related communication or approval processes.
The technical contact is used for technical domain-related matters and, in managed setups, may be associated with ProRedLine.
The abuse contact is used for abuse-related communication where relevant.

These roles do not all serve the same function, which is why the contact structure of a domain may include both customer-related and service-related details depending on the situation.

Accuracy of Contact Information #

It is important that the contact information linked to a domain remains accurate. Incorrect or outdated details can lead to practical problems such as failed verification, transfer issues, or domain-related administrative interruptions.

For domains managed through ProRedLine, updates to this information are handled through support rather than by direct registrar-side self-service. This helps ensure that changes are applied correctly within the service structure.

Verification and Domain Management #

Registrars may use the stored contact information for verification emails, confirmation requests, transfer-related communication, and other important notices connected to the domain. If the relevant contact details are incorrect, these processes may fail or be delayed.

This is one of the reasons why keeping domain contact information current is important, even when some or all WHOIS details are privacy-protected from public view.

---

Customer Responsibilities for the Domain #

As the domain owner, you remain responsible for the domain and how it is used. This applies regardless of whether the domain is connected to ProRedLine hosting, external services, or only DNS management.

ProRedLine acts as the service provider and technical intermediary, but that does not transfer ownership responsibility away from the customer.

Legal and Operational Responsibility #

The customer is responsible for the domain name itself, the way it is used, and the services connected to it. This includes responsibility for content published under the domain, email sent from the domain, and compliance with applicable laws, policies, and regulations.

In practice, owning a domain is not only a technical matter. It also carries administrative and legal responsibilities.

Registration and Contact Information #

The customer is responsible for providing correct registration-related information and for keeping relevant domain contact details accurate. This also includes responding to verification or confirmation requests where required.

If contact details are incorrect or outdated, domain-related processes may fail and, in some cases, the domain may be suspended or otherwise affected.

Renewals and Expiration #

The customer is responsible for making sure the domain is renewed on time and that any required payment is completed before expiration.

If a domain expires, it may stop resolving, enter a recovery or redemption stage, or eventually become unavailable. Recovery after expiration is not something that can always be guaranteed, so timely renewal remains the customer’s responsibility.

DNS and Configuration #

If the customer chooses to manage DNS records or connect the domain to services, the customer is responsible for ensuring those settings are correct. Incorrect DNS changes can cause website downtime, email failures, or loss of service functionality.

ProRedLine provides the tools and service environment, but does not automatically correct customer-made DNS misconfigurations.

External Services and Third-Party Use #

If the domain is connected to external providers or third-party services, the customer is also responsible for making sure the setup is compatible and correctly configured. This includes following the requirements of the external service and applying any necessary DNS or domain-related changes.

Abuse, Misuse, and Policy Compliance #

The customer is responsible for preventing misuse of the domain, including spam, phishing, illegal content, or other prohibited use. If abuse or policy violations occur, the customer remains responsible for the domain-related use involved.

Where relevant, ProRedLine may take action on connected or hosted services if misuse, abuse, or policy violations are detected.

Transfers and Ownership-Related Actions #

If the customer wants to transfer the domain, change ownership-related details, or use authorisation processes, the customer is responsible for initiating and approving those actions correctly. This also includes keeping transfer-related information secure where applicable.