Domain Services Agreement

This Domain Services Agreement governs the provision of domain name registration, renewal, transfer, and management services by Core Hosting OÜ ("Core", "we", "us") to the Customer. By registering a domain name through Core Hosting or using domain services, the Customer acknowledges that they have read, understood, and agree to be bound by this Agreement.

1. Terms and Definitions

Domain Name means a unique address in the Domain Name System (DNS) used to identify resources on the Internet.

Registrar means an organization accredited by the relevant registry to register domain names.

Registry means the organization that manages the database of domain names for a specific domain zone.

Registrant (Domain Holder) means the person in whose name a domain name is registered.

Administrative Contact means a person authorized by the Registrant to manage the domain name and interact with the Registrar.

Technical Contact means a person responsible for the technical configuration of the domain name.

WHOIS means a publicly accessible database containing information about registered domain names and their holders.

WHOIS Privacy (ID Protection) means a service that allows hiding the Registrant's personal data in the public WHOIS database by replacing it with proxy service data.

Auth-Code (EPP Code, Authorization Code) means a unique security code required to transfer a domain name to another registrar.

Grace Period means a grace period after the expiration of a domain registration during which the domain can be renewed without additional fees.

Redemption Period means a recovery period for a deleted domain during which the domain can be restored for an additional fee.

Auto-renewal means automatic renewal of domain name registration upon expiration of the current registration period.

International Domain Zones means gTLDs (generic Top-Level Domains) and ccTLDs where registration is performed through a partner registrar.

National Domain Zones means the domain zones .EE, .FI, .LV, .IS where Core Hosting acts as a direct registrar.

Name Servers (DNS Servers) means servers that store and provide information about domain names and their corresponding IP addresses.

UDRP (Uniform Domain-Name Dispute-Resolution Policy) means the mandatory administrative procedure for resolving domain name disputes.

URS (Uniform Rapid Suspension System) means a faster alternative dispute resolution mechanism for clear-cut trademark infringement cases.

2. Subject of the Agreement

Core undertakes to provide the Customer with services for registration, renewal, transfer, and management of domain names in accordance with the terms of this Agreement. Services are provided in the following domain zones:

• International zones: .com, .net, .org, .info, .biz and other gTLDs/ccTLDs through a partner registrar
• National zones: .EE, .FI, .LV, .IS directly

The Customer undertakes to comply with the terms of this Agreement, as well as the policies and rules of the relevant registries and registrars.

3. Role of Core Hosting

Core Hosting operates in two capacities depending on the domain zone.

Reseller for International Domain Zones

Registration is performed through partner registrar P.D.R. SOLUTIONS (U.S.) LLC (legal address: 10 Corporate Drive, Massachusetts, Burlington, 01803, United States; VAT ID: EU826478134). Core Hosting acts as an intermediary between the Customer and the registrar. As a reseller, Core Hosting is not responsible for decisions made by the registrar or registry but undertakes to make reasonable efforts to protect the Customer's interests.

Direct Registrar for National Zones

Core Hosting acts as a direct accredited registrar for the following national domain zones:

• .EE (Estonia) — accredited by Estonian Internet Foundation
• .FI (Finland) — accredited by Traficom
• .LV (Latvia) — accredited by NIC.LV
• .IS (Iceland) — accredited by ISNIC

As a direct registrar, Core Hosting bears full responsibility for providing services in accordance with the rules of the respective registries.

Chain of responsibility: for international zones the chain is Customer → Core Hosting → P.D.R. SOLUTIONS → Registry; for national zones it is Customer → Core Hosting → Registry.

4. Domain Name Registration

Right to Register

The Customer warrants that they have the legal right to register the requested domain name and that registration and use of the domain name does not violate third-party rights, including trademark rights, trade names, and other intellectual property rights. The Customer bears full responsibility for the choice of domain name and the consequences of its registration. Registration of a domain name does not create or confirm any legal rights to the name beyond the registration itself.

Registration Process

Domain name registration is performed based on the Customer's application. To register a domain, the Customer must provide accurate and current contact information, including:

• Name or company name of the domain holder
• Postal address
• Email address
• Phone number
• For legal entities: registration number/code
• For some zones: additional identification data

For domains in national zones (.EE, .FI, .LV, .IS), additional requirements for Registrant identification may apply according to Section 12. Core processes applications on a "first-come, first-served" basis. Domain registration is considered complete after confirmation by the registrar/registry and receipt of notification by the Customer from the Core. Registration will not be completed until all required information is accurately submitted and the process is completed or cancelled by one of the parties.

Registration Periods

A domain name is registered for a period of 1 to 10 years depending on the domain zone and the Customer's choice. Actual application processing time depends on the domain zone: for most gTLDs from several minutes to 24 hours, for certain ccTLDs up to 5 business days.

Grounds for Refusal of Registration

Core, the registrar, or the registry may refuse to register a domain name in the following cases:

• The domain name is already registered by another person
• The domain name is reserved or blocked by the registry
• The domain name violates naming rules of the respective zone
• Incomplete or inaccurate data has been provided
• Special requirements for registration in this zone are not met
• Registration services have not been paid for
• There are technical obstacles to registration
• The domain name is subject to legal proceedings or disputes

In case of refusal, the Core notifies the Customer with indication of the reason.

Contact Data Verification

After domain registration, the Customer must verify the administrative contact email address within the timeframe established by the registrar (usually within 15 days). Failure to verify the email address may result in suspension of the domain name. The registrar may periodically request re-verification of contact data throughout the registration term.

5. Domain Name Renewal

Renewal Terms

A domain name may be renewed at any time during its registration period, for a period of 1 to 10 years, provided that the total registration period does not exceed the maximum allowed for that zone (usually 10 years). The combined remaining validity period and the added renewal period must not exceed 10 years or the zone-specific maximum.

Renewal Notifications

Core sends the Customer notifications about domain registration expiration 30 days before expiration, 14 days before expiration, and 2 days before expiration. Notifications are sent to the email address of the administrative contact specified in the domain data. The Customer is responsible for maintaining current contact data and receiving notifications. Failure to receive notifications does not relieve the Customer of responsibility for timely domain renewal.

Consequences of Non-Renewal

If a domain name is not renewed before the registration expiration date, the domain enters Grace Period status. Grace Period duration depends on the domain zone: most gTLDs 0–45 days, .LV and .FI 30 days, .EE 15 days. During the Grace Period, the domain can be renewed at the regular price, but its functionality may be limited (DNS may be suspended).

After the Grace Period expires, the domain may enter Redemption Period status if provided by the registry policy. Domain restoration during Redemption Period is possible for an additional fee, which is typically significantly higher than the regular renewal cost. The duration of Redemption Period is usually 30 days for most zones. After the Redemption Period ends, the domain is deleted from the registry and becomes available for registration by any party. Core is not responsible for loss of a domain due to the Customer's failure to renew it on time.

6. Domain Name Transfer

Transfer to Core Hosting (Incoming Transfer)

To transfer a domain name from another registrar to Core Hosting, the Customer must:

• Obtain an Auth-Code (authorization code) from the current registrar
• Ensure the domain is unlocked for transfer
• Ensure the domain was registered at least 60 days ago
• Ensure the domain registration does not expire within the next 2 weeks
• Submit a transfer request through the Core Hosting control panel
• Ensure contact email addresses are valid and accessible

After submitting a transfer request, a confirmation email will be sent to the domain's administrative email address. The transfer must be confirmed or rejected by the current registrar within 5 days; if no response is received, the transfer is automatically approved. Upon successful transfer, 1 year is automatically added to the domain registration period for most zones. The cost of transfer usually includes domain renewal for 1 year. Transfer processing typically takes 5–7 days.

Transfer from Core Hosting (Outgoing Transfer)

The Customer has the right at any time to transfer their domain to another registrar. To obtain an Auth-Code, the Customer can generate the code in the control panel independently (free of charge) or request it through the support service. In certain cases, a fee may be charged for providing an Auth-Code according to the current price list. Core must provide the Auth-Code within 5 calendar days from the date of the request. Core may not unreasonably prevent domain transfer or require additional payment, except in cases where there is an outstanding payment for services. The Customer must ensure there are no outstanding invoices before initiating an outgoing transfer.

Transfer Restrictions

Domain name transfer is prohibited in the following cases:

• The domain was registered less than 60 days ago
• The domain was transferred less than 60 days ago (60-day transfer lock)
• The domain is in locked status
• There is an ongoing dispute regarding the domain (UDRP, URS, or court proceedings)
• There is an outstanding payment for services
• The domain is in redemptionPeriod or pendingDelete status
• The domain is subject to legal or registry hold

The 60-day transfer lock after registration or previous transfer is a standard ICANN policy and cannot be waived.

Change of Registrant (Change of Ownership)

Change of domain name holder is performed by submitting a corresponding request through the control panel or support service. For national domain zones (.EE, .FI, .LV), special verification procedures for the new holder may apply. Change of registrant for .com, .net, and some other zones initiates a 60-day transfer lock to another registrar (can be disabled upon request for .com/.net). Both the current and new Registrant must confirm the ownership change. Required documentation may include proof of right to the domain name (purchase agreement, court decision, inheritance documents, etc.).

7. Rules Applicable to Top-Level Domains

The Customer acknowledges and agrees to comply with all policies, rules, and requirements established by the registry operators for each top-level domain. Registry policies are incorporated into this Agreement by reference and are binding on the Customer. These policies may include but are not limited to:

• Domain-specific eligibility requirements
• Acceptable use policies
• Dispute resolution policies (UDRP, URS, national procedures)
• Data collection and publication requirements
• Renewal and deletion procedures
• Transfer restrictions and requirements
• Name server and technical requirements
• Reserved and premium domain name lists

Registry Policy Resources

The Customer can review the current policies for domain extensions at the following locations:

ICANN General Policies:

• ICANN gTLD Consensus Policies
• ICANN Registrar Accreditation Agreement

International Domain Zones:

• Core Hosting Aggregated Policies (multiple TLDs)
• P.D.R. SOLUTIONS / ResellerClub Agreements

National Domain Zones (ccTLD):

• .EE (Estonia): Estonian Internet Foundation
• .FI (Finland): Traficom
• .LV (Latvia): NIC.LV
• .IS (Iceland): ISNIC

Partner Registrar Policies:

• P.D.R. SOLUTIONS / ResellerClub

Core will make reasonable efforts to inform Customers of significant policy changes but is not responsible for monitoring or notifying all registry policy updates. It is the Customer's responsibility to review and comply with applicable registry policies. Registry operators may change their policies at any time; continued registration and use of a domain name constitutes acceptance of updated registry policies.

8. WHOIS and Personal Data Protection

WHOIS Data Publication

In accordance with ICANN and registry policies, certain information about the domain holder is published in the publicly accessible WHOIS database:

• Domain name
• Registrant name or company name
• Contact data (may be hidden for natural persons in accordance with GDPR)
• Administrative and technical contact data
• Name servers
• Registration, update, and expiration dates
• Domain status
• Registrar name

The Customer warrants the accuracy and currency of the data provided for WHOIS. Providing false or inaccurate data is grounds for suspension or cancellation of domain registration. The Customer must update WHOIS data within 7 days of any changes.

WHOIS Privacy (Personal Data Protection)

For domains in zones where technically possible, the Core offers WHOIS Privacy (ID Protection) service for an additional fee. When WHOIS Privacy is activated, the Customer's personal data in the public WHOIS database is replaced with proxy service data. WHOIS Privacy is not available for all domain zones; the list of zones with available protection is published on the Core's website.

WHOIS Privacy cannot be applied to domains where registry rules require mandatory publication of holder data (e.g., some ccTLDs, .us domains requiring U.S. nexus). Use of WHOIS Privacy does not release the Customer from the obligation to provide accurate contact data to the Core/registrar. Even with WHOIS Privacy enabled, actual Registrant data must be disclosed in cases of valid court orders, law enforcement requests with proper legal basis, UDRP/URS proceedings, and valid intellectual property claims.

GDPR Compliance

For domains registered by natural persons from the European Economic Area, GDPR provisions on personal data protection apply. Contact data of natural persons may be hidden from public WHOIS in accordance with registrar and registry policies. In case of lawful request, domain holder data may be disclosed to authorized parties (law enforcement agencies, courts, dispute resolution procedures). The Customer has the right to request access to their personal data, correction, deletion (subject to domain registration requirements), and restriction of processing.

Obligation to Update Contact Data

The Customer must maintain current contact data throughout the entire domain registration period. Changes to contact data must be submitted through the control panel within 7 days from the date of change. Core may periodically request confirmation of contact data accuracy. Failure to maintain accurate contact data may result in domain suspension or deletion.

9. Auto-Renewal

Auto-Renewal Activation

The Customer may activate the automatic domain name renewal function through the control panel. When auto-renewal is activated, the domain will be automatically renewed for the selected period (usually 1 year) upon expiration of the current registration period. For certain domain zones (e.g., .LV), auto-renewal may be activated by default in accordance with registry policy. The Customer is responsible for ensuring sufficient funds in their account for auto-renewal to succeed.

Auto-Renewal Process

Auto-renewal is processed according to the following schedule (may vary by zone):

• For most gTLDs: 30–45 days before expiration
• For .LV: 30 days before expiration (default enabled)
• For .FI: 30 days before expiration
• For .EE: varies, check registry policy

Core will attempt to charge the renewal fee from the Customer's account or payment method on file. If auto-renewal fails (insufficient funds, payment method expired), the Customer will be notified and the domain will not be automatically renewed. Failed auto-renewal does not prevent manual renewal before domain expiration.

Disabling Auto-Renewal

The Customer may disable auto-renewal at any time through the control panel. To prevent auto-renewal for the current registration period, auto-renewal must be disabled before the renewal process begins (typically 30–45 days before expiration). Disabling auto-renewal does not cancel existing domain registration; the domain will simply not be automatically renewed upon expiration.

Auto-Renewal Notifications

Before processing auto-renewal, the Core sends a notification to the Customer's email address. After successful auto-renewal, the Customer receives confirmation and updated registration information. If auto-renewal fails, the Customer receives notification with instructions for manual renewal.

10. Domain Suspension and Deletion

Grounds for Suspension

Core, the registrar, or the registry may suspend a domain name in the following cases:

• Non-payment for registration or renewal services
• Violation of this Agreement or registry policies
• Providing false or inaccurate WHOIS data
• Failure to verify administrative contact email address
• Court order or law enforcement request
• UDRP/URS proceeding
• Violation of intellectual property rights
• Use of domain for illegal activities (spam, phishing, malware distribution)
• Violation of registry-specific policies
• Registrar or registry operational requirements

Suspended domain functionality is limited: DNS records may not resolve, website and email may not work. The domain remains registered during suspension and can be restored upon resolution of the issue that caused suspension.

Suspension Notice

Core will attempt to notify the Customer before suspension when possible. In cases of legal requirements, security threats, or urgent abuse, suspension may occur without prior notice. Core will provide information about the reason for suspension and steps required for restoration.

Domain Restoration After Suspension

To restore a suspended domain, the Customer must:

• Eliminate the cause of suspension
• Pay all outstanding invoices
• Provide accurate and complete WHOIS data
• Comply with all requirements specified by the Core, registrar, or registry

Restoration timing depends on the reason for suspension and domain zone policies. Additional fees may apply for domain restoration, particularly if the domain has entered Redemption Period.

Domain Deletion

A domain name may be deleted in the following cases:

• Registrant's request for deletion
• Expiration of registration period and all grace periods without renewal
• Court order or UDRP/URS decision
• Registry policy requirements
• Registrant (legal entity) has been dissolved and no valid successor claim has been made within the specified timeframe

After deletion, the domain enters a mandatory waiting period before becoming available for public registration (typically 30 days). Deleted domains cannot be restored except during the Redemption Period if applicable.

Special Provisions for Deceased or Dissolved Registrants

If the Registrant who is a natural person is deceased, the domain can be transferred to legal heirs with proper succession documents. If no transfer request is received within 6 months, the domain may be deleted; a grace period of 30 days is provided for submitting documentation.

If the Registrant who is a legal entity is dissolved, the domain can be transferred to legal successors with proper documentation. If no transfer request is received within the specified period, the domain may be deleted. For national zones, specific registry procedures apply (see Section 12).

11. Domain Name Disputes

Types of Dispute Resolution

Domain name disputes may be resolved through UDRP (Uniform Domain-Name Dispute-Resolution Policy) for most gTLDs, URS (Uniform Rapid Suspension System) for new gTLDs, national dispute resolution procedures for ccTLDs, court proceedings, or direct negotiation between parties.

UDRP Proceedings

UDRP is a mandatory administrative procedure for resolving domain name disputes involving allegations of abusive registration. A complainant must prove all three elements: (1) the domain name is identical or confusingly similar to a trademark in which the complainant has rights; (2) the Registrant has no rights or legitimate interests in the domain name; (3) the domain name was registered and is being used in bad faith.

UDRP proceedings are conducted by approved dispute resolution providers (e.g., WIPO, Forum, CAC). Core will comply with UDRP decisions and implement required actions (transfer or cancellation of domain). During UDRP proceedings, the domain is typically locked and cannot be transferred.

URS Proceedings

URS is a faster, lower-cost alternative to UDRP for clear-cut cases of trademark infringement. URS proceedings result in suspension of the domain rather than transfer. Suspended domains display a standard page indicating the domain is suspended pursuant to URS. The Registrant may appeal URS decisions within a specified timeframe.

National Dispute Resolution Procedures

For .EE domains, disputes are resolved by the Estonian Internet Foundation Domain Disputes Committee in accordance with its regulations. For .FI domains, disputes are resolved according to Finnish law and Traficom regulations. For .LV domains, disputes are resolved according to Latvian law and NIC.LV policies. For .IS domains, disputes are resolved according to Icelandic law and ISNIC procedures.

Registrant's Obligations During Disputes

The Registrant must participate in dispute resolution proceedings if initiated. Failure to respond to complaint notifications may result in a default decision against the Registrant. The Registrant must provide accurate information and documentation requested by dispute resolution providers. Core will forward all dispute-related communications to the Registrant's administrative contact email address.

Core's Role in Disputes

Core acts as a neutral party and does not take sides in disputes between Registrants and third parties. Core will implement decisions made by dispute resolution providers, courts, and arbitration tribunals. Core may place domains on hold during disputes to prevent transfer or modification. Core is not responsible for legal costs, damages, or other consequences of domain name disputes.

12. Special Conditions for National Domain Zones

National domain zones (.EE, .FI, .LV, .IS) are subject to specific rules and requirements of their respective registries. Core Hosting acts as a direct accredited registrar for these zones and maintains contractual relationships with the respective registries. Additional requirements may include identity verification, local presence requirements, or specific documentation. Registry policies for national zones may differ significantly from ICANN gTLD policies.

.EE Domain Names (Estonia)

Registry: Estonian Internet Foundation (EIF). Registry Policies: internet.ee. Key requirements:

• Identity verification required (Estonian ID card, Mobile-ID, or bank transfer from Registrant's account)
• Registration periods: 1 to 10 years
• Grace period after expiration: 15 days
• Domain Disputes Committee available for dispute resolution
• Document requirements may differ from international zones

For complete terms and conditions, refer to the EIF Domain Regulation.

.FI Domain Names (Finland)

Registry: Traficom (Finnish Transport and Communications Agency). Registry Policies: traficom.fi. Key requirements:

• Available to all natural and legal persons
• Registration periods: 1 to 5 years
• Maximum total registration period: 5.5 years (including advance renewal)
• Grace period: 30 days after expiration
• Auto-renewal supported (optional)
• Minimum 2, maximum 10 name servers required

For complete terms and conditions, refer to Traficom regulations.

.LV Domain Names (Latvia)

Registry: NIC.LV (Institute of Mathematics and Computer Science, University of Latvia). Registry Policies: nic.lv. Key requirements:

• Available to all persons
• Accurate WHOIS data mandatory
• Grace period: 30 days after expiration
• Auto-renewal activated by default (can be disabled)
• Transfer requires authorization from both registrars

For complete terms and conditions, refer to NIC.LV policies.

.IS Domain Names (Iceland)

Registry: ISNIC (Internet Registry Iceland). Registry Policies: isnic.is. Key requirements:

• Specific requirements may apply for different categories
• Some categories may require local presence or connection to Iceland
• Standard grace periods and transfer procedures apply

For complete terms and conditions, refer to ISNIC domain rules.

The Customer must comply with all registry-specific rules and policies as published on registry websites. Registry policies may be updated; the Customer is responsible for staying informed of changes. Language requirements and documentation standards may vary by registry. Some registries may communicate directly with Registrants in addition to through Core Hosting.

13. Personal Data Processing

Legal Basis and Scope

Core processes personal data of Registrants in accordance with GDPR (Regulation EU 2016/679), the Estonian Personal Data Protection Act, registry-specific requirements, and this Agreement. Personal data processed includes name or company name, personal identification code or date of birth, address (postal and email), phone number, payment information, domain name transaction history, and technical data (IP addresses, access logs). Legal basis for processing is contract performance (provision of domain services), legal obligations (ICANN requirements, registry policies, law enforcement requests), and legitimate interests (fraud prevention, service improvement).

Purposes of Processing

Personal data is processed for the following purposes:

• Domain name registration, renewal, and management
• WHOIS database publication (as required by policy)
• Communication with Registrant
• Billing and payment processing
• Technical support
• Compliance with legal obligations
• Dispute resolution
• Fraud prevention and security

Data is not used for marketing purposes without separate consent.

Data Recipients

Personal data may be disclosed to:

• Registrars (P.D.R. SOLUTIONS for international zones)
• Registries
• WHOIS database (publicly accessible, subject to privacy protections)
• Payment processors
• Dispute resolution providers (UDRP, URS, national procedures)
• Law enforcement and regulatory authorities (upon valid legal request)
• Courts and arbitration tribunals

All data recipients are required to protect personal data in accordance with applicable laws.

Data Retention

Personal data is retained during active domain registration; for 10 years after domain deletion/transfer for .EE domains; according to registry-specific requirements for national zones; for 2 years after contract termination for international zones; and longer if required by law or legal proceedings. Payment data is retained according to accounting and tax law requirements (typically 7 years).

Rights of Data Subjects

Registrants have the right to access their personal data, rectify inaccurate data, request deletion (subject to legal retention requirements), restrict processing (in certain circumstances), data portability, object to processing based on legitimate interests, withdraw consent (where processing is based on consent), and lodge a complaint with the supervisory authority (Estonian Data Protection Inspectorate). Rights can be exercised by contacting Core Hosting support. Deletion of personal data may not be possible while domain registration is active, as accurate WHOIS data is legally required.

International Data Transfers

For international domain zones, personal data is transferred to P.D.R. SOLUTIONS in the United States. Data transfer is based on Standard Contractual Clauses approved by the EU Commission, necessity for contract performance, and adequacy decisions where applicable. For national zones, data is processed within the European Economic Area (Estonia, Finland, Latvia) or with appropriate safeguards (Iceland).

Data Security

Core implements appropriate technical and organizational measures to protect personal data, including encryption of data in transit and at rest, access controls and authentication, regular security assessments, employee training on data protection, and incident response procedures.

In case of personal data breach, the Core will notify the supervisory authority within 72 hours (if required), notify affected Registrants if high risk to their rights, document the breach and response measures, and take steps to prevent recurrence.

14. Information Security

Core's Security Obligations

Core maintains information security measures appropriate to the risks associated with domain name services, including secure access to domain management systems, multi-factor authentication for sensitive operations, regular security monitoring and logging, vulnerability assessments, and backup and disaster recovery procedures. For national zones with specific security requirements (e.g., .FI KATAKRI requirements), the Core complies with applicable standards.

Customer's Security Responsibilities

The Customer is responsible for maintaining confidentiality of account credentials, using strong unique passwords, enabling two-factor authentication when available, promptly reporting suspected security incidents, and keeping contact information current for security notifications. The Customer must not share account credentials with unauthorized persons, use accounts for illegal purposes, attempt to gain unauthorized access to Core systems, or interfere with the security or operation of domain services.

Security Incident Reporting

Core will notify Customers of security incidents that may affect their domains or data. For national zones, security incidents are reported to registries within required timeframes: for .FI within 24 hours to Traficom, for .EE without undue delay to Estonian Internet Foundation, for .LV as required by NIC.LV. Customers should report suspected security incidents to Core Hosting support immediately.

Domain Security Features

Core offers security features including domain locking (prevents unauthorized transfers), DNSSEC support (domain name system security extensions), and registry lock services (where available, for additional protection). Customers are encouraged to enable available security features appropriate to their needs.

15. Liability of Parties

Core's Liability

Core is liable for damages caused by intentional misconduct or gross negligence. The Core's liability is limited to direct damages actually incurred. Core's maximum liability under this Agreement is limited to the amount of fees paid by the Customer for the affected domain name in the 12 months preceding the event giving rise to liability.

Core is not liable for:

• Decisions made by registries or registrars
• Loss of domain name due to Customer's failure to renew or maintain accurate contact data
• Consequences of domain name disputes with third parties
• Service interruptions caused by third parties, force majeure, or technical issues beyond Core's control
• Indirect damages, lost profits, or consequential damages
• Domain registration delays or failures due to registry/registrar issues

Core makes no warranties regarding availability of specific domain names, uninterrupted or error-free operation of domain services, outcome of domain disputes, or third-party services or content.

Customer's Liability

The Customer is liable for all domain name registrations and renewals made through their account, use of registered domain names, accuracy of provided information, compliance with this Agreement and applicable policies, and payment of all fees and charges.

The Customer agrees to indemnify and hold harmless the Core from claims, damages, and expenses (including legal fees) arising from Customer's violation of third-party rights (trademark infringement, etc.), Customer's breach of this Agreement, use of domain names for illegal purposes, and inaccurate or fraudulent information provided by the Customer.

Force Majeure

Neither party is liable for failure to perform obligations due to force majeure events beyond their reasonable control, including natural disasters, war, terrorism, civil unrest, government actions or regulations, Internet infrastructure failures, cybersecurity attacks affecting critical infrastructure, and pandemic or epidemic. The affected party must notify the other party of force majeure events promptly. Obligations are suspended during force majeure but resume when circumstances permit.

Registry and Registrar Decisions

Core acts as an intermediary and is not responsible for decisions made by registries or registrars regarding acceptance or rejection of domain registrations, domain suspensions or deletions, policy changes, fee changes, or dispute resolution outcomes. Core will make reasonable efforts to assist Customers in communicating with registries and registrars but cannot guarantee specific outcomes.

16. Refund Policy

Refunds for domain services are subject to the Core's Refund Policy. Domain name services have specific refund limitations due to the nature of domain registration and registry policies. The Customer is advised to review the Refund Policy carefully before purchasing domain services.

17. Fees and Payment

Fees for domain services and payment terms are specified in the Core's General Terms and Conditions and current price list. Payment is required in advance for domain registration, renewal, and transfer services. The Customer is responsible for reviewing current pricing and payment terms before ordering services.

18. Term and Termination

Term of Agreement

This Agreement becomes effective when the Customer first orders domain services and remains in effect until terminated. Individual domain registrations have specific terms (1–10 years) but this Agreement continues to govern the relationship.

Termination by Customer

The Customer may terminate this Agreement at any time by transferring all domains to another provider, allowing all domains to expire without renewal, or requesting account closure. Termination does not entitle the Customer to refund of pre-paid services unless specifically provided in Section 16. The Customer remains responsible for all fees and obligations incurred before termination.

Termination by Core

Core may terminate this Agreement with 30 days' notice without cause. Core may terminate this Agreement immediately in case of:

• Material breach of Agreement by Customer
• Fraudulent activity
• Non-payment of fees
• Use of services for illegal purposes
• Violation of registry or registrar policies
• Provision of false information

Upon termination by Core, the Customer is responsible for transferring domains to another provider before the termination date.

Effects of Termination

Upon termination, no new domain registrations will be accepted; existing domain registrations continue until their individual expiration dates; the Customer must transfer domains to another provider or allow them to expire; and access to the control panel may be restricted.

Termination does not affect payment obligations for services already rendered, provisions intended to survive termination (liability, indemnification, etc.), or the Customer's obligations to transfer domains away before expiration.

Survival

The following provisions survive termination of this Agreement: payment obligations, liability limitations, indemnification, dispute resolution, and any provision that by its nature should survive.

19. Amendments to Agreement

Core reserves the right to amend this Agreement at any time. Amendments may be necessary due to changes in applicable laws or regulations, changes in registry or registrar policies, changes in ICANN policies, business operational changes, or service improvements or modifications.

Core will notify Customers of material amendments by email to the Customer's registered address and by notice on the Core's website, at least 30 days before amendments take effect. For amendments required by law, registry, or registrar with shorter notice requirements, the Core will notify Customers as soon as reasonably possible.

If the Customer does not agree with amendments, the Customer may terminate the Agreement before amendments take effect, transfer domains to another provider, or allow domains to expire. Continued use of services after amendments take effect constitutes acceptance of the amended Agreement.

20. General Provisions

This Agreement, together with the Core's Privacy Policy, Cookie Policy, Refund Policy, Acceptable Use Policy, and applicable registry and registrar policies, constitutes the entire agreement between the parties regarding domain services.

Core may assign this Agreement or any rights hereunder without Customer's consent. The Customer may not assign this Agreement without Core's prior written consent.

If any provision of this Agreement is found invalid or unenforceable, the remaining provisions continue in full effect. Invalid provisions will be replaced with valid provisions that most closely reflect the original intent.

Failure to enforce any provision does not constitute a waiver of that provision or any other provision. Waiver must be in writing to be effective.

All notices under this Agreement must be in writing and sent to the Customer at the email address registered in their account, and to the Core at the support email published on the website. Notices are deemed received by email 24 hours after sending (if not bounced) and by post 5 business days after mailing.

This Agreement is executed in English. In case of translations, the English version prevails in case of discrepancies. Section headings are for convenience only and do not affect interpretation. This Agreement does not create any third-party beneficiary rights except as explicitly stated regarding registries and registrars. The parties are independent contractors; this Agreement does not create a partnership, agency, or employment relationship.

21. Dispute Resolution and Governing Law

Governing Law

This Agreement is governed by the laws of the Republic of Estonia. International conventions on domain names (ICANN policies, registry agreements) apply to the extent they are incorporated by reference.

Dispute Resolution for Agreement Issues

Disputes between the Customer and Core arising from this Agreement shall be resolved through good faith negotiations, and if unresolved, through the competent courts of Estonia. This does not affect domain name disputes covered by Section 11, or consumer rights under applicable consumer protection laws.

Domain Name Disputes

Domain name disputes with third parties are subject to UDRP/URS for applicable domains, national dispute resolution procedures for ccTLDs, and court proceedings as appropriate. The Customer agrees to participate in applicable dispute resolution procedures.

Venue

Court proceedings shall be brought in Harju County Court, Tallinn, Estonia, or other competent Estonian courts. Each party consents to personal jurisdiction in Estonia for disputes under this Agreement.

22. Contact Information

For questions regarding this Agreement, domain services, or to exercise rights under this Agreement, contact:

For full contact information, see Section 22 of the Core Hosting Terms of Service.
General enquiries: info@core.hosting