This Domain Registration Policy (the “Policy”) forms part of the Terms of Service and applies to all domain name registrations, transfers, renewals, and related services obtained through NodeSpace Technologies, LLC (“NodeSpace”, “we”, “us”, “our”). Capitalized terms not defined here have the meanings given in the Terms of Service. ICANN policies and registry‑specific rules apply in addition to this Policy.

A) Ownership and Registrant of Record. Domains registered or transferred via NodeSpace are registered in the Customer’s name as the Registrant of Record. Domains registered “on behalf of” the Customer, including promotional or “free domain” offers, are owned by the Customer, not NodeSpace. Unless otherwise instructed, NodeSpace may be listed as the technical or administrative contact for provisioning purposes, but such listing does not grant NodeSpace any ownership interest.

B) Contact Data and WHOIS Accuracy. Customer must provide accurate, current, and complete Registrant, Administrative, Technical, and Billing contact data and keep it up to date. Customer authorizes NodeSpace to transmit required data to the registrar of record, registry operators, data escrow providers, and ICANN as required by the ICANN Registrar Accreditation Agreement (RAA) and applicable law. Failure to provide or verify accurate data may result in suspension, transfer lock, or cancellation.

C) New Registration and Post‑Transfer 60‑Day Lock. Newly registered domains and domains that have completed an inter‑registrar transfer are normally subject to a sixty (60) day transfer lock per ICANN’s Transfer Policy (TFRP). During this period, the domain cannot be transferred to a different registrar. Certain ccTLDs or registry rules may vary.

D) Change of Registrant and 60‑Day Lock. Changing the Registrant name, organization, or email (a “Change of Registrant”) may trigger an additional sixty (60) day inter‑registrar transfer lock per ICANN policy. By default, NodeSpace enforces this lock to protect registrants from hijacking. If permitted by the registrar and registry for the TLD, Customer may request an opt‑out of the 60‑day lock before the Change of Registrant action by opening a support ticket; approval is not guaranteed and depends on TLD policy.

E) Transfers Away. Customer may transfer a domain to another registrar subject to (i) resolution of any holds or disputes; (ii) removal of registrar lock; (iii) availability of an EPP/Auth Code; (iv) disabling of privacy/proxy where required; and (v) satisfaction of ICANN and registry eligibility requirements (including lock periods described above). All fees charged by the gaining registrar, registry, or third parties are the Customer’s responsibility. Promotional or “free” domains may be transferred away at the Customer’s expense; any refund requests for bundled services are subject to the Refunds Policy.

F) Renewals, Expiration, and Redemption. Domains may auto‑renew if enabled in the client portal and a valid payment method is on file. If a domain expires, it may enter a grace period (typically up to 30 days) during which it may be renewed at the standard renewal fee. After grace, many TLDs enter Redemption/Restore (typically 30–45 days) with additional registry redemption fees. Timelines and fees vary by TLD and registry. Once a domain is deleted and released by the registry, it may be registered by others and cannot be recovered by NodeSpace.

G) Nameservers, DNS, and Zone Management. Customer may update nameservers via the client portal, subject to registry propagation delays. If DNS hosting is provided by NodeSpace, Customer is responsible for the accuracy of zone records. NodeSpace is not liable for misconfiguration by the Customer or third parties.

H) Privacy/Proxy Services. Where available, WHOIS privacy/proxy services are optional and may be provided by a third‑party provider subject to its terms. Privacy may need to be disabled to process certain transfers. NodeSpace may disclose underlying registrant data to competent authorities or as required by law.

I) Disputes; UDRP/URS. Domain disputes are governed by the ICANN Uniform Domain‑Name Dispute‑Resolution Policy (UDRP) and, for certain TLDs, the Uniform Rapid Suspension System (URS). NodeSpace will comply with applicable orders, locks, and transfers required under these policies and by competent authorities.

J) Prohibited Uses. Domains must not be used for illegal activity, malware, phishing, spam, or other abuse. The Acceptable Use Policy applies to all domain‑related services. Registries may impose additional restrictions (e.g., residency or usage requirements for certain TLDs).

K) Fees and Refunds. Unless otherwise stated by law or registry rule, domain registration, transfer, renewal, premium domain, and redemption/restore fees are non‑refundable once processed. See the Refunds Policy for service‑level refund terms; in the event of conflict, registry/ICANN rules prevail for domain transactions.

L) Changes; Precedence. We may update this Policy from time to time. The version posted at the time of your transaction governs. In case of conflict, the order of precedence is: (1) registry rules for the TLD; (2) ICANN policies; (3) a signed order/quote; (4) the Terms of Service; (5) this Policy.