The .LY registry environment uses CoCCA’s Shared Registry System, a platform designed for country-code top-level domain registries. The system supports the Extensible Provisioning Protocol, better known as EPP, so authorised registrars can exchange structured domain-management commands with the registry.
For registrants, this technology works behind the scenes. You still search, register and manage your domain through a registrar such as Register.ly. EPP provides the standard technical channel used for supported transactions between the registrar and the registry.
The technology does not replace .LY policy. Eligibility rules, restricted namespaces, short-domain requirements, and manual review continue to depend on the current rules and the specific configuration of the .LY registry.
What is the CoCCA Shared Registry System?
CoCCA stands for Council of Country Code Administrators. CoCCA Registry Services develops and maintains a Shared Registry System, or SRS, used by country-code registries in several regions.
A shared registry system maintains the authoritative registration records for a top-level domain and provides controlled access to registrars and administrators. It can manage domain objects, contacts, nameserver hosts, lifecycle states, security controls, and registry reporting.
The official CoCCA deployment list identifies Libya Telecom and Technology and .LY among the country-code deployments holding an active license with support. CoCCA states that its SRS can run on the top-level domain manager’s infrastructure or as a hosted primary or backup instance.
CoCCA supplies registry technology. It should not be described as the .LY registry authority, and Register.ly should not be described as the registry.
Who performs each role in the .LY namespace?
Several organizations can be involved in one country-code domain without performing the same function.
The IANA .LY delegation record identifies the General Authority of Communications and Informatics, or GACI, as the ccTLD manager. It identifies Libya Telecom and Technology as the technical contact and lists the official .LY WHOIS and RDAP services.
CoCCA provides the software platform used for registry operations. The platform gives relevant registry administrators and authorized registrars tools to manage registration data and supported transactions.
Register.ly operates as a .LY registrar. It provides the customer-facing search, registration, and management services and communicates supported requests to the registry. Registry policy and final approval can still apply, particularly where a request requires documents or manual review.
What is EPP?
EPP is an application-layer client-server protocol for provisioning and managing objects stored in a shared central repository. The Internet Engineering Task Force defines the core protocol in RFC 5730.
EPP uses structured XML commands and responses. Instead of staff re-entering every standard request in separate systems, an authorized registrar can send a defined command and receive a machine-readable result.
The protocol includes query operations such as check, info, and poll. It also defines transform operations such as create, renew, update, transfer and delete. Object-specific standards explain how those operations apply to domain names, contacts, and host objects.
EPP is a communication standard, not a registration policy. A technically valid command can still fail if the registry’s rules, the domain’s status, or the registrar’s permissions don’t allow the requested operation.
How EPP supports .LY registrar operations
In the .LY environment, EPP can provide a consistent interface between an authorized registrar and the registry for operations enabled by the registry.
Availability checks
A registrar can check whether a name is available for registration. An available response does not guarantee approval when the name belongs to a restricted namespace, is reserved, or requires additional review.
Domain creation
A create command can submit the domain, registration period, nameservers and associated registration data. Registry validation still decides whether the supplied request satisfies the applicable rules.
Information and status checks
An info request can return registry-held information that the registrar is authorized to access. Status values help identify conditions such as transfer restrictions, server holds, or lifecycle states.
Renewals
A renew command can extend an eligible registration. The registry checks the current expiry date, permitted period, and other policy conditions before accepting the transaction.
Updates
Update commands can change supported data such as nameservers, statuses or linked objects. Sensitive contact changes and restricted namespaces may remain subject to verification outside the automated command.
Transfers
EPP provides standard transfer operations and query states. The exact .LY transfer process, authorization requirements and eligible statuses remain controlled by current .LY policy.
Deletion and restoration
Registry systems can apply configured lifecycle rules after deletion or expiration. Grace periods, redemption, and restoration should always be described using current .LY guidance rather than assuming that a generic-domain lifecycle applies.
Why the platform matters to registrants
Most registrants never connect to EPP directly, but they can benefit from a standards-based registry interface.
Faster processing for supported operations
Automated communication can reduce the time between an accepted registrar request and the corresponding registry transaction.
Fewer manual data-entry errors
Structured commands require defined fields and return defined responses. This reduces repeated manual entry, although registrants must still provide accurate information.
Clearer status information
Machine-readable statuses help a registrar explain whether a domain is active, held, pending transfer, expired or subject to another condition.
More consistent service
A standard interface makes it easier to apply the same checks and workflows across ordinary registrations, renewals and updates.
Better traceability
Transaction identifiers, responses and system auditing can help support teams investigate when a request was submitted and how the registry responded.
These are operational benefits, not guarantees that every request will be instant. Payment, eligibility, policy checks, document review and maintenance windows can still affect completion.
EPP does not remove manual review
Automation works best for standard transactions with complete and valid data. Some .LY requests still require human verification.
Restricted namespaces such as .gov.ly, .edu.ly, .sch.ly and .med.ly can require eligibility documents. Names shorter than four characters immediately before .LY require local presence and additional documentation under current Register.ly guidance.
The registrar may collect and validate the request before it is sent for further review. An EPP connection does not override the governing policy, create an entitlement to a name or guarantee approval.
EPP, RDAP, and WHOIS are different services
EPP, RDAP and WHOIS all concern domain-registration data, but they serve different purposes.
EPP is a provisioning protocol. Authorized registrars use it to submit and manage supported registry transactions.
RDAP is a registration-data access protocol. It returns structured responses for domain, entity, and nameserver queries. IANA lists the .LY RDAP service as the .LY RDAP service.
WHOIS is an older query protocol that commonly returns registration data as plain text. IANA lists whois.nic.ly as the .LY WHOIS server.
A public RDAP or WHOIS service does not provide registrar provisioning access. Likewise, an EPP connection is not a public domain-lookup service.
Security and operational controls
A registry interface controls valuable domain assets, so access requires strong operational security.
CoCCA states that its platform includes controls such as two-factor authentication, IP restrictions, API tokens, limited-validity domain authorization codes, role separation and detailed auditing. It also publishes support for EPP over TCP and related domain, host, contact, grace-period, and DNSSEC standards.
These are platform capabilities. The precise controls, extensions and commands enabled for.LY should be confirmed against the production registry configuration and registrar documentation before they are described as available.LY functions.
Register.ly must also secure its own registrar systems, staff access, customer accounts and integration credentials. Registry security and registrar security work together; neither replaces the other.
How the registry system supports GDPR and data protection
CoCCA states that its registry platform is designed to support European GDPR requirements. Its published capabilities include configurable disclosure rules based on registrar and contact location, data minimization, redaction of personal information for EU data subjects from public WHOIS responses, secure transmission and retention controls.
CoCCA’s GDPR information explains that the registry can require only one registrant contact instead of separate administrative, billing and technical contacts. It also states that submitted data is protected in transit using TLS and may be encrypted in the registry database where required. Contact objects can be retained for defined periods after they are no longer linked to a domain for policy, legal and audit purposes.
These are platform capabilities, not a statement that every .LY record is automatically hidden or that GDPR applies identically to every registrant. The actual collection, storage, disclosure, retention and deletion of .LY registration data depend on the registry configuration, applicable law, the registrant’s circumstances and the registrar’s own privacy obligations.
For Register.ly customers, this means the registry technology can support privacy-aware handling of registration data while still allowing authorized access for registry administration, the controlling registrar, legal compliance and legitimate operational needs. Customers should review the Register.ly privacy policy for information about how Register.ly processes personal data.
What this means for Register.ly customers
You do not need to understand XML or maintain an EPP connection to register a .LY domain. Register.ly handles the registrar-side integration and presents the relevant functions through its website, client area, and support processes.
Before submitting a request, you should:
- Check whether the domain appears available through the .LY domain search.
- Review the current .LY domains guide for eligibility and lifecycle information.
- Use accurate registrant and contact information.
- Prepare documents when applying for a restricted namespace or short name.
- Keep your account protected with a strong password and two-factor authentication where available.
- Contact support when the requested operation needs manual verification.
Frequently asked questions
Does Register.ly operate the .LY registry?
No. Register.ly is a .LY registrar operated by Libyan Spider. It provides registration and domain-management services and communicates with the registry through the available interfaces.
Is CoCCA the .LY registry?
CoCCA provides the Shared Registry System technology. The IANA delegation record identifies GACI as the .LY ccTLD manager and LTT as the technical contact.
Can customers connect directly to the .LY EPP service?
EPP access is intended for authorized registry participants such as registrars. Customers manage their domains through their registrar unless an official registrar-onboarding arrangement provides otherwise.
Does EPP make every registration immediate?
No. EPP can automate supported transactions, but payment, registry status, restricted namespaces, reserved names, eligibility checks and manual review can affect processing.
Does EPP replace RDAP or WHOIS?
No. EPP provisions and manages registry objects. RDAP and WHOIS provide registration-data lookup services.
Does the .LY support DNSSEC?
Yes, .LY supports DNSSEC.