Irish-Language .ie Domains: Fadas, Punycode and a Practical Launch Checklist

If your business or community organisation uses an Irish-language name, removing its fada can change how that name looks and reads. A web address should support the identity you actually use, not force an avoidable spelling compromise.

The .ie namespace supports Irish-language domains containing fadas. These are internationalised domain names, usually shortened to IDNs. Choosing one involves more than checking whether the spelling looks attractive: you also need to consider how customers type it, how your website platform handles it and which address you use for email.

This guide explains the practical decisions without promising that every checkout, mailbox or third-party app accepts the same input. Confirm IDN support with your providers before ordering or replacing an existing address. Example spellings in this article explain the technology; they are not offers of available domains.

What characters can a .ie domain contain?

The registry’s current character guidance allows letters, numbers, hyphens and the fada. Spaces are not allowed, and a name cannot begin or end with a hyphen. Uppercase and lowercase do not create different registrations.

A fada is meaningful spelling, not decorative formatting. Ask a fluent speaker or the person responsible for the brand to verify the intended word. Copying a name from a logo without checking the text can preserve a design error in the registration itself.

Check the complete label, including any hyphens and additional words. DNS length rules apply to the encoded representation as well as the user-visible name, so use a provider’s validation rather than treating a character count in a word processor as the final answer.

Unicode and Punycode are two forms of the same IDN

Unicode is the human-readable spelling containing the accented character. The DNS-compatible ASCII representation uses an encoded label beginning with xn--. The conversion is commonly called Punycode.

The registry’s IDN technical explainer illustrates this using éire.ie and xn--ire-9la.ie. Those are two representations of that example IDN, not two separate domains that must both be purchased.

That explainer dates from the 2016 rollout. Its encoding explanation remains useful, but its launch arrangements and old browser or email-provider lists should not be treated as current product compatibility promises. Test the services you actually plan to use.

Keep both representations in your private setup notes. A hosting platform may ask for the ASCII form, while marketing materials use the familiar Irish spelling. Obtain the conversion from a reputable tool or provider and verify that it converts back to the exact intended name.

The accented and unaccented spellings are separate names

An Irish-language word with a fada and the spelling without that fada are not merely two display formats of the same domain. They are distinct names. Do not assume registering one gives you control of the other.

If both are relevant to your brand, check them separately and consider the cost of maintaining each. Neither availability nor ownership should be inferred from the other. Naming rights and .ie eligibility remain separate considerations for each application.

Choose one primary website address. If you legitimately control a useful alternate spelling, configure it to send visitors to the chosen site using appropriate web redirects. Avoid publishing two identical standalone websites merely because two spellings are available.

Choose the address around real customer behaviour

Think about where people will encounter the domain. A visitor clicking a link in a social profile has a different experience from someone hearing it on a radio interview or typing it from a delivery van. Test the address in each important channel.

Ask a small group of intended users to type it from memory, copy it from a message and read it aloud. Include mobile keyboards. This is a usability check, not an argument against correct Irish spelling: it helps you decide whether an alternate address or a clearly displayed link would be useful.

Use selectable text on contact pages rather than placing the address only inside an image. Where a QR code is appropriate, test its destination and keep the written address alongside it. Customers should still have a usable route if a camera or app is unavailable.

Confirm registration and hosting support before paying

Ask the domain provider whether its ordering workflow supports your exact IDN. If a search form rejects Unicode, that does not prove the registry prohibits the name; it may indicate a limitation in that particular form. Do not repeatedly submit different spellings until one appears to work.

Ask the hosting platform which form it expects when adding a custom domain, issuing a certificate or verifying ownership. Keep screenshots or written setup instructions from the provider, but never include account credentials in a shared handover document.

For Hoster, contact support about your proposed IDN if the ordinary search or checkout does not accept it. We should confirm the supported ordering path and current pricing before you proceed; this article does not promise automatic Unicode checkout or a particular domain’s availability.

Keep email compatibility a separate decision

A functioning website on an IDN does not prove that every email product can provision or deliver mail for it. Mail hosting, sending applications, recipient systems and address-validation forms may support different combinations of internationalised addresses.

Ask your chosen email provider about the exact domain and address format. Test incoming and outgoing messages with the services your customers commonly use. Also test contact forms, booking systems, invoice tools and account-recovery emails, rather than checking only one message between two internal mailboxes.

An unaccented domain that you control may be a practical email option where compatibility is uncertain. That is an operational choice, not a requirement that an Irish-language brand abandon its spelling. Explain which address is for the website and which is for email so customers are not left guessing.

Connect DNS, HTTPS and redirects carefully

Follow the hosting provider’s specific record instructions for the encoded domain. Adding a DNS record does not automatically publish the site or issue its HTTPS certificate. Test the complete address in a browser after the provider has finished its verification.

Check the root address and any www version you intend to use. If one redirects to the other, the source may also need a valid certificate for an HTTPS request to reach that redirect. Test the accented display form and its ASCII representation to confirm they reach the same intended destination.

If an alternate unaccented domain is part of the plan, test its redirect independently. A CNAME is not an HTTP redirect. Keep email records intact if either address already carries mail, and coordinate DNSSEC if you are moving authoritative DNS providers.

Make the Irish-language site useful, not just Irish-labelled

A fada in the address is not a ranking shortcut or proof that the content serves Irish-speaking customers. Build pages that answer actual visitor questions, and clearly identify available languages. Use a fluent editor for product details, contact information and important terms.

If you publish Irish and English versions, plan the language navigation and maintenance responsibility. Visitors should be able to find the matching page where one exists, not repeatedly return to a homepage. Keep pricing, service availability and contact details consistent across versions.

Measure whether people reach the right content and complete useful actions. Search impressions, relevant enquiries and successful form submissions are more informative than assuming an IDN automatically produces extra traffic. No domain spelling guarantees search rankings.

Watch for lookalikes and recovery problems

Browsers may display an IDN as its ASCII form depending on their safety rules and settings. That display alone does not mean the domain is malicious. Nevertheless, inspect unfamiliar links carefully and do not rely only on a visual resemblance to your brand.

Protect the domain account with available authentication controls, an accessible recovery email and documented renewal responsibility. Keep a record of the exact registered name. A colleague should not have to reconstruct an encoded spelling during an urgent certificate or DNS incident.

Launch checklist

1. Verify the correct Irish spelling with a competent reviewer.
2. Confirm registry eligibility and provider support for the exact IDN.
3. Record the matching Unicode and ASCII representations.
4. Evaluate alternate spellings separately, without assuming availability.
5. Choose one primary website address and document redirects.
6. Check custom-domain and HTTPS support with the hosting platform.
7. Test email and third-party forms with the intended address format.
8. Review mobile typing, link display and language navigation.
9. Assign account recovery, renewal and content-maintenance ownership.

Frequently asked questions

Do I buy the Punycode version separately?

No. The encoded ASCII form and the matching Unicode form represent the same IDN. An unaccented spelling is a different domain, however.

Will every app display the fada?

Do not assume so. Display and validation behaviour can vary. Test the browsers, applications and communication channels important to your business.

Does an Irish-language address improve rankings automatically?

No. Choose it because it suits your identity and customers, then support it with helpful content and a technically reliable website.

Review our .ie application guide for eligibility, explore domain options, or search a conventional spelling. For an IDN-specific ordering question, speak to Hoster before completing checkout.