www.icann.org
Open in
urlscan Pro
2606:4700::6812:25d
Public Scan
Submitted URL: https://www.icann.org/epp#clientTransferProhibited
Effective URL: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
Submission: On September 19 via api from US — Scanned from US
Effective URL: https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en
Submission: On September 19 via api from US — Scanned from US
Form analysis 1 forms found in the DOM
<form class="search-form"><label class="hidden" for="search_text">Search ICANN.org</label><input type="search" name="search_text" id="search_text" value="" placeholder="Search ICANN.org" class="SearchBox-textField searchText"><input type="hidden"
name="previous_text" id="previous_text" autocomplete="off"><input type="submit" name="commit" value="" class="SearchBox-submit" data-disable-with=""></form>Text Content
Skip to main content
* Search ICANN.org
* Log In
* Sign Up
Get Started
ICANN for BeginnersFellowship ProgramNextGen@ICANN ProgramHistory
News and Media
AnnouncementsBlogMedia ResourcesPress ReleasesGlobal NewslettersICANN News
SubscriptionsRegional Reports
Policy
Develop PolicyOperational Design Phase (ODP)Implement Policy
Public Comment
Public Comment HomeUpcoming ProceedingsOpen ProceedingsClosed ProceedingsAbout
Public CommentOther Public Consultations
Resources
Board Activities and MeetingsAccountability MechanismsRegistrarsRegistry
OperatorsDomain Name RegistrantsContractual ComplianceDomain Name Security
ThreatsPrivacy and Proxy ServicesGovernment EngagementCareersComplaints OfficeI
Need HelpICANN 25th Anniversary Photo Mosaic
Community
Engagement Calendar
Quicklinks
Board Activities and MeetingsData Protection and PrivacyDomain Name
RegistrantsEngagement CalendarIANA ServicesICANN Acronyms and TermsICANN Grant
ProgramNew gTLD ProgramPublic Technical Identifiers (PTI)Open DataQuestion About
A Domain Name?Technology @ ICANNWSIS+20 Outreach Network
Resources
*
About ICANN
* Acronyms and Terms
* Courses and Learning
* ICANN for Beginners
*
Participate
* What ICANN Does
* Effect on the Internet
* What's Going On Now
* How to Participate
*
Fellowship Program
* Committee
* Terms & Conditions
* NextGen@ICANN Program
* President's Corner
* ICANN Management Organization Chart
* Staff
* Careers
*
In Focus
* Continuity
*
DNSSEC
* Standards
* IANA DNSSEC Root Information
* TLD DNSSEC Report
* Root Deployment
* Deployment Graph
* Tools
* Training
* Key Ceremony
* News
* Blog Posts
* Presentations
* Related Sites
* GNSO Improvements
* Travel Support
* WHOIS Policy Review Team Recommendations - Implementation
*
Media Resources
* Contacts
* ICANN News
* Subscribe and Follow
* Media Assets
* Leader Bios
* About ICANN
* Strategic Initiatives
* Additional Resources
* Board Activities and Meetings
*
Accountability
*
Accountability Mechanisms
* Reconsideration
*
Independent Review Process
* Updating the IRP
*
Ombudsman
* About
* Program
* Framework
* Standards of Practice
* Respectful Communication
* Reports
* Speeches
* Links
* Questions
*
Empowered Community
* Empowered Community Administration
* Empowered Community Administration Mailing List
* Empowered Community Correspondence
* Document Disclosure
*
Reviews
* Getting Started
*
Organizational Reviews
* ALAC
* ASO
* Board
* ccNSO
* GNSO
* Nominating Committee
* RSSAC
* SSAC
* Technical Liaison Group
*
Specific Reviews
* Accountability & Transparency
* Registration Directory Service
* Security, Stability, and Resiliency
* Competition, Consumer Trust & Consumer Choice
* CCT Metrics
* Expected Standards of Behavior
* Employee Practices and Resources
* Enhancing ICANN Accountability – Work Stream 2 Implementation
*
Governance
*
Governance Documents
* Guidelines
*
Articles of Incorporation
* Current
* Archive
*
Bylaws
* Current Bylaws
* Archive
* Board Code of Conduct
* Board Conflicts of Interest Policy
* Board Statements of Interest
* Summary of Conflicts of Interest and Ethics Practices Review
* Evolving ICANN’s MSM
*
Agreements
*
NTIA IANA Functions' Stewardship Transition
* Call for Public Input: Draft Process to Develop the Proposal (8 April-8
May 2014
* Process to Develop the Proposal and Next Steps
*
Registry
* Archive
*
Affirmation of Commitments
* AOC Tracking
* ccTLD
* Partnership Memorandums of Understanding
*
Registrar
* Archive
* Annual Reports
*
Financials
* Financial Reports
* Policies, Guidelines and Procedures
* Annual Disclosure of Payments to Suppliers
* Lobbying Disclosures & Contribution Reports
*
Planning
*
Strategic Plan
* ICANN Strategic Plan for FY26-30
*
ICANN Strategic Plan for FY21-25
* Strategic Outlook Trends Program
* ICANN Strategic Plan for FY16-20
* Presentations
* RFPs
* Litigation
* Newsletter
*
Correspondence
* 2023
* 2022
* 2021
* 2020
* 2019
* 2018
* 2017
* 2016
* 2015
* 2014
* 2013
* 2012
* 2011
* 2010
* 2009
* 2008
* 2007
* 2006
* 2005
* 2004
* 2003
* 2002
* 2001
* 2000
* 1999
* 1998
* Quarterly Reports
*
Groups
* 2023 ICANN CEO Search Committee
*
RSSAC
* Charter
* SSAC
* GAC
* At-Large
* ASO
* ccNSO
* GNSO
*
Technical Liaison Group
* Technical Experts Group (TEG)
*
NomCom
* Past NomComs
* Customer Standing Committee
* Root Zone Evaluation Review Committee (RZERC)
* Business
* Civil Society
*
Complaints Office
* Complaints Report
* Domain Name System Abuse
*
Contractual Compliance
* About
*
Programs
* Approach & Process
* gTLD Registry Compliance
* Accredited Registrar Compliance
* Audit
* General Questions
* Complaint Submission & Learn More
*
Reporting & Performance Measurement
*
Notices
* Archive
* Performance Reports
* Reports
* Outreach
*
Registrars
*
Accreditation Agreement
*
Global Amendments
* 2024 Global Amendment to the RAA
* 2023 Global Amendment to the RAA
* Registrar Library
* News & Communications
*
How to Become a Registrar
* Registrar Application
* Registrar Application Instructions
* Registrar Training
*
Changes to Existing Accreditation
* Annual Registrar Compliance Certificate
* Bulk Transfers
* Data Retention Waiver
* Purchasing an ICANN-Accredited Registrar
* Registrar Data Escrow Program
* Registrar Mergers
* Registrar Name Changes
* Registrar Primary Contact Updates
* Registry-Registrar Agreement (RRA) Termination
* Renewing an Existing Accreditation
* Terminating an Accreditation
* Transferring (Assigning) an ICANN Accreditation
* Privacy and Proxy Service Providers
*
Registrar Resources
* Advisories
*
Agreements & Policies
* Policy Statement
* Billing Frequently Asked Questions (FAQ) for Registrars
* Consensus Policies
* Contact List
*
Domain Name Transfers
* Domain Name Holder FAQs
* Inter-Registrar Transfer Information
* Policy
* Operations Handbook for Registrars
* GDD Accounts and Services Team
* gTLD Lifecycle
* Naming Services portal
* Registration Data Access Protocol (RDAP)
* Registrar Data Escrow Reporting FAQ
* Registrar Data Escrow Agent Transition Resources
* Registrar Data Escrow Agent Change FAQ
* Registrar FAQs
* Security Response Waiver (SRW) Requests for Registrars
* Data Directory Services Privacy Law Conflicts
* Whois-Related Policies and Provisions
* History
*
Registry Operators
*
Advisories & Consensus Policies
* Advisories
*
Consensus Policies
*
Registration Data Policy
* Registration Data Policy Implementation Resources
*
Registry Service Evaluation Policy (RSEP)
* RSEP Implementation Notes
* Preliminary Determination of Competition Issues
* Reconciliation
* RSEP Announcements Archive
*
News & Events
* CP Summit
* ICANN News & Media
* ICANN Public Comment Page
* ICANN Public Meetings Calendar
*
Registry Agreements
*
Global Amendments
* 2024 Global Amendment to the Base New gTLD Registry Agreement
* 2023 Global Amendment to the Base New gTLD Registry Agreement
* 2017 Global Amendment to the Base New gTLD Registry Agreement
*
Registry Agreements Archive
* Proof of Concept Reports
* Terminated Registry Agreements
*
Registry Resources
* Bulk Transfers
* Data Protection and Privacy
*
Emergency Back-end Registry Operator (EBERO)
*
gTLD Registry Continuity
* Continuity Archive
* Form 6166 - U.S. Tax Residency Certification (TRC)
* Framework for Registry Operators to Respond to Security Threats
* Operations Handbook for Registry Operators
* GDD Accounts and Services Team
* gTLDs JSON Report
* List of Top-Level Domains
* Monthly Registry Reports
* Naming Services portal
* New gTLD Program
* New gTLD Program Case Studies
* New gTLD Registry Operator CSV Report
* Registration Data Access Protocol (RDAP)
* Registry FAQs
* Registry Listing Page
* Registry System Testing (RST)
* Service Level Agreement (SLA) Monitoring System API Specification
*
Services for Registry Operators
*
Assignment of Registry Agreement or Registry Operator Change of Control
*
Assignment of Registry Agreements
* Completed Direct Change of Control
* Registry Operator Change of Control
* Annual Certification of Compliance
* Continued Operations Instrument (COI)
* Centralized Zone Data Service (CZDS)
* Community gTLD Change Requests
* Cross-Ownership Notification Service
*
Data Escrow
* ICANN-Approved Registry Data Escrow Agents
* Registry Data Escrow Agent Change Requests
* Registry Data Escrow Agreement Amendments
* Registry Data Escrow Agent Application
* IDN Table Update and Publish
* Material Subcontracting Arrangement (MSA) Change
* New gTLD RA Renewals
* Registry Agreement Termination Service
* Registry Operator Name Change
*
RSEP Process
* Fast Track RSEP Process and Standard Authorization Language
* RSEP Process Workflow
* Technical Evaluation Panel
*
Registry Transition Processes
* EBERO Temporary Transition Process
* EBERO Transition Process - Communicate
* EBERO Transition Process - DNS
* EBERO Transition Process - Data Escrow
* EBERO Transition Process - RDDS
* EBERO Transition Process - SRS
* Prospective Registry Evaluation Matrix
* Registry Transition Process with Proposed Successor - Check Support
* Registry Transition Process with Proposed Successor - Communicate
* Registry Transition Process with Proposed Successor - Evaluate
* Registry Transition Process with Proposed Successor
* Registry Transition Process with Request for Proposals - Check Support
* Registry Transition Process with Request for Proposals - Communicate
* Registry Transition Process with Request for Proposals - Evaluate
* Registry Transition Process with Request for Proposals - RFP
* Registry Transition Process with Request for Proposals
* Removal of Cross-Ownership Restrictions
*
Reserved Names
*
Two-Character ASCII Labels
* Two-Character Archive
* Country & Territory Names
*
RRA Amendment
* RRA Amendment Procedure
* RRA Amendment with Temporary Specification
* Registry-Registrar Agreement (RRA) Termination
*
Rights Protection Mechanisms & Dispute Resolution Procedures
* INGO Claims Notification
* PDDRP
* PICDRP
* RRDRP
* TMCH
* TMCH Requirements
* URS
* Security Response Waiver (SRW) Requests for Registry Operators
*
Domain Name Registrants
* About Domain Names
* ICANN Policies
*
Registration Data Policies
*
WHOIS and Registration Data Directory Services
*
The Domain Name Registration Process
* Using Domain Name Registration Data
* Keeping Registration Data Accurate
* Access and the Evolution of the WHOIS System
* Domain Name Industry
* Registering Domain Names
*
Managing Domain Names
* Contact Information and WDRP
* Securely Managing Your Domain Name
* Transferring Domain Names
* Renewing Domain Names
* Rights and Responsibilities
* Spam, Phishing, and Website Content
* Trademark Infringement
* GDS Metrics
*
Identifier Systems Security, Stability and Resiliency (OCTO IS-SSR)
* IS-SSR Team Blogs
* Security Terminology
* Document Archive
*
ccTLDs
* Background Materials
* Agreements
* Delegation
* Root Zone Database
* Model MOU
* Workshops
* ICANN and ISO
*
Internationalized Domain Names
*
Root Zone Label Generation Rules (LGR)
* Generation Panel Update
* Maximal Starting Repertoire
* Proposals for Root Zone Label Generation Ruleset
* IDN Variant TLD Implementation
* LGR Toolset
* IDN ccTLD Fast Track
* IDN Implementation Guidelines
* Second-Level LGR Reference
* Resources
* Announcements and Blogs Posts
* New gTLD Program
*
Universal Acceptance Initiative
* Make your systems UA-ready
* Universal Acceptance Steering Group (UASG)
* UA Training
* UA Day
* UA Readiness Evaluations
* Announcements and Blogs Posts
*
Policy
* Policy Mission
* Policy Staff Goals
* Presentations
*
Global Addressing
* IPv6 Allocation
* ASN Allocation
* Post Exhaustion IPv4 Allocation
* New RIRs Criteria
* Review Procedures
* Policy Updates
* Operational Design Phase (ODP)
* Implementation
*
Public Comment
* Open
* Upcoming
* Archive
* Root Zone KSK Rollover
*
Technical Functions
* Tech Day Archive
*
ICANN Locations
* Report Security Issues
* PGP Keys
* Certificate Authority
* Registry Liaison
* Ombudsman
*
I Need Help
* Dispute Resolution
*
Domain Name Dispute Resolution
*
Charter Eligibility Dispute Resolution Policy
* Providers
* Rules
*
Eligibility Requirements Dispute Resolution Policy
* Providers
* Rules
*
Intellectual Property Defensive Registration Challenge Policy
* Providers
* Rules
*
Qualification Challenge Policy
* Providers
* Rules
*
Restrictions Dispute Resolution Policy
* Providers
* Rules
*
Transfer Dispute Resolution Policy
* Providers
*
Uniform Domain Name Dispute Resolution Policy
* Policy Document
* Providers
* Provider Approval Process
* Rules
* Principal Documents
* Proceedings
* Historical Documents
* Timeline
*
Name Collision
* FAQ: IT Professionals
* FAQ: Registries
* Guide for IT Professionals
* Recommendations for New ccTLDs
* Report a Problem
* Registrar Problems
* Whois Data Correction
* Independent Review Process
* Request for Reconsideration
* Document
EPP STATUS CODES | WHAT DO THEY MEAN, AND WHY SHOULD I KNOW?
Extensible Provisioning Protocol (EPP) domain status codes, also called domain
name status codes, indicate the status of a domain name registration. Every
domain has at least one status code, but they can also have more than one.
Is your domain name registration about to be dropped? Is it safely locked to
prevent unauthorized transfers, updates or deletions? Does it have any
restrictions or pending actions that you need to address? Finding and
understanding your domain's EPP status codes will answer all of these questions
and more.
It is important for registrants (that means you!) to understand EPP status codes
because they can explain why your domain may have stopped working, if it is
protected from domain name hijacking, and when and if your domain name
registration will expire and become available to the public for registration.
You can find out your domain's status codes by running a Whois lookup, which you
can do by visiting http://www.internic.net/whois.html or your registrar's
website. Your domain's EPP status codes will be included in the search results.
There are two different types of EPP status codes: client and server codes.
Client status codes are set by registrars. Some registrars automatically enact
certain status codes when you register a domain name, while others do so when
you request it. Server status codes are set by registries, and they take
precedence over client codes. Both kinds of status codes appear when you run a
Whois lookup for your domain.
The following are two tables containing the 17 standardized EPP (see std69)
domain status codes plus the Registry Grace Period (RGP) status codes (see
RFC3915). The first table lists the server and RGP status codes; the second
table lists the client status codes. These tables will explain what each status
means, why you should care what it means, and what kind of action you might want
to take to respond to a status.
SERVER STATUS CODES ARE SET BY YOUR DOMAIN'S REGISTRY
EPP Status Code RDAP Status Mapping What does it mean? Should you do something?
addPeriod
add period
This grace period is provided after the initial registration of a domain name.
If the registrar deletes the domain name during this period, the registry may
provide credit to the registrar for the cost of the registration.
This is an informative status set for the first several days of your domain's
registration. There is no issue with your domain name.
autoRenewPeriod
auto renew period
This grace period is provided after a domain name registration period expires
and is extended (renewed) automatically by the registry. If the registrar
deletes the domain name during this period, the registry provides a credit to
the registrar for the cost of the renewal.
This is an informative status set for a limited time after your domain's auto-
renewal by the registry. If you do not want to keep it (i.e., pay the renewal
fee) anymore, you should contact your registrar immediately to discuss what
options are available.
inactive
inactive
This status code indicates that delegation information (name servers) has not
been associated with your domain. Your domain is not activated in the DNS and
will not resolve.
If your domain has remained in this status for several days, you may want to
contact your registrar to request information about the delay in processing.
If the TLD requires documentation to be provided for registration, you may need
to provide the required documentation.
ok
active
This is the standard status for a domain, meaning it has no pending operations
or prohibitions.
Asking your registrar to enact status restrictions, like
clientTransferProhibited, clientDeleteProhibited, and clientUpdateProhibited,
can help to prevent unauthorized transfers, deletions, or updates to your
domain.
pendingCreate
pending create
This status code indicates that a request to create your domain has been
received and is being processed.
If the TLD is on a special registration period (e.g. sunrise), this may indicate
that the domain name will be allocated at the end of such period.
If the TLD is not on a special registration period and you are NOT the listed
Registrant, you should contact your registrar immediately to resolve the issue.
pendingDelete
pending delete
This status code may be mixed with redemptionPeriod or pendingRestore. In such
case, depending on the status (i.e. redemptionPeriod or pendingRestore) set in
the domain name, the corresponding description presented above applies. If this
status is not combined with the redemptionPeriod or pendingRestore status, the
pendingDelete status code indicates that your domain has been in
redemptionPeriod status for 30 days and you have not restored it within that
30-day period. Your domain will remain in this status for several days, after
which time your domain will be purged and dropped from the registry database.
Once deletion occurs, the domain is available for re-registration in accordance
with the registry's policies.
If you want to keep your domain name, you must immediately contact your
registrar to discuss what options are available.
pendingRenew
pending renew
This status code indicates that a request to renew your domain has been received
and is being processed.
If you did not request to renew your domain and do not want to keep it (i.e.,
pay the renewal fee) anymore, you should contact your registrar immediately to
discuss what options are available.
pendingRestore
pending restore
This status code indicates that your registrar has asked the registry to restore
your domain that was in redemptionPeriod status. Your registry will hold the
domain in this status while waiting for your registrar to provide required
restoration documentation. If your registrar fails to provide documentation to
the registry operator within a set time period to confirm the restoration
request, the domain will revert to redemptionPeriod status.
Watch your domain's status codes within this frequently defined seven day period
to ensure that your registrar has submitted the correct restoration
documentation within the time window. If this period ended and your domain has
reverted back to a redemptionPeriod status, contact your registrar to resolve
whatever issues that may have halted the delivery of your domain's required
restoration documentation.
pendingTransfer
pending transfer
This status code indicates that a request to transfer your domain to a new
registrar has been received and is being processed.
If you did not request to transfer your domain, you should contact your
registrar immediately to request that they deny the transfer request on your
behalf.
pendingUpdate
pending update
This status code indicates that a request to update your domain has been
received and is being processed.
If you did not request to update your domain, you should contact your registrar
immediately to resolve the issue.
redemptionPeriod
redemption period
This status code indicates that your registrar has asked the registry to delete
your domain. Your domain will be held in this status for 30 days. After five
calendar days following the end of the redemptionPeriod, your domain is purged
from the registry database and becomes available for registration.
If you want to keep your domain, you must immediately contact your registrar to
resolve whatever issues resulted in your registrar requesting that your domain
be deleted, which resulted in the redemptionPeriod status for your domain. Once
any outstanding issues are resolved and the appropriate fee has been paid, your
registrar should restore the domain on your behalf.
renewPeriod
renew period
This grace period is provided after a domain name registration period is
explicitly extended (renewed) by the registrar. If the registrar deletes the
domain name during this period, the registry provides a credit to the registrar
for the cost of the renewal.
This is an informative status set for a limited period or your domain's renewal
by your registrar. If you did not request to renew your domain and do not want
to keep it (i.e., pay the renewal fee) anymore, you should contact your
registrar immediately to discuss what options are available.
serverDeleteProhibited
server delete prohibited
This status code prevents your domain from being deleted. It is an uncommon
status that is usually enacted during legal disputes, at your request, or when a
redemptionPeriod status is in place.
This status may indicate an issue with your domain that needs resolution. If so,
you should contact your registrar to request more information and to resolve the
issue. If your domain does not have any issues, and you simply want to delete
it, you must first contact your registrar and request that they work with the
Registry Operator to remove this status code.
Alternatively, some Registry Operators offer a Registry Lock Service that allows
registrants, through their registrars to set this status as an extra protection
against unauthorized deletions. Removing this status can take longer than it
does for clientDeleteProhibited because your registrar has to forward your
request to your domain's registry and wait for them to lift the restriction.
serverHold
server hold
This status code is set by your domain's Registry Operator. Your domain is not
activated in the DNS.
If you provided delegation information (name servers), this status may indicate
an issue with your domain that needs resolution. If so, you should contact your
registrar to request more information. If your domain does not have any issues,
but you need it to resolve in the DNS, you must first contact your registrar in
order to provide the necessary delegation information.
serverRenewProhibited
server renew prohibited
This status code indicates your domain's Registry Operator will not allow your
registrar to renew your domain. It is an uncommon status that is usually enacted
during legal disputes or when your domain is subject to deletion.
Often, this status indicates an issue with your domain that needs to be
addressed promptly. You should contact your registrar to request more
information and resolve the issue. If your domain does not have any issues, and
you simply want to renew it, you must first contact your registrar and request
that they work with the Registry Operator to remove this status code. This
process can take longer than it does for clientRenewProhibited because your
registrar has to forward your request to your domain's registry and wait for
them to lift the restriction.
serverTransferProhibited
server transfer prohibited
This status code prevents your domain from being transferred from your current
registrar to another. It is an uncommon status that is usually enacted during
legal or other disputes, at your request, or when a redemptionPeriod status is
in place.
This status may indicate an issue with your domain that needs to be addressed
promptly. You should contact your registrar to request more information and
resolve the issue. If your domain does not have any issues, and you simply want
to transfer it to another registrar, you must first contact your registrar and
request that they work with the Registry Operator to remove this status code.
Alternatively, some Registry Operators offer a Registry Lock Service that allows
registrants, through their registrars to set this status as an extra protection
against unauthorized transfers. Removing this status can take longer than it
does for clientTransferProhibited because your registrar has to forward your
request to your domain's registry and wait for them to lift the restriction.
serverUpdateProhibited
server update prohibited
This status code locks your domain preventing it from being updated. It is an
uncommon status that is usually enacted during legal disputes, at your request,
or when a redemptionPeriod status is in place.
This status may indicate an issue with your domain that needs resolution. If so,
you should contact your registrar for more information or to resolve the issue.
If your domain does not have any issues, and you simply want to update it, you
must first contact your registrar and request that they work with the Registry
Operator to remove this status code.
Alternatively, some Registry Operators offer a Registry Lock Service that allows
registrants, through their registrars to set this status as an extra protection
against unauthorized updates. Removing this status can take longer than it does
for clientUpdateProhibited because your registrar has to forward your request to
your domain's registry and wait for them to lift the restriction.
transferPeriod
transfer period
This grace period is provided after the successful transfer of a domain name
from one registrar to another. If the new registrar deletes the domain name
during this period, the registry provides a credit to the registrar for the cost
of the transfer.
This is an informative status set for a limited period or your domain's transfer
to a new registrar. If you did not request to transfer your domain, you should
contact your original registrar.
CLIENT STATUS CODES ARE SET BY YOUR DOMAIN'S REGISTRAR
clientDeleteProhibited
client delete prohibited
This status code tells your domain's registry to reject requests to delete the
domain.
This status indicates that it is not possible to delete the domain name
registration, which can prevent unauthorized deletions resulting from hijacking
and/or fraud. If you do want to delete your domain, you must first contact your
registrar and request that they remove this status code.
clientHold
client hold
This status code tells your domain's registry to not activate your domain in the
DNS and as a consequence, it will not resolve. It is an uncommon status that is
usually enacted during legal disputes, non-payment, or when your domain is
subject to deletion.
Often, this status indicates an issue with your domain that needs resolution. If
so, you should contact your registrar to resolve the issue. If your domain does
not have any issues, but you need it to resolve, you must first contact your
registrar and request that they remove this status code.
clientRenewProhibited
client renew prohibited
This status code tells your domain's registry to reject requests to renew your
domain. It is an uncommon status that is usually enacted during legal disputes
or when your domain is subject to deletion.
Often, this status indicates an issue with your domain that needs resolution. If
so, you should contact your registrar to resolve the issue. If your domain does
not have any issues, and you simply want to renew it, you must first contact
your registrar and request that they remove this status code.
clientTransferProhibited
client transfer prohibited
This status code tells your domain's registry to reject requests to transfer the
domain from your current registrar to another.
This status indicates that it is not possible to transfer the domain name
registration, which will help prevent unauthorized transfers resulting from
hijacking and/or fraud. If you do want to transfer your domain, you must first
contact your registrar and request that they remove this status code.
clientUpdateProhibited
client update prohibited
This status code tells your domain's registry to reject requests to update the
domain.
This domain name status indicates that it is not possible to update the domain,
which can help prevent unauthorized updates resulting from fraud. If you do want
to update your domain, you must first contact your registrar and request that
they remove this status code.
ICANN is not responsible for profile content or verification of user details.
* YouTube
* Twitter
* LinkedIn
* Flickr
* Facebook
* Newsletters
* Community Wiki
* ICANN Blog
WHO WE ARE
* Get Started
* ICANN Learn
* Participate
* Diversity at ICANN
* Groups
* Board Members
* President's Corner
* Staff
* Careers
* Public Responsibility
CONTACT US
* Locations
* I Need Help
* Report Security Issues
* Certificate Authority
* Registry Liaison
* Ombuds
* Complaints Office
* Media Resources
ACCOUNTABILITY AND TRANSPARENCY
* Accountability Mechanisms
* Document Disclosure
* Independent Review Process
* Request for Reconsideration
* Empowered Community
* Employee Anonymous Hotline Policy and Procedures
GOVERNANCE
* Governance Documents
* Agreements
* Organizational Reviews
* Specific Reviews
* Annual Report
* Financials
* Planning
* RFPs
* Litigation
* Correspondence
HELP
* Dispute Resolution
* Domain Name Dispute Resolution
* Name Collision
* ICANN Lookup
* Registration Data Request Service (RDRS)
DATA PROTECTION
* Data Privacy Practices
* Privacy Policy
* Terms of Service
* Cookies Policy
© Internet Corporation for Assigned Names and Numbers.Privacy PolicyTerms of
ServiceCookies Policy
A NOTE ABOUT OUR TERMS OF SERVICE:
We have updated our electronic terms of service to provide greater transparency
and align with laws applicable to us. Learn more.
This site uses cookies to deliver an efficient user experience and to help us
see how the site is used. Learn more.OK
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include
characters used in the local representation of languages that are not written
with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can
contain Latin letters with diacritical marks, as required by many European
languages, or may consist of characters from non-Latin scripts such as Arabic or
Chinese. Many languages also use other types of digits than the European
""0-9"". The basic Latin alphabet together with the European-Arabic digits are,
for the purpose of domain names, termed ""ASCII characters"" (ASCII = American
Standard Code for Information Interchange). These are also included in the
broader range of ""Unicode characters"" that provides the basis for IDNs. The
""hostname rule"" requires that all domain names of the type under consideration
here are stored in the DNS using only the ASCII characters listed above, with
the one further addition of the hyphen ""-"". The Unicode form of an IDN
therefore requires special encoding before it is entered into the DNS. The
following terminology is used when distinguishing between these forms: A domain
name consists of a series of ""labels"" (separated by ""dots""). The ASCII form
of an IDN label is termed an ""A-label"". All operations defined in the DNS
protocol use A-labels exclusively. The Unicode form, which a user expects to be
displayed, is termed a ""U-label"". The difference may be illustrated with the
Hindi word for ""test"" — परीका — appearing here as a U-label would (in the
Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated
ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A
domain name that only includes ASCII letters, digits, and hyphens is termed an
""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a
name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."