Registrant floor
- Version
- v1
- In force since
- Not yet
- Next review
- At adoption
- Snapshot
- None yet
- Adopted by
- Proposed for founding adoption
- Signature
- At adoption
- Log entry
- Not appended yet
- Binding text
- English
Proposed, not in force
Open for comment until 28 October 2026, 00:00 UTC. Nothing here binds anyone until it is adopted.
Scope
This policy sets the least every TLD owes its registrants. A TLD may give more, never less. A test TLD, in which the GOpenCDR terms promise registrants nothing, is outside it.
Registrant data
Registering a name needs an account with a verified email address, and nothing more unless the TLD policy names it under P-4 4.4.
Rule registration.verified_email.
RDAP answers for a name with its status, dates, nameservers and DNSSEC data, and redacts everything about the registrant with RFC 9537 markers. There is no bulk access, no search by registrant and no reverse lookup. A contact form relays messages to the registrant without disclosing their address.
Rule rdap.redaction.
Redacted data is disclosed only under the registration data disclosure policy, or under a stricter policy of the TLD.
Keeping a name
A free name is kept by confirming the account's email address once every 12 monthsfloor. One confirmation covers every name the account holds.
If the confirmation does not arrive in time, the names get 30 daysfloor of grace, in which they keep resolving, and then 30 daysfloor of redemption, in which they leave their zones but stay registered. Confirming restores them until redemption ends; then the registrations end. The registrant is mailed before each step.
A TLD that charges for names says so in its policy, and its renewal rules apply there in place of 3.1 and 3.2.
A registration is the right to use a name for as long as it is kept up. It is not property. It moves to another account only by a transfer on the registrant's instruction, where the TLD allows transfers.
Changes
A TLD change that restricts registrants takes effect at least 30 daysfloor after it is published, and registrants are mailed. A change that loosens takes effect at once.
Registrants accept each binding version of the policies that apply to their names before they take a new action. A new registration, a transfer or a change waits until they have; renewals and deletions never wait.
Rule policy.acceptance. Limits: Never pauses a renewal or a deletion.
Restrictions and appeals
A name is held, locked, suspended or deleted only for DNS abuse under P-8, a binding order of a court or an authority, a breach of the terms, or a decision under the name dispute policy, and never because of what a site under it says. A person takes every such decision; automated checks only find candidates. Withdrawal under P-1 and the steps of 3.2 run on their own.
A registrant whose name is restricted gets a statement of reasons and may challenge the decision within 6 monthsfloor. A person who did not take the decision reviews it and answers with reasons.