Skip to main content
miji.be

Homograph Attack

A phishing technique that uses visually similar Unicode characters to impersonate a legitimate domain. Extremely difficult to detect by eye.

Aug 25, 2026 / About 1 min read

Security

A homograph attack (also called an IDN homograph attack) exploits visually identical or near-identical Unicode characters to forge a domain name that looks like a legitimate one. For example, the Latin letter "a" (U+0061) and the Cyrillic letter "a" (U+0430) are indistinguishable to the human eye but are treated as different characters by computers.

A concrete example: replacing the Latin "a" in "apple.com" with a Cyrillic "a" produces a domain that looks identical but resolves to a completely different server. In 2017, security researcher Xudong Zheng demonstrated this technique and drew widespread attention.

Internationalized Domain Names (IDN) make this attack possible. IDN allows non-ASCII characters (Japanese, Arabic, etc.) in domain names by converting them internally to Punycode (strings starting with xn--). Browsers display the Unicode form in the address bar, making spoofed domains hard to spot.

Shortened URLs face a double risk from homograph attacks. First, the short URL service's own domain could be spoofed with homograph characters. Second, the redirect destination registered in a short URL could be a homograph phishing site. Short URL services are also expected to reject destinations that turn out to be spoofed domains, though visual similarity alone cannot be turned into a mechanical dividing line.

Major browsers defend on the display side, but the conditions for falling back to Punycode differ between them. The display policy Chrome publishes covers not only domains that mix confusable scripts, but also confusable names written entirely in a single script, and names that match a top domain once confusable characters are folded into a common form. Firefox centres on allowing Unicode display when the registry of the top-level domain has stated its own countermeasures, and treats spoofing that replaces every character within one script as something the display side cannot prevent, leaving it to whoever accepts the registration. The case that drew attention in 2017 was written entirely in Cyrillic precisely because that shape slipped past checks relying on script mixing. Seeing Unicode in the address bar is not proof that the domain is legitimate.

Was this article helpful?

Related Terms

Phishing

A cyberattack that uses deceptive links and websites to trick users into revealing sensitive information.

URL Encoding

URL encoding (percent-encoding) converts special characters into percent-encoded sequences (%XX) safe for use in URLs. Essential for handling spaces, Unicode characters, and reserved symbols in web addresses.

Percent-Encoding

A mechanism for encoding special characters in URLs by replacing them with a percent sign followed by hexadecimal digits.

HTTPS

The secure version of HTTP that encrypts data transmitted between a browser and a web server using TLS.

SSL/TLS

Cryptographic protocols that provide secure communication over the internet by encrypting data between client and server.

Internationalized Domain Name

A domain name containing non-ASCII characters (Japanese, Arabic, etc.). Internally converted via Punycode but carries homograph attack risks.

Related Articles

Short URL Phishing - How to Spot Scams and Protect Yourself from Malicious Links

Learn to identify phishing attacks that use short URLs. Covers 5 common scam patterns, URL preview tools, and practical defense strategies.

How to Spot Suspicious URLs - 5 Checkpoints to Avoid Getting Tricked

A beginner-friendly guide to spotting phishing scams. Learn 5 easy checkpoints including the https padlock, domain reading tricks, and short URL safety.

How Link Previews Work and Their Security Risks - Safe Operation of Short URLs

Explore the technical mechanisms behind link previews (OGP) generated by SNS and chat apps, and the security risks that arise through short URLs. Learn about preview spoofing attack techniques and defense strategies.

FAQ

How can I spot a homograph attack?
Visual detection is extremely difficult. Check the browser address bar: if Punycode (a string starting with xn--) appears, the browser has fallen back to the safer display, which is a cue to doubt that domain. Note that legitimate internationalized domain names can also appear as Punycode, so Punycode display is not by itself proof of spoofing, and Unicode display is not proof of safety either. You can also paste the URL into a text editor and inspect the character codes.
Can Japanese domains be used in homograph attacks?
Yes. Some Japanese kanji and Chinese hanzi look identical but have different Unicode code points, making them exploitable. Browser defenses have improved but are not foolproof.
Can URL shortening services detect homograph attacks?
Short URL services do turn away destinations that look dangerous at registration, but judging strings that merely look alike is hard to mechanize, so nothing removes every case. Work on the assumption that the destination domain still needs checking on the side that opens it.

Put the terms to work

Shorten a URL for Free