EPP Codes and Client Authorisation for Bulk .ie Domain Transfers

An EPP code, called an Authcode by the .ie registry, is a unique authorisation code associated with an individual domain that enables its transfer to another registrar, so each registration in a client portfolio needs the correct corresponding code before submission.

EPP stands for Extensible Provisioning Protocol, the system registrars use to communicate registration changes to registries. Clients may encounter labels such as “transfer code”, “authorisation code” or “Authcode” when requesting the same transfer credential.

The .ie registry’s published process requires the customer to supply the Authcode to the receiving registrar. An agency should therefore coordinate the request with the client rather than assume the new provider can independently retrieve every code. IE Domain Registry

Treat the code as a sensitive credential. Use an agreed secure channel, restrict access to staff handling the transfer and avoid including live codes in widely shared project documents.

Clients can request Authcodes from their current registrar or the .ie registry’s Registration Services team, then provide them securely for the agreed transfers, with agencies coordinating requests by provider while keeping each code matched to its domain and the relevant client approval.

The registry can be contacted at registrations@weare.ie. It sends codes to the email addresses recorded for the Registrant Contact and Administrative Contact and does not issue them by telephone. This makes contact access an early preparation task. .IE

For a portfolio spread across several providers, use this sequence:

• Confirm the inventory: list each domain, client, current registrar and renewal date.
• Check contact access: establish who can receive the relevant messages.
• Record client instructions: identify the destination provider and agreed scope.
• Coordinate code requests: group work by current provider without mixing clients’ credentials.
• Submit approved domains: investigate incomplete entries separately.
• Record completion: confirm the new registrar, renewal date and management arrangements.

If a code is rejected, check the domain-to-code pairing and accidental spaces before requesting a replacement. Resolve the specific error rather than repeatedly resubmitting the same details.

For a straightforward .ie registrar transfer, the published registry process centres on the domain’s Authcode, while agencies should also retain written client instructions and confirm any provider-specific checks, particularly where contact details are outdated, authority is unclear or the registered holder needs changing.

Do not assume every transfer requires a fresh set of documents used for initial .ie domain registration. Equally, do not promise that a code will resolve disputed authority or inaccurate registration details. Ask the receiving registrar what evidence is needed for those exceptions.

As a practical agency record, capture:

• Client identity: the business or person holding the registration.
• Approving contact: their name, role and verified contact details.
• Domain scope: the exact registrations covered by the instruction.
• Destination: the receiving registrar and intended management account.
• Financial approval: transfer and renewal charges, quoted in € with VAT treatment clear.
• Service scope: whether DNS, hosting and email changes are included or excluded.

A useful instruction is specific: permission to transfer listed registrations to a named provider, preserve the registered holder and retain existing nameservers unless separately approved.

This is an operational recommendation, not a universal registry form. Follow any additional verification requirements supplied by the registrar.

Confirm costs before collecting approvals. The .ie registry states that a registrar transfer requires a renewal payment, including advance renewal where the domain is not yet due. weare.ie

If a former employee or previous supplier remains the Administrative Contact, establish the correct update process before proceeding. The .ie registry requires this role to identify a named person; ask the current registrar what supporting information it needs to make the change.

An old invoice or access to the website may help explain the history, but neither should replace proper verification of the client’s authority.

A registrar transfer changes the provider managing the registration. Changing the registrant changes the registered holder and follows a separate process. Updating the Administrative Contact is another distinct action. SmartHost’s guidance explicitly separates contact updates from ownership changes. SmartHost

An agency can manage a client’s domain without becoming its registered holder. Keep that distinction visible in the transfer record and future handover arrangements.

Permission to transfer a registration should not be treated as blanket approval to rebuild DNS or migrate business email hosting.

Record the existing nameservers and identify who supplies authoritative DNS. If DNS is bundled with the outgoing provider, confirm whether that service continues after transfer.

Where DNS must move, preserve the complete zone, including MX records for mail delivery, SPF records, DKIM records and DMARC policy. DNS propagation becomes relevant when DNS information changes; moving the registration does not itself move a website or mailbox.

Also check whether a registry lock or another transfer restriction needs a separate release procedure. These controls are distinct from email authentication records.

SmartHost is an accredited .ie registrar. Its published process accepts the domain’s Authcode during ordering, handles the transfer after payment and provides confirmation when it completes. Transferred domains can then be managed through the customer portal. SmartHost Knowledgebase

For an agency portfolio, begin with the domain inventory and any known exceptions. Agree the submission method, client account arrangements and DNS responsibilities with our team before sending credentials.

The business value comes from making each registration traceable: the right client, the right approval, the right code and a clear completion record.