The server implements version 1.0 of EPP protocol as defined in RFC-5730, domain name mapping (RFC-5731) and contact objects mapping (RFC-5733).


Host object mapping (RFC-5732) is not implemented as network records are attributes of each domain name in our data model (as defined in section 1.1 of RFC-5731).

It is assumed that the reader is familiar with the EPP protocol and the way EPP extensions are defined.

Details of NIC.LV EPP service

The live server is available at epp.nic.lv on the standard EPP port number 700. Transport over TCP will be used as described in RFC-5734 with TLS (Transport Layer Security) to encrypt the traffic (currently client certificates are optional) Service is allowed only from IP addresses, specified by the registrar when applying for EPP account.

We have developed some simple extensions for contact and domain objects to meet our data collection needs. Also, some restrictions take place - details are given in documentation for each EPP command.

Where to begin?

We currently do not offer a client side implementation for EPP. However, it should not be hard to develop or adapt already existing one.

If you already have experience with EPP as a registrar, then it should not be hard to adjust existing software for working with .LV domain names. You may be interested to look at extensions and learn about our data model specifics. Also, for each EPP command, the divergences from standard EPP are be outlined.

If EPP is still like an unexplored land for you, please, take a look at EPP protocol overview. Also, we strongly recommend to read the relevant RFCs and compare them with our implementation.

A quite wide choice of both commercial and free open source EPP client and toolkit software are available on the net, from simple software layers, abstracting away the complexity of the protocol into set of simple, object-oriented classes down to full-blown software to run a complete registrar system.

An EPP Sandbox environment would provide a safe play-ground for you where to develop and test your client side implementations.

XML examples

In examples, following prefixes are used for namespaced elements:

However, in server response element namespace prefixes may be different from these - namespace of the element is defined only by it’s URI.


ACE-encoded domain name
Domain name label which is encoded using only US-ASCII symbols but originally contained also Unicode characters. Are prefixed with “xn–”
International Domain Name - containing non-ASCII symbols.
NIC24 online system
online web interface for managing domain names.
Registrar’s primary person
legal person, having a registry-registrar agreement with NIC.LV, also, used as billing contact for domain names managed by the registrar

Indices and tables