Can a business email address contain a percent sign?

For a public-facing small business, prefer a simple role or person address that avoids percent signs—such as quotes@<short-name>.au or bookings@<short-name>.au—then test the exact setup before printing or publishing it.

Why a percent sign does not work in practice

RFC 5321 section 4.1.2 defines the normal SMTP mailbox local part using the atext character set, which does not include the percent sign character. While percent signs have historically appeared in special email routing contexts (such as source routing with user%domain@relay), they are not part of the standard character set for normal unquoted local parts that customers can type casually. A percent sign is not an allowed character in the local part of a standard unquoted email address for typical business use.

Even where percent signs might be technically permitted in legacy routing scenarios or quoted-string forms, mail providers rarely create or accept addresses containing percent signs for public use because of the fundamental conflict with URL encoding (%20 for space, %40 for @), email routing syntax, and string parsing in forms and CRMs. Website forms, booking tools, CRMs, accounting packages and imported contact lists almost universally reject addresses containing percent signs, treating the percent as a URL-encoded character introducer, routing delimiter or invalid character rather than part of the literal address.

When customers see an address containing a percent sign—such as sales%info@example—they typically interpret it as a URL-encoded character sequence, a typing error, or incomplete technical syntax. The percent sign's role as the introducer for URL-encoded characters (%20, %2B, %40) is so entrenched that using it inside an address identifier creates ambiguity at every point in the workflow. The same workflow concerns that make giving an email address over the phone challenging are amplified when a percent sign is part of the address.

What customers see and type

Picture a business telling a customer: sales%info@<short-name>.au. The customer hears "sales percent info at ..." and writes down what sounds like a URL-encoded string, a mathematical expression, or a typing error. When dictated over the phone, customers may write "percent" as a word, replace it with a hyphen or period, omit it entirely, or type only the parts before and after the percent sign as separate addresses.

Now imagine the same address on a printed invoice, quote PDF, business card or van sign. The percent sign is visible, but it looks like it begins a URL-encoded character sequence (%20, %40), marks a mathematical percentage, or resembles a typing error. When a customer retypes the address from a mobile screen or physical paper, they may skip the percent sign, type the word "percent" literally, replace it with a hyphen or period, or assume the address is incomplete and add what they think should follow the percent.

This variability does not mean every customer will mistype the address. It means the percent sign introduces an interpretation choice where none would exist if the address were sales@<short-name>.au, info@<short-name>.au, or bookings@<short-name>.au instead. The visual association between % and URL encoding creates an additional layer of confusion—customers familiar with web addresses may interpret sales%info as an incomplete encoding rather than a literal email address.

Form validation and CRM import rejection

Most email validation libraries and form validation tools reject percent signs in email addresses outright because percent signs are not part of the standard unquoted local-part character set defined in RFC 5321 section 4.1.2 and are reserved as the introducer for URL-encoded characters. Even validation that permits special characters in certain contexts typically excludes or mishandles percent signs because of their role in URL encoding, legacy email routing syntax and string literal parsing.

Website contact forms, CRM imports, booking systems, accounting packages and quote generators often treat a percent sign as a URL-encoding introducer or routing delimiter. An address like sales%info@example entered into a form may be rejected with an error message like "Invalid email address", interpreted as a URL-encoded string and decoded incorrectly (for example, treating %20 as a space), truncated at the percent sign (keeping only sales), stripped of the percent sign (turning it into salesinfo@example), or flagged as invalid characters.

The business may not see the alteration until a reply to a stored address bounces or goes missing. A customer who enters sales%info@example into a website form may receive no confirmation, an error requiring them to re-enter the address in a different format, or the form may strip or incorrectly decode the percent sign during validation and store a different address than the one printed on the card.

URL parsers, link detection in email clients, and automatic hyperlinking in web forms will typically fail or behave unpredictably when encountering an email address containing a percent sign. Contact lists, CRMs and automated systems that attempt to validate, link or process email addresses often reject addresses containing percent signs because they conflict with URL-encoding rules and email routing syntax.

Confusion with URL encoding

The primary source of confusion with a percent sign in a business email address is that percent signs are universally used as the introducer for URL-encoded characters. When someone sees sales%info@<short-name>.au, they naturally interpret it as an incomplete URL-encoded string (like sales%20info for "sales info" with a space, or user%40domain in legacy routing contexts), a mathematical percentage expression, or a typing error.

This interpretation is reinforced by everyday web browsing where %20, %2B, %40 and similar sequences encode spaces, plus signs, @ symbols and other special characters in URLs. Customers who see an address with a percent sign will typically assume they are looking at a URL fragment, incomplete encoding syntax, or a typing error, and will either drop the percent sign, type what they think should follow it (like %20), or replace it with a simpler separator.

Even when a customer carefully types the percent sign as shown, web browsers, email clients, CRM tools and form validators may interpret the input as a URL-encoding introducer. An address like mailto:sales%info@example may fail to parse correctly because the percent conflicts with URL-encoding rules. Link detection algorithms and automatic hyperlinking will often reject or misparse addresses containing percent signs.

Additionally, some legacy email routing systems used percent signs in source routing syntax (such as user%domain@relay), where the percent sign instructed the relay server to forward the message to user@domain. While this syntax is obsolete and not used in modern public email addresses, the historical association with routing adds another layer of ambiguity to addresses containing percent signs.

Print and signage: looks like URL encoding or a percentage

When printed on a business card, invoice, quote PDF, van sign, or website footer, a percent sign in the email address creates immediate visual confusion. To most readers, the percent sign signals a URL-encoded character introducer (%20, %40), a mathematical percentage (25%), or a typing error—not a literal character that must be included in the address.

The same address that is rejected or misinterpreted in a web form becomes even more problematic when printed on physical materials. A customer looking at sales%info@<short-name>.au on a business card, invoice header, or van sign may:

Drop the percent sign entirely, typing salesinfo@<short-name>.au.

Interpret the string as a URL fragment and expect additional characters after the percent.

Type the word "percent" literally, resulting in salespercentinfo@<short-name>.au or similar.

Replace the percent sign with a hyphen, period, or space.

Assume the address is incomplete or contains a typing error and contact the business to confirm the correct address.

The risk is not that every customer will make one of these errors—it is that the percent sign introduces multiple plausible interpretations where a simpler address like sales@<short-name>.au or info@<short-name>.au would be unambiguous.

Safer alternatives for public-facing business addresses

For a public-facing small business, the simplest and most reliable approach is to choose a role or person address that avoids percent signs entirely. Addresses like quotes@<short-name>.au, bookings@<short-name>.au, sales@<short-name>.au, or info@<short-name>.au work across all forms, CRMs, email clients, printed materials and phone dictation without introducing URL-encoding or routing-syntax confusion.

If the business currently uses a longer address and is considering a shorter matched .au address as an alternative, the key advantage is that shorter addresses are easier to say, print, type and remember—without requiring any special characters that conflict with URL-encoding or legacy routing syntax. A shorter .au address can forward to the existing inbox (subject to setup and approval), so the business does not need to abandon the existing address or change the website immediately. An account manager confirms fit, availability, .au eligibility requirements, setup steps and provider compatibility manually before anything changes.

How to test before you publish

Before printing a business email address on cards, invoices, quotes, van signs or website footers, test the exact address through the full workflow:

Send a test email from a personal account (Gmail, Outlook, etc.) to the address and confirm that the email arrives in the intended inbox within a few minutes.

Enter the address into the business website contact form (if one exists) and confirm that the form accepts the address, sends a confirmation, and that the confirmation arrives at the intended inbox.

Import the address into a CRM or contact list (such as HubSpot, Salesforce, Mailchimp, or a spreadsheet) and confirm that the address is stored correctly without being rejected, decoded, stripped or altered.

Create a test invoice or quote PDF containing the address and ask a colleague or friend (who was not involved in choosing the address) to type the address into their email client from the printed or on-screen PDF. Confirm that they type it correctly without assistance.

Dictate the address over the phone to a colleague or friend and ask them to write it down and type it into their email client. Confirm that they can do so without requiring spelling assistance, clarification, or corrections.

If any step reveals that the address is rejected, altered, mistyped, or misunderstood, adjust the address before printing or publishing it. Testing the exact workflow before committing to printed materials or public listings prevents costly reprints, customer confusion and missed communications.