Terms of Service

01 Agreement and Scope

Universal Domain Registry is a policy-driven domain registry. UDR allocates conditional use rights in labels beneath parent domains controlled by UDR or its partners, including ORG.YT, BIZ.WF, NAME.PM, AC.GR, SCH.TF, and SCH.WF. UDR is not ICANN, AFNIC, EETT, FORTH-ICS, or an ICANN-accredited registrar, but it voluntarily aligns its registry controls with mature registry and registrar standards where they fit a private subdomain namespace.

These Terms govern use of the UDR website, WHOIS/RDAP lookup tools, registrar portal, public forms, APIs, automation endpoints, and label-registration services. By requesting, registering, renewing, transferring, configuring, using, or benefiting from a UDR label, the registrant and any sponsoring registrar accept these Terms and all policies incorporated by reference.

• The incorporated policies include the Acceptable Use Policy, Privacy Policy, Registration Data and RDAP Policy, Dispute Resolution Policy, Reserved Name List, Prices and Pricing Policy, Premium Domain Policy and Prices, Cookie Policy, and applicable registrar or API terms.
• If a registrar, reseller, or agent requests a label for a customer, that party represents that it has authority to bind the customer to these Terms and UDR policies.
• UDR may update policies with reasonable notice where practical, but urgent changes may take effect immediately for security, upstream registry, legal, or operational reasons.

02 Conditional Registration Right

A UDR registration creates a limited, revocable, non-exclusive right to use a delegated label for the active registration period. It does not create ownership of the label, the parent domain, any top-level domain, registry database records, or registry infrastructure.

UDR may refuse an application, cancel an order, hold activation, or require extra verification when the requested label is unavailable, reserved, premium, rights-sensitive, technically invalid, misleading, high risk, or inconsistent with upstream rules.

• Registration is effective only after UDR or the sponsoring registrar confirms acceptance and the registry database marks the label active.
• Search results, availability checks, quotations, waitlists, preorders, carts, or invoices do not guarantee registration.
• A registrant remains responsible for all activity under the label, including activity by employees, contractors, hosting providers, DNS providers, email providers, and users.

03 Registrant Representations

By applying for, maintaining, or renewing a label, the registrant represents that the application data is complete and accurate, the registrant has authority to request the label, and use of the label will comply with law, UDR policies, registrar terms, and upstream registry rules.

• The registrant will not knowingly infringe or violate third-party rights.
• The registrant will not use the label for unlawful, deceptive, abusive, or security-threatening activity.
• The registrant will maintain accurate contact and technical data and promptly correct inaccuracies.
• The registrant will cooperate with UDR, the sponsoring registrar, and upstream registry requests needed to investigate abuse, verify authority, resolve disputes, or protect DNS stability.

04 AFNIC and Greece Upstream Compliance

UDR labels are private subdomain registrations beneath parent names that remain subject to upstream registry, registrar, regulator, and court authority. AFNIC and Greece Upstream Compliance means UDR may take action to preserve the standing of parent domains in .pm, .wf, .yt, and .gr even when the action affects a delegated UDR label.

• AFNIC-family labels in .pm, .wf, and .yt may be affected by AFNIC naming policies, public-order and morality principles, rights-protection procedures, and upstream registrar instructions.
• Greece-family labels in .gr may be affected by .gr assignment rules, reserved and geographic name controls, public-order requirements, EETT regulation, FORTH-ICS processes, and upstream registrar instructions.
• UDR may suspend, lock, transfer, delete, withhold, or refuse renewal of a label when upstream compliance requires it.

05 Lifecycle, Renewal, Transfer, and Deletion

Labels follow UDR lifecycle states that may include application, review, active, client hold, server hold, grace, expired, redemption, pending delete, deleted, reserved, premium, and dispute lock. UDR may publish lifecycle timelines on the registrar or API documentation page and may vary timelines by registrar channel or upstream family.

• Renewal is the registrant responsibility unless the sponsoring registrar offers auto-renewal and the registrant remains eligible, paid, and policy-compliant.
• Transfers, registrant changes, nameserver changes, and account moves may be restricted during disputes, abuse investigations, chargebacks, verification checks, premium review, or upstream holds.
• UDR may delete a label after expiration, non-payment, fraud, unrepaired policy breach, or upstream instruction. Deleted labels may return to general availability, become reserved, or become premium at UDR discretion unless law or a binding decision provides otherwise.

06 Fees, Taxes, Refunds, and Chargebacks

Prices may include base registry fees, premium fees, registrar fees, taxes, payment charges, restoration fees, transfer fees, verification fees, or special-service fees. Public pricing pages and registrar feeds control only when expressly confirmed by UDR or the sponsoring registrar.

• Registration, renewal, restoration, premium, and transfer fees are generally non-refundable after registry acceptance unless UDR confirms an error or applicable law requires a refund.
• Chargebacks, disputed payments, fraud-screening failures, or payment reversals may result in hold, deletion, or non-renewal.
• Taxes and regulatory charges are the responsibility of the registrant or sponsoring registrar unless explicitly included in the displayed price.

07 Availability, RDAP, API, and Support

UDR aims to operate reliable registry, RDAP, support, and automation services, but it does not guarantee uninterrupted access. Planned maintenance, emergency mitigation, upstream outages, provider failures, software updates, abuse response, and security events may affect availability.

• RDAP output is informational and may omit non-public personal data under privacy rules.
• API credentials, automation tokens, and registrar credentials must be protected and used only for authorized registry operations.
• UDR may rate-limit, block, revoke, or rotate access for security, scraping, inaccurate data, excessive load, or abusive usage.

08 Disclaimers and Liability Allocation

UDR provides public information, registry services, automation tools, and label delegations on an as-available basis. UDR does not warrant that any label will be available, lawful for a registrant purpose, free from dispute, free from upstream action, or suitable for a particular business model.

• UDR is not responsible for registrant content, hosting, mail, DNS provider performance, registrar billing disputes, third-party services, or upstream registry decisions outside UDR control.
• The registrant and sponsoring registrar indemnify UDR for claims, losses, costs, or proceedings arising from inaccurate data, unlawful use, rights infringement, abuse, breach of policy, or unauthorized instructions.
• To the maximum extent permitted by law, UDR excludes indirect, consequential, special, punitive, loss-of-profit, loss-of-data, and business-interruption damages.

09 Suspension, Termination, and Survival

UDR may suspend or terminate access to public tools, registrar tools, APIs, automation endpoints, or labels for breach, non-payment, security risk, false information, repeated support abuse, upstream instruction, legal request, or operational necessity. Provisions concerning fees, data, indemnity, dispute handling, liability, and policy enforcement survive termination where needed.