An email address is a structured identifier used to specify an electronic mailbox or recipient within an email system. In the familiar internet form, an address contains a local part followed by the at-sign and a domain, such as alex@example.com. The local part identifies a mailbox or recipient within the relevant domain's addressing system, while the domain identifies the administrative domain responsible for handling mail. An email address is therefore an addressing identifier rather than the message itself, and it does not inherently describe the person's physical location or the device on which they read their mail.
The at-sign separates the local part from the domain part. In alex@example.com, alex is the local part and example.com is the domain. The domain can use DNS records to advertise mail servers that accept messages for it. The local part is interpreted by the mail system operated by that domain and does not necessarily correspond to a person's real name. It can identify an individual, role, department, automated service or other mailbox. Addresses such as support@example.com or invoices@example.com can therefore represent organisational functions rather than individual people.
Email-address syntax is governed by internet standards and is more complicated than the simplified format commonly shown to users. The local part can contain characters and forms that many everyday interfaces do not permit, and domain names have their own rules concerning labels and internationalisation. Some technically valid addresses may be rejected by particular software because implementations impose additional restrictions. Quoting and escaping rules can also occur in formal email syntax. Consequently, an email address that looks unusual is not necessarily invalid, while an address that looks ordinary can still fail because the domain does not exist or does not accept mail for that mailbox.
Domains are central to email addressing because they identify an administrative namespace. A domain such as example.com can publish MX records specifying servers responsible for receiving email. A domain may also use subdomains for different organisational or technical purposes. The domain component does not necessarily identify the provider through which the recipient reads messages, because organisations can use their own domains while outsourcing mail hosting to another service. The same domain can therefore have addresses managed by infrastructure physically operated by a third party.
Email addresses can represent different types of destinations. A personal mailbox may belong to one individual, while a shared mailbox can be accessed by several authorised users. Distribution lists can cause one address to deliver messages to multiple recipients. Role accounts can represent functions such as sales, support or security. Automated addresses can receive messages for software systems. Alias addresses can provide alternative names that route to the same underlying mailbox. These distinctions matter operationally because an address alone does not reveal whether one person, several people or an automated system ultimately handles the incoming message.
An email address is not the same thing as an email account. An account usually includes authentication credentials, storage, settings and other services, whereas an address is an identifier through which messages can be directed. One account can sometimes have multiple addresses or aliases, and an organisation can route several addresses to the same mailbox. Similarly, an address does not necessarily prove that a person controls it. Ownership or control is normally established through account authentication, administrative access or verification procedures rather than merely knowing the address.
Email addresses are important in security because they can be spoofed in message headers, harvested by attackers, exposed through data breaches or targeted by phishing campaigns. A message appearing to come from a familiar address does not by itself establish authenticity. Organisations can use authentication technologies such as SPF, DKIM and DMARC to reduce certain forms of domain impersonation. Users should also distinguish between the displayed sender name, the visible email address and the actual technical authentication information because these can provide different evidence about the origin of a message.
An email address is consequently a routing and identification mechanism within the email ecosystem. Its familiar structure encodes a local identifier and an administrative domain, allowing distributed mail systems to determine where a message should be sent. Addresses can identify individuals, roles, services, aliases or groups and can be hosted by organisations or third-party providers. Understanding the distinction between an address, mailbox, account, domain and mail server is important because these terms describe different components of email infrastructure even though ordinary users may use them interchangeably.
