Clear rules for every domain.

This Domain Registration Policy (the “Policy”) forms part of the APNCloud Terms of Service and applies whenever a customer registers, renews, transfers, restores, manages, or otherwise uses a domain-name service through APNCloud. It is intended to explain the customer’s responsibilities, the role of registrars and registries, domain lifecycle rules, transfer restrictions, registration-data obligations, renewal and expiration processes, dispute procedures, and circumstances in which a domain may be placed on hold, suspended, deleted, or otherwise restricted. Domain names are governed not only by APNCloud’s contractual terms but also by the rules of the relevant registry, registrar, ICANN where applicable, and the laws and policies that apply to the domain extension and transaction.

1. Scope and Relationship to Other Terms

This Policy applies to all domain-name services made available by APNCloud, including new registrations, renewals, inbound and outbound transfers, contact-data changes, nameserver management, DNS-related configuration provided with a domain, restoration or redemption requests, and other domain functions offered through the APNCloud Client Area. The exact services available may differ by top-level domain (“TLD”), registry, registrar, country, customer type, or technical availability.

This Policy must be read together with the APNCloud Terms of Service, Privacy Policy, Refund Policy, Acceptable Use Policy, Billing & Renewal Policy, Abuse Policy, and any service-specific terms displayed during checkout. If a registry, registrar, ICANN consensus policy, country-code registry rule, or other mandatory domain rule conflicts with this Policy, the mandatory external rule will apply to the extent of that conflict. APNCloud may also require the registrant to accept a registrar or registry registration agreement when necessary.

2. APNCloud’s Role and Third-Party Registrars

APNCloud may provide domain services as a reseller, agent, interface provider, or other intermediary using one or more third-party registrars, registry operators, technical providers, or domain reselling platforms. A customer purchasing a domain through APNCloud understands that APNCloud does not operate every registry and may not itself be the ICANN-accredited registrar of record for the domain. The registrar of record and registry for a domain may be identified through the applicable registration data lookup service.

The registrant’s right to use a domain name is created and maintained through the applicable registrar and registry system. APNCloud does not sell permanent ownership of a domain name. Registration gives the registrant a renewable contractual right to use the registered name for the applicable registration period, subject to payment, continued eligibility, registry rules, dispute procedures, and compliance with applicable policies.

3. Eligibility and Authority to Register

A person or organization placing a domain order must have legal authority to enter into the registration and must provide accurate information. If a domain is registered for a company, employer, client, organization, or other third party, the person placing the order confirms that they are authorized to act for that registrant and to accept the applicable registration terms on its behalf.

Certain TLDs impose eligibility, residency, local presence, identity, industry, trademark, business-registration, documentary, or other qualification requirements. The customer is responsible for satisfying those requirements and providing requested evidence. APNCloud may reject, delay, suspend, or cancel a domain order if the registry or registrar determines that eligibility requirements are not met.

4. Domain Availability and Registration Orders

A domain appearing as “available” in a search result is not guaranteed to remain available until registration is successfully completed by the relevant registry. Availability results can change because another party may register the name, registry data can update, premium status can change, or a technical delay can occur. Payment alone does not guarantee successful registration.

An order is considered successfully registered only after APNCloud receives confirmation from the relevant registrar or registry and the domain appears in the customer’s account or otherwise receives confirmation of successful registration. If a registration fails, APNCloud may retry, request additional information, offer an alternative, or refund the applicable registration charge when appropriate. APNCloud is not responsible for consequential loss caused by a domain being unavailable before successful registration.

5. Registration Data and Accuracy

The registrant must provide complete, current, and accurate domain registration data as required for the relevant TLD. This may include registrant name, organization, email address, telephone number, postal address, country, and other details required by the registrar or registry. The registrant must update such information when it changes.

Providing false, misleading, incomplete, invalid, or unauthorized information may result in verification requests, transfer restrictions, suspension, loss of privacy services, deletion, or other action permitted by the registrar, registry, ICANN policy, or applicable law. The registrant is responsible for maintaining access to the email address associated with the domain because transfer approvals, verification notices, expiration notices, security alerts, and other important communications may be sent to that address.

Where applicable, domain registration data is collected, transferred, published, withheld from public display, retained, or disclosed in accordance with the ICANN Registration Data Policy, registrar obligations, applicable privacy law, and APNCloud’s Privacy Policy. Public registration-data display may be limited, redacted, or unavailable depending on applicable rules.

6. Identity, Fraud and Payment Verification

APNCloud may request reasonable verification before or after a domain order to protect customers, prevent unauthorized transactions, comply with registrar requirements, investigate suspected fraud, or meet legal obligations. Verification may include confirmation of account ownership, payment ownership, contact details, business information, domain purpose, or other information reasonably necessary for the transaction.

If a payment is reversed, charged back, reported as unauthorized, or reasonably suspected to be fraudulent, APNCloud may place the affected domain or account on hold, prevent transfer, suspend services, request verification, or take other proportionate action while the matter is investigated, subject to mandatory registry and registrar rules. Fraudulent use of another person’s payment method or identity is prohibited.

7. Registration Period and Term

Domain registration periods vary by TLD. The period selected and successfully processed at checkout determines the initial registration term, subject to registry limitations. A domain does not automatically remain registered indefinitely. The registrant must renew the registration before expiration or maintain a valid automatic-renewal arrangement where such an option is available.

Some registries restrict the maximum number of years for which a domain can be registered or renewed. A requested multi-year period may therefore be limited, adjusted, or processed according to the relevant registry’s rules. Registry maintenance, premium pricing, restoration fees, or policy changes can also affect future renewal conditions.

8. Pricing, Premium Domains and Registry Fees

Domain prices may differ by TLD, registration period, registry classification, promotional eligibility, premium status, renewal status, transfer type, restoration status, exchange rate, taxes, and supplier cost. Registration, renewal, transfer, and redemption prices are not necessarily the same.

A premium domain may carry a higher registration price, higher renewal price, higher transfer price, or a combination of these. Registry premium pricing can change. Customers should review the price shown for the relevant transaction before completing payment. Promotional registration prices may apply only to the initial term and do not guarantee the same renewal price.

Taxes, duties, regulatory charges, registry surcharges, payment-processing effects, or other mandatory charges may be added where applicable. APNCloud may update future domain pricing when supplier, registry, registrar, tax, currency, or operating costs change. Price changes do not normally alter a registration period already paid for and successfully processed.

9. Renewals and Automatic Renewal

The registrant is responsible for renewing a domain before it expires. APNCloud may send renewal reminders as a convenience, but the customer should independently monitor expiration dates in the Client Area and keep account contact information current. Failure to receive a reminder does not by itself extend the registration term or guarantee recovery after expiration.

Where automatic renewal is offered and enabled, APNCloud may attempt to charge the payment method or account balance associated with the service before or around the renewal date, depending on the billing configuration. Automatic renewal is not guaranteed if the payment method is invalid, expired, blocked, has insufficient funds, requires additional authentication, or if the domain is otherwise ineligible for renewal. The customer remains responsible for confirming that renewal was successfully completed.

Renewal fees are generally non-refundable once a renewal has been submitted to and accepted by the registrar or registry, because the registration period may be extended immediately and the underlying registry fee may become non-recoverable. Any applicable refund rights are governed by the APNCloud Refund Policy and mandatory law.

10. Expiration, Grace Periods and Deletion

If a domain is not renewed by its expiration date, website, email, DNS, and other services connected to the domain may stop working. An expired domain may be redirected, placed on hold, have DNS resolution interrupted, or enter an expiration lifecycle controlled by the registrar and registry.

Some TLDs may provide an auto-renew or renewal grace period after expiration, but the length and conditions vary and are not guaranteed for every TLD. During such a period, the former registrant may be able to renew the domain at the standard renewal price or another price specified by the registrar. A domain may also be deleted earlier where permitted by the relevant rules.

For applicable generic top-level domains, a deleted registration may enter a Redemption Grace Period during which restoration may still be possible through the deleting registrar, commonly with a substantially higher restoration fee. ICANN policy requires a 30-day Redemption Grace Period for applicable gTLD registrations following deletion, subject to the policy’s scope and exceptions. After the applicable redemption and pending-delete stages end, the domain may be released and become available for registration by any eligible party. APNCloud cannot guarantee recovery once a domain expires or is deleted.

11. Domain Transfers to APNCloud

An inbound transfer is subject to the policies of the gaining registrar, losing registrar, registry, and ICANN where applicable. The customer may need to unlock the domain, obtain an authorization or EPP code, confirm transfer contact information, respond to approval requests, and pay any applicable transfer fee.

For applicable gTLDs, a transfer may be restricted during the first 60 days after initial registration and during the first 60 days after a prior inter-registrar transfer. Other transfer restrictions can apply because of dispute proceedings, court orders, fraud, registry rules, transfer locks, or a recent change of registrant. The customer should avoid making unnecessary registrant changes immediately before a planned transfer if those changes could trigger a lock.

A transfer order does not guarantee completion. If a transfer fails because the domain is locked, the authorization code is wrong, contact approval is not completed, the domain expires, the domain is subject to a dispute, or another policy restriction applies, APNCloud may require the customer to correct the issue and restart the process.

12. Transfers Away from APNCloud

Subject to applicable policy and payment status, registrants may request transfer of an eligible domain to another registrar. APNCloud will not intentionally prevent an eligible transfer merely to retain the customer. The registrant may be required to unlock the domain, obtain an authorization code, verify account ownership, or complete security checks.

Transfer-out requests may be denied or delayed where permitted or required by policy, including during applicable 60-day locks, pending UDRP or URS proceedings, court orders, unresolved transfer disputes, fraud investigations, or other mandatory restrictions. A registrar lock status should not be confused with a non-removable policy lock; where policy requires that the registrant be allowed to unlock a domain, the relevant process will be made available.

Outstanding unrelated service invoices do not automatically eliminate transfer rights where applicable transfer policy prohibits denial on that basis. However, the customer remains responsible for valid debts owed under other APNCloud services.

13. Change of Registrant and 60-Day Transfer Lock

Changing the registrant’s name, organization, or email address can be treated as a Change of Registrant under applicable ICANN transfer rules. The registrar may require confirmation from the prior registrant, the new registrant, or authorized designated agents before the change is completed.

For applicable gTLDs, a registrar must generally impose a 60-day inter-registrar transfer lock following a Change of Registrant, unless the registrar offers an allowed opt-out mechanism and the registrant properly opts out before the change. Customers planning both a registrant change and an inter-registrar transfer should consider completing the transfer first when appropriate.

14. Domain Locks, Authorization Codes and Account Security

Customers are responsible for protecting APNCloud account credentials, domain authorization codes, recovery email access, and other security information. An authorization code should be treated as sensitive because it may be used as part of a transfer process.

APNCloud or the registrar may apply domain locks for security, transfer protection, dispute handling, fraud investigation, court orders, registry requirements, or other permitted reasons. Customers should promptly report suspected account compromise or unauthorized domain changes. APNCloud may require identity or account verification before releasing sensitive transfer or ownership information.

15. Nameservers, DNS and Technical Configuration

The customer is responsible for ensuring that nameserver and DNS settings are correct for the services they intend to use, except to the extent APNCloud expressly manages those settings as part of another service. DNS changes may require time to propagate across caches and networks. Propagation times are estimates and cannot be guaranteed.

Changing nameservers, DNSSEC settings, DNS records, mail records, or other domain configuration can interrupt websites, email, or other services. APNCloud is not responsible for outages caused by customer configuration errors, third-party DNS providers, external networks, or unsupported settings, except to the extent required by applicable law or a specific managed-service commitment.

16. Privacy, Proxy and Registration Data Services

Privacy or proxy services may be available for eligible domains, but availability depends on the TLD, registrar, registrant type, legal requirements, and service provider. Such services do not remove the registrant’s responsibility to provide accurate underlying registration data.

Privacy or proxy information may be disabled, disclosed, or bypassed where required by law, registry or registrar policy, dispute procedures, valid rights-protection processes, or lawful disclosure obligations. APNCloud does not promise that registration data will remain anonymous in all circumstances.

The processing of personal data associated with domain services is further described in the APNCloud Privacy Policy. Customers registering domains for other individuals must ensure they have lawful authority to provide any personal information submitted on behalf of those individuals.

17. Country-Code, Internationalized and Restricted TLDs

Country-code TLDs and specialized TLDs may be governed by policies that differ significantly from ICANN gTLD rules. They may impose local presence, trustee, citizenship, business, trademark, industry, documentation, or use requirements. Registration or renewal may be cancelled if the registrant ceases to meet those requirements.

Internationalized Domain Names (“IDNs”) use non-ASCII characters and may be represented technically in encoded form. Compatibility can vary among browsers, email systems, applications, certificates, and third-party services. The customer is responsible for checking whether an IDN is suitable for the intended use.

Registry-reserved, blocked, premium, sunrise, claims-period, trademark-protected, or otherwise restricted names may be unavailable or subject to additional rules and charges.

18. Registrant Ownership, Control and Internal Disputes

APNCloud will generally treat the registered account holder and the registrant data maintained through the registrar system as important indicators of authority, but APNCloud may require additional evidence where ownership or control is disputed. Customers should ensure that domains registered for a business are held using appropriate business-controlled account and contact details.

APNCloud is not a court and does not adjudicate private ownership disputes between business partners, employees, developers, agencies, family members, shareholders, or other parties. Where a dispute cannot be resolved by clear account records or mutual written instructions, APNCloud may restrict changes until the parties provide a binding court order, applicable dispute decision, registrar instruction, or other sufficient legal authority.

19. Prohibited and Abusive Domain Use

Domains registered or managed through APNCloud must not be used to facilitate unlawful or abusive activity. Prohibited conduct includes phishing, malware distribution, credential theft, fraudulent impersonation, spam campaigns, command-and-control infrastructure, unlawful sale of regulated goods, infringement schemes, deceptive domain use, or other conduct prohibited by the APNCloud Acceptable Use Policy.

APNCloud may investigate abuse complaints and may refer matters to the registrar, registry, hosting provider, payment provider, law enforcement, or other appropriate party where reasonably necessary. Actions may include warning, requesting remediation, disabling related hosting, changing DNS, placing a domain on hold, locking the domain, or suspending the account where permitted by applicable rules and proportionate to the risk.

20. Trademark, Intellectual Property and Domain Disputes

Registering a domain through APNCloud does not grant trademark rights or other intellectual-property rights in the name. The registrant is responsible for determining whether the selected domain infringes or violates the rights of another party.

Applicable domains may be subject to the Uniform Domain Name Dispute Resolution Policy (“UDRP”), Uniform Rapid Suspension System (“URS”), registry-specific dispute policies, court proceedings, trademark claims procedures, or other rights-protection mechanisms. APNCloud and the registrar may be required to lock, suspend, transfer, cancel, or otherwise act on a domain in accordance with a valid decision, settlement, court order, registry instruction, or mandatory policy.

APNCloud does not provide legal representation in domain disputes and does not guarantee that a registrant will retain a domain that becomes subject to a successful claim.

21. Suspension, Hold, Cancellation and Registry Action

A domain may be suspended, locked, placed on clientHold/serverHold, cancelled, or otherwise restricted where permitted or required because of non-payment, invalid registration data, failed verification, fraud, abuse, security threats, court orders, dispute proceedings, registry or registrar instructions, sanctions or legal restrictions, or violation of applicable agreements.

Where reasonably possible and appropriate, APNCloud will provide notice and an opportunity to correct a remediable issue. Immediate action may be taken without advance notice when necessary to address serious fraud, phishing, malware, active attacks, legal requirements, risk to third parties, or an instruction from a registrar or registry that APNCloud cannot override.

22. Refunds and Non-Refundable Domain Transactions

Domain registration, renewal, transfer, restoration, redemption, premium-domain, registry, and other domain-related fees may become non-refundable once the relevant transaction has been submitted to and accepted by the registrar or registry. This is because the underlying registry or registrar charge may be immediate and non-recoverable.

The general 14-day refund period described in the APNCloud Refund Policy does not automatically mean that a completed domain registration, renewal, transfer, restoration, premium-domain purchase, or other irreversible third-party domain transaction can be reversed. Eligibility for any refund depends on the status of the transaction, applicable law, and the APNCloud Refund Policy.

If a domain order fails before registration or another paid domain transaction cannot be completed, APNCloud will handle the related payment in accordance with the Refund Policy and the circumstances of the failed transaction. Approved refunds are normally returned to the original payment method where practicable.

23. Resellers, Agents and Customer Responsibility

A customer who resells domain services or registers domains for its own clients remains responsible for accurately communicating applicable domain rules, collecting lawful registration data, obtaining necessary authority, and ensuring that its clients comply with mandatory registrar and registry terms. A reseller must not represent that it owns customer domains merely because it paid the registration charge or manages the account.

Where a reseller, developer, or agency manages a domain on behalf of another party, the parties should maintain clear records of who is the intended registrant and who controls renewal, transfer, and account access. APNCloud may require evidence of authority before acting on conflicting instructions.

24. Communications and Notices

APNCloud, the registrar, or the registry may send important domain notices to the email address associated with the APNCloud account or registration data. These may include verification requests, renewal reminders, expiration notices, transfer confirmations, registrant-change confirmations, abuse notices, dispute notices, or policy updates.

The customer must maintain a working email address and review notices promptly. Customers should also keep spam filtering and mailbox capacity configured so that important domain notices can be received. Failure to read an important message does not guarantee that a deadline, transfer lock, expiration event, or registry requirement will be extended.

25. Service Changes, Registrar Changes and Migration

APNCloud may change upstream registrars, reseller platforms, DNS providers, or other domain-service suppliers when reasonably necessary for reliability, pricing, security, compliance, or business continuity. Such changes may require technical migration or administrative updates but will not intentionally alter the registrant’s substantive right to the registered domain during a valid paid term.

Where a supplier change affects a feature, management interface, privacy service, transfer process, or future pricing, APNCloud may update this Policy or provide additional notice as appropriate. Mandatory registry and ICANN rules may also change independently of APNCloud.

26. Limitation of Domain-Service Guarantees

APNCloud will use reasonable care in processing domain transactions but cannot guarantee uninterrupted registry or registrar systems, continuous DNS availability, successful transfer of every domain, permanent availability of a chosen name, recovery after expiration, acceptance of every registration, or uninterrupted operation of third-party services.

APNCloud is not responsible for losses caused solely by actions or failures outside its reasonable control, including registry outages, registrar outages, third-party DNS failures, global DNS caching, policy-mandated holds, domain disputes, court orders, registry deletions, customer configuration errors, customer failure to renew, or inaccurate registration data, subject always to any liability that cannot lawfully be excluded.

Any broader limitation of liability, warranty disclaimer, indemnity, governing-law provision, and dispute provision in the APNCloud Terms of Service applies to domain services except where a mandatory domain policy or applicable law provides otherwise.

27. Policy Updates

APNCloud may update this Policy to reflect changes in law, ICANN policies, registrar or registry requirements, supplier arrangements, domain products, abuse controls, or business processes. The current version will be published on the APNCloud website with an updated effective date.

Where a change materially affects existing customers and advance notice is reasonably required by law or contract, APNCloud will provide appropriate notice. Continued use or renewal of domain services after an updated Policy takes effect constitutes acceptance to the extent permitted by applicable law.

28. Contact, Complaints and Domain Support

Customers should use the APNCloud Client Area or the official support contact for domain registration, renewal, transfer, verification, expiration, DNS, abuse, or account-control questions. Security-sensitive requests may require verification before APNCloud can disclose information or change domain settings.

General support email: [email protected]. Abuse matters should be submitted through the official APNCloud abuse-reporting channel or contact method shown on the website. Customers may also have rights to contact the registrar of record, registry operator, ICANN Contractual Compliance, or another competent authority where the issue falls within that party’s responsibility.

Appendix A — Practical Domain Lifecycle Guide

This summary is provided for convenience only. Exact timelines and fees vary by TLD, registrar, and registry, and the controlling policy always prevails.

Appendix B — Relevant External Domain Frameworks

The following external policies may apply to eligible domain names. These references are provided for transparency and may be updated by the relevant authority:

• ICANN Information for Domain Name Registrants
• ICANN Transfer Policy
• ICANN Expired Registration Recovery Policy
• ICANN Registration Data Policy
• ICANN Uniform Domain Name Dispute Resolution Policy (UDRP)

END OF DOMAIN REGISTRATION POLICY