Registry Registrar Agreement

01 Appointment and Authority

This Registry Registrar Agreement governs registrar access to UDR label registration services, APIs, EPP-style workflows, WHOIS/RDAP correction processes, support channels, and automation hooks. A registrar may sponsor labels only after UDR accepts the registrar, completes onboarding, and issues credentials.

• The registrar remains responsible for its customers, resellers, employees, API users, and systems.
• The registrar must make UDR policies binding on registrants before submitting or renewing any label.
• UDR may suspend registrar access for security risk, unresolved abuse, non-payment, inaccurate data, policy breach, or upstream registry instruction.

02 Required Registrant Terms

Each registrar must maintain customer terms that, at minimum, require accurate registration data, lawful use, compliance with UDR policies, acceptance of registry holds and dispute locks, consent to RDAP publication as described in the Privacy Policy, and cooperation with abuse and rights investigations.

• Registrant terms must prohibit DNS Abuse, illegal activity, fraudulent or deceptive practices, malware, botnets, phishing, pharming, spam used to deliver abuse, piracy, counterfeiting, and rights infringement.
• Registrant terms must disclose premium pricing, renewal pricing, expiration behavior, restoration charges, and transfer limits before purchase where applicable.
• Registrar must preserve evidence that the registrant accepted current UDR policies.

03 Technical Integration and Security

Registrar systems must meet UDR technical and security requirements for API authentication, rate limits, command format, contact data, nameserver syntax, DNSSEC material, transaction logging, error handling, and webhook use.

• Credentials must be unique, protected, rotated when compromised, and used only by authorized systems.
• Registrar must maintain audit logs for orders, renewals, transfers, status changes, data changes, abuse actions, and support instructions.
• Registrar must notify UDR promptly of credential compromise, material API errors, suspicious registration patterns, or a security incident affecting UDR labels.

04 Registration Data, RDAP, and Accuracy

Registrar must collect, validate where required, protect, update, and transmit registration data needed for registry operation, RDAP publication, dispute handling, abuse response, billing, and upstream compliance.

• Registrar must maintain a process for registrants to correct inaccurate data and must update UDR data without undue delay.
• Registrar must respond to UDR accuracy inquiries, lawful disclosure requests, and RDAP correction requests within stated deadlines.
• Registrar must not submit placeholder, proxy, false, or intentionally incomplete data unless the relevant privacy or proxy service is lawful, disclosed, and reachable.

05 Abuse Desk and Mitigation

Registrar must maintain an abuse contact capable of receiving and acting on reports every day. For well-evidenced DNS Abuse, registrar must take appropriate mitigation actions reasonably necessary to stop or disrupt abuse and must coordinate with UDR where registry-level action is needed.

• Critical abuse reports require urgent triage and clear communication to UDR.
• Registrar must preserve evidence and explain actions taken, including takedown, suspension, customer notice, no-action rationale, or escalation.
• Repeated abuse or poor response quality may trigger registrar program review, volume limits, manual approval, credential suspension, or termination.

06 Fees, Settlement, Taxes, and Chargebacks

Registrar is responsible for registry fees, premium fees, renewal fees, restoration fees, transfer fees, taxes, chargebacks, and other charges according to the active price schedule, registrar addendum, invoice, or API quote.

• UDR may require pre-funding, credit limits, auto-debit, or manual review for high-risk orders.
• Registrar must clearly disclose retail pricing, premium status, renewal pricing, taxes, and refund rules to registrants.
• Non-payment or chargebacks may result in holds, service suspension, deletion, or registrar account restrictions.

07 Audits, Records, and Compliance Review

UDR may request records reasonably needed to verify policy acceptance, registration authority, data accuracy, abuse response, payment status, or upstream compliance. Registrar must cooperate with audits and keep relevant records for a commercially reasonable period.

• UDR may impose corrective action plans, registration limits, manual review, or suspension after material compliance failures.
• Registrar must cooperate with upstream registry inquiries, dispute-provider instructions, court orders, and competent-authority requests affecting sponsored labels.
• Confidential information must be protected and used only for authorized registry purposes.

08 Termination, Transition, and Survival

Either party may terminate according to the executed registrar agreement or addendum. UDR may terminate or suspend immediately for severe abuse, security compromise, insolvency risk, sanctions concern, fraud, repeated policy breach, or upstream instruction. After termination, UDR may move labels to another registrar, place them under direct management, or require registrant transition notices.