Emoji in domain names (and Punycode)

Yes, emoji domain names exist (☕.example). Under the hood they're converted to plain ASCII via “Punycode.” But they come with real caveats — support is spotty and there are security concerns.

How it works: Punycode

Domain names must be ASCII at the protocol level, so Unicode domains (including emoji) are encoded with Punycode into an xn-- prefixed ASCII string. Browsers convert between the pretty Unicode form and the xn-- form behind the scenes.

Why they're risky

  • Most registries (including .com) don't allow emoji domains at all — only a few TLDs do.
  • Rendering is inconsistent across browsers and apps.
  • Homograph attacks — lookalike Unicode characters can impersonate real domains, so browsers often show the xn-- form as a safety measure.

The verdict

Fun for a novelty link, poor for a real brand. Use a normal domain and put the emoji in your content, not your address.

Frequently asked questions

Can a domain name contain emoji?

Only under certain TLDs — .com and most major registries don't allow it. They're encoded via Punycode when permitted.

What is Punycode?

An encoding that represents Unicode domain names as ASCII xn-- strings so the DNS system can handle them.