Why Mailto URIs Have No Host

Understanding the syntax difference between hierarchical URLs (like https://) and opaque URIs (like mailto:).

Opaque vs. Hierarchical URIs

URI specifications (defined in RFC 3986) categorize addresses into two structural categories:

Hierarchical URIs: These schemes (like http, https, ftp) use a double slash // to demarcate an authority component (a host/domain or IP address). Example: https://example.com/index.html
Opaque URIs: These schemes (like mailto, tel, urn) do not have a hierarchical structure, nor do they define a specific hostname authority. They represent an address target directly. Example: mailto:[email protected]

Adding double slashes to a mailto link is an invalid URI syntax under RFC 6068 specifications.

❌ INCORRECT SYNTAX

<a href="mailto://[email protected]">

Adding double slashes causes mail handlers to treat [email protected] as a hostname authority.

✅ CORRECT SYNTAX

<a href="mailto:[email protected]">

Standard syntax directly specifies the recipient box without slashes, ensuring universal client parser compatibility.

When operating systems try to resolve a link starting with mailto://, they parse the string incorrectly. For instance:

Outlook desktop may crash or fail to resolve the target inbox.
Browser mail handlers might treat the domain extension (e.g. .com) as a port parameter and drop the email.
Mobile iOS/Android web views may ignore the handler call entirely.

To ensure your mailto links work universally without triggering OS default handler errors, use standard formatting rules.