Web ownership & practical systems

How Domain Email Works

Lesson 11 of 25

Email can use the same domain as a website while operating on completely different servers.

That is one of the first things to understand.

Your website might live on one server while email for the same domain is handled by another company entirely.

A simplified path looks like:

Sender → Sending Mail System → DNS → Receiving Mail System → Filtering → Mailbox

Email addresses depend on domains

Consider:

support@example.com

The part after the @ identifies the domain.

DNS records for that domain help mail systems determine where messages should go and how messages claiming to come from the domain should be evaluated.

MX records

MX stands for Mail Exchange.

MX records tell sending mail systems which mail servers are responsible for receiving email for a domain.

Changing website hosting does not automatically require changing MX records.

That separation allows a website to move while email continues operating elsewhere.

SMTP

SMTP is the protocol family used for sending and transferring email.

When you send a message, mail software generally submits it to a mail system. Mail servers then communicate with other mail servers to move the message toward its destination.

Receiving and reading mail can involve other protocols and interfaces, including IMAP, POP3 and webmail.

SPF

SPF allows a domain to publish information describing which systems are permitted to send mail under that domain for SPF evaluation.

Receiving systems can compare the sending system with the published SPF policy.

SPF is useful, but it is only one part of modern email authentication.

DKIM

DKIM adds a cryptographic signature to email.

The receiving system can use a public key published through DNS to check that signature.

This helps verify that a message was signed by a system authorized for the signing domain and that signed portions of the message were not altered after signing.

DMARC

DMARC builds on SPF and DKIM.

It adds domain alignment rules, reporting and a published policy describing how receivers should treat messages that fail the relevant checks.

SPF, DKIM and DMARC work together, but they are not interchangeable.

Forwarding can complicate authentication

Email forwarding can change the path a message takes.

That can cause authentication complications, especially for SPF, because the forwarding server may not be one of the original sender’s authorized systems.

Modern mail systems have techniques for dealing with forwarding, but forwarding is one reason email delivery can become more complicated than simply “send message from A to B.”

Alias versus mailbox

An alias is an address that routes mail somewhere else.

A mailbox actually stores messages for an account.

For example:

sales@example.com

could be a real mailbox, or it could simply forward to another address.

Why branded email matters

An address such as:

name@example.com

connects communication directly to the domain.

The underlying email provider can change later while the public address remains the same if the migration is handled correctly.

That is another advantage of putting the domain at the center of the web presence.

Put This Lesson to Work

Choose a real website or project you control. Identify where this lesson applies, record who is responsible for that part, and identify one change or check you can safely make.

Worked example

For a domain-email lesson, record the separate website and email providers. Look up the existing MX records without changing them, then confirm which provider receives mail.

Your finished result

A short explanation of the system, its owner, and a checked next action. Keep passwords and recovery codes out of your notes.

Check your understanding

  • Can you explain the main idea without repeating a slogan?
  • What evidence or example supports your explanation?
  • Which decision will you make differently, and why?
Open the matching worksheet
WRUnity logo

Welcome to WRUnity

One free SpiderTaz Network account works across every network site.