Can a business email address contain an underscore?
An underscore can be valid in the part of an email address before @, but it is not permitted in the domain part of a normal SMTP mailbox domain. Provider and form support can still vary, so a customer-facing business should prefer the simplest address it can use consistently and test the exact setup before publishing it.
For example, the underscore in quotes_team@wattleridge.example appears before @. The domain after @ contains no underscore. That placement may be valid, but technical validity does not prove that every provider, form or business app will accept the address.
Before @ and after @ follow different rules
An email address has 2 relevant parts:
- The local part comes before
@:quotes_team. - The domain part comes after
@:wattleridge.example.
RFC 5322 section 3.2.3 includes the underscore in the characters used by a dot-atom local part. That means an underscore can be valid before @.
RFC 5321 section 4.1.2 defines the normal SMTP mailbox domain using labels made from letters, digits and hyphens. It does not permit underscores there. Do not put an underscore in the normal domain of a mailbox address.
Standards syntax is only the first check. A provider may restrict which local parts it creates. A website form, CRM, booking system, accounting package or imported contact list may apply narrower validation or alter the address. This syntax-versus-workflow distinction also matters for apostrophes in business email addresses and plus signs and provider-dependent address handling.
Why an underscore may be awkward for customers
Picture Wattle Ridge Electrical giving quotes_team@wattleridge.example to a customer on a noisy call. The customer must hear “underscore”, distinguish it from a hyphen and enter it in the right place. quotes@wattleridge.example is simpler to say.
The same choice appears across quote PDFs, invoices, cards, vans and mobile forms. An underscore can be missed when someone retypes the address. It may be harder to see when linked text is underlined. A third-party form may reject it even when the mail provider accepts it.
None of that means a simpler address guarantees fewer errors, successful delivery or more enquiries. It means the public workflow has fewer details for a customer to interpret. If the visual distinction is the concern, read the separate guide to hyphens in business email addresses. For the wider naming choice, compare professional email address formats for small business.
When an underscore may still be reasonable
An underscore may be reasonable for a private or internal convention when the business already uses it and every required system accepts the exact address. Test it rather than assuming support from the standard alone.
For a public address that customers regularly hear, print or type, prefer a simpler first-name or role address when one is available. This is a practical recommendation, not an absolute ban. The right choice depends on the exact provider, forms, apps and customer workflow. If calls are common, test the address using the same conditions covered in this guide to giving an email address over the phone.
Run a harmless 6-part test
Before publishing an underscore address:
- Confirm that the provider can create or route the exact address.
- Send harmless fictional content from an unrelated inbox and confirm that it reaches the intended destination.
- Enter the address into the real website, quote, booking, CRM and accounting workflows the business uses.
- Copy it from a PDF and a mobile screen. Check that the underscore remains visible and unchanged.
- Start a test reply. Inspect the complete From and Reply-To addresses separately instead of assuming the incoming address will also be the outgoing identity.
- Record who owns the public address, routing rule and mailbox access. Set a retest trigger for any provider or configuration change.
This test proves only the exact route, provider and configuration tested at that time. It does not guarantee delivery or inbox placement.
The public address is only 1 layer. An underscore does not create a routing rule, mailbox, login, shared access, storage policy, audit history or permission to send from that address. Confirm mailbox access, storage and history separately. A successful inbound test does not prove what customers will see when the business replies.
Where Short Mail may fit
If your current public address is awkward to say, print or type, a Short Mail account manager can check whether a shorter matched .au address may fit and forward to the inbox you already use. Fit, availability, .au eligibility, setup requirements and provider compatibility are confirmed manually before anything changes.
The public address, routing, mailbox, access and storage remain separate parts of the setup. Sending permission and the From and Reply-To details customers see also require separate checks for your business.