You get a secure email address in three moves. First, lock the account so only you can sign in. Second, pick a provider whose storage matches what you’re protecting. Third, if the address is on your own domain, add the DNS records that stop anyone else sending as you. The first move matters most, and it works on any provider. The third is the part most guides skip, and it’s the one that protects your clients from mail that only looks like yours.
- The account is where most break-ins happen. A unique password and a passkey or security key close that door.
- The provider decides who can read stored mail. Gmail and Outlook can. Proton and Tuta are built so they can’t.
- The domain decides who can send as you, and whether the address stays yours when you change provider.
This page walks through each, with the domain side in full. Who sells secure email, and what each kind of company protects, is covered elsewhere in this set and linked where it comes up.
How do I get a secure email address?
Here’s the order that does the most good first.
- Use a password that lives nowhere else. Keep it in a password manager.
- Turn on two-step verification. A passkey or security key is stronger than a text-message code, because it can’t be phished.
- Set a recovery address and phone you control. Keep them current. More on why this matters for a domain address below.
- Choose the provider for what you protect. If the worry is a stranger reading your mail, any major provider with step 2 done is sound. If the worry is the provider itself or a court order for content, choose a zero-access provider. The models are compared in what secure email means.
- Put the address on a domain you own, if it’s for a business or you want it for life. Then set MX, SPF, DKIM and DMARC as described below.
- Use aliases so each site or list gets its own address.
The account steps are set out in more detail in how do I create a secure email. The rest of this page is about steps 5 and 6.
How email works, and where your domain comes in
A message crosses at least two companies’ servers on its way to someone. Your domain is read at nearly every step.
- You press send. Your provider’s server takes the message.
- Your server looks up the recipient’s domain in DNS. It wants the MX record, which names the server that takes mail for that domain. The SMTP standard, RFC 5321, describes this as resolving “a destination domain name to either an intermediate Mail eXchanger host or a final target host.”
- The two servers connect. If both support it, they encrypt the connection with TLS.
- The receiving server checks who really sent the message. It reads your domain’s SPF, DKIM and DMARC records to decide.
- The message is stored in the recipient’s mailbox, where their provider’s rules apply.
Two things follow from that trip. Your provider protects the message while it holds it. Your domain’s records decide whether the other end believes the message is yours, and whether it insists on encryption on the way in.
There’s one gap in step 3 worth knowing. Google’s own Workspace documentation says that “if a TLS connection can’t be created, servers often send the message anyway.” A record called MTA-STS closes that gap for mail coming to your domain. It’s in the table below.
Your own domain or the provider’s
An address like you@gmail.com or you@proton.me sits on the provider’s domain. An address like you@yourfirm.com sits on yours. Both can be secure. They differ in who controls what.
| Address on the provider’s domain | Address on your own domain | |
|---|---|---|
| Who sets SPF, DKIM and DMARC | The provider, already done | You, at your DNS host |
| If you change provider | The address stays behind | You change the MX record and keep the address |
| If the provider closes your account | The address is gone | You point the domain somewhere else |
| Aliases | What the provider’s plan allows | As many as your plan allows, plus catch-all on many hosts |
| A second account to protect | No | Yes, the registrar account |
| Cost | Free plans exist | A paid plan on most secure providers, plus the domain |
The cost row is real on secure providers. Proton’s plans page lists custom domains under Mail Plus, not the free plan. Its custom domain page says “All paid plans support adding custom domains.”
The portability row is the reason most firms choose their own domain. The address on your business card outlives any provider. Who owns an address, and what that means if you ever leave, is set out in can you keep your email address. Whether a move is worth making at all is its own decision, and what a more secure provider would actually buy you walks through it.
The records that make a domain address secure
Every record below lives at your DNS host, which is often your registrar. Your mail provider gives you the values. You paste them in. Most hosts publish them on a setup page, and Proton’s asks for a verification record, MX, SPF, DKIM and DMARC.
| Record | What it does | What goes wrong without it |
|---|---|---|
| MX | Names the server that accepts mail for your domain | Mail to your address doesn’t arrive |
| SPF | Lists the servers allowed to send as your domain | Receivers can’t tell your servers from a forger’s |
| DKIM | Signs each message so a receiver can check it wasn’t altered | Mail is easier to forge, and more of yours lands in spam |
| DMARC | Ties SPF and DKIM to the visible From address, and tells receivers what to do when a message fails | Forged mail in your name still reaches your clients |
| MTA-STS, with TLS-RPT | Tells senders to deliver to you only over verified TLS, and sends you reports when that fails | Mail to you can fall back to an unencrypted connection |
The FTC’s small business guidance puts the first three plainly:
Without email authentication, scammers can use your domain name to send emails that look like they’re from your business.
NIST’s Trustworthy Email guidance recommends the same three. The FTC adds that if your host won’t set them up, “consider taking your business elsewhere.” What a forged message in your name looks like, and why it costs firms money, is in what is email spoofing.
There’s also a sending reason to set them. Gmail’s sender guidelines, in effect from February 1, 2024, require SPF or DKIM from everyone who sends to Gmail. Proton’s setup page says that without these records, “your messages may be rejected or sent to spam by major email providers like Gmail.”
SPF: one record, and a limit of ten lookups
Your domain gets one SPF record. If you send from more than one service, such as your mail host and a newsletter tool, they all go into that single record. The SPF standard, RFC 7208, caps how far a receiver will follow it:
SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation, to avoid unreasonable load on the DNS.
Each “include” of another service counts toward the ten, and some services use several. Go over the limit and the check fails outright. If you add a fourth or fifth sending tool, check the count.
DMARC: start by watching, then enforce
DMARC has three policies. The specification, RFC 7489, defines the strictest this way:
The Domain Owner wishes for Mail Receivers to reject email that fails the DMARC mechanism check.
A policy of none only reports. Quarantine sends failing mail to spam. Reject stops it at the door. Here’s the usual path:
- Publish p=none with a reporting address. Receivers send you daily summaries of who is sending as your domain.
- Read two to four weeks of reports. Look for real services you forgot, like a billing tool or a scanner that emails PDFs. Add each one to SPF, or set up DKIM for it.
- Move to p=quarantine. Proton recommends this for most domains.
- Move to p=reject once the reports show only mail you recognize.
A domain you own but never send from should go straight to reject. Forgers like quiet domains, because nobody is watching them.
MTA-STS: encryption on the way in, required
MTA-STS is a short policy file on your website plus a DNS record. The standard, RFC 8461, lets a domain tell senders to “refuse to deliver to MX hosts that do not offer TLS with a trusted server certificate.” Google supports it for Workspace domains and documents it in its admin help. TLS-RPT is its partner record, which sends you reports when a delivery fails. Start in testing mode, read the reports, then enforce.
It’s the one record on this list a small firm can skip without much risk, since most big providers already connect with TLS. It’s worth adding once DMARC is at reject.
The domain is an account too
A domain address adds a second front door. Whoever controls your registrar account controls your MX record. That means they control where your mail goes and can reset passwords on anything tied to your address.
Protect the registrar account the way you protect the mailbox:
- Turn on two-step verification at the registrar, with a passkey or app if it offers one.
- Turn on auto-renew, and keep a card on file that won’t expire before the next renewal.
- Turn on the registrar lock, which blocks transfers until you lift it.
- Use a recovery address on a different domain. If the registrar’s only contact is you@yourfirm.com, a lapsed domain also cuts off the mail that would have warned you.
That last one is easy to miss. ICANN’s Expired Registration Recovery Policy requires registrars to send at least two reminders:
One of these notices must be sent approximately one month prior to expiration and one must be sent approximately one week prior to expiration.
Those reminders go to the contact address on file. After expiry there’s still a way back. Registries must offer a 30-day Redemption Grace Period after a domain is deleted, when the owner can restore it. After that, anyone can buy it.
What happens when a domain is let go
When a firm closes or rebrands, the old domain often lapses. Whoever buys it next can receive mail sent to every old address. That includes password resets.
Truffle Security showed what that reaches. On January 13, 2025, it reported buying one defunct startup’s domain. Through Sign in with Google, its researcher reached former employees’ accounts:
logging into each of the following services granted us access to old employee accounts: ChatGPT, Slack, Notion, Zoom, HR systems
It estimated over 100,000 such domains were for sale. If you rebrand, keep the old domain renewed for years and forward its mail. It’s a small yearly cost against everything still tied to it.
Aliases: a different address for each use
An alias is a second address that delivers to the same mailbox. Used well, it tells you which company leaked your address. It also makes some phishing easy to spot, because a fake bank message arriving at your newsletter alias is wrong on its face.
There are four kinds, and they differ in who can see the link to your real address.
| Kind | How it looks | Where it works | What it hides |
|---|---|---|---|
| Plus address | you+shop@gmail.com | Gmail, and many other providers | Nothing; your real address is in plain view |
| Domain alias | shop@yourfirm.com | Any host on your own domain | Your main address, unless the sender guesses it |
| Catch-all | anything@yourfirm.com | Many hosts; any paid Proton plan | Your main address, but it also catches spam to made-up names |
| Hide-my-email alias | random words at the provider’s domain | Proton, including 10 on the free plan | Your real address and your name |
Google’s Workspace Learning Center explains that mail sent to any plus variation arrives in your current inbox, and that you can filter on it. Gmail’s own help also notes that “dots don’t matter in Gmail addresses,” so dotted spellings are the same inbox too. Plus addresses are handy for sorting. Spammers know how to strip the plus part, so they’re weak for privacy.
Proton’s catch-all page says “You can set up a catch-all address using your custom domain with any Proton paid plan.” Turn it on only if you’ll actually invent addresses on the fly. Otherwise it collects mail sent to every guessed name.
Keeping your address off marketing lists in the first place is a privacy question, and it’s covered in the private email guides.
Encryption on the address you already have
You don’t need a new address to encrypt mail. Add-on services sit on Gmail or Outlook and encrypt what you send. Your address, your domain records and your inbox all stay put. Two names come up often in searches.
Virtru works inside Google Workspace and Microsoft Outlook. Its recipient page says recipients don’t install anything:
With Virtru, there is no software to install, and you don’t have to create a username or password.
The recipient clicks “Unlock Message” and confirms who they are with a Google or Microsoft sign-in or a verification email. Virtru also lets organizations hold their own keys, which is rare among add-ons.
MailHippo is HIPAA-focused encryption that, in its own words on its home page, “works with your current email address, and with any email provider.” It provides a business associate agreement at signup. Recipients follow a link, log into MailHippo’s site and read the message there. As listed October 4, 2026, it offers a free 30-day trial, then Basic at $4.95 a month and Pro at $7.95 a month.
The two differ mainly in what the recipient goes through and who holds the keys. Both leave your domain records exactly as they are, so set those either way. How these add-ons compare with Purview, Paubox and the rest is in the secure email companies. Sending one protected message from your current account is covered in sending securely from Gmail and sending securely from Microsoft 365.
Point and your domain
Point isn’t an email provider, and it doesn’t encrypt mail or host an address. It works on the Gmail or Outlook account you already have, and it never needs your email password. Your MX, SPF, DKIM and DMARC records stay where you set them, and so does your registrar lock. What Point does on that inbox is on what Point does for you.
Mail that’s end-to-end encrypted opens only for you and the recipient, and that includes any assistant. That trade is set out in encrypted email, and what an AI assistant cannot read.
Common questions
What is Virtru email?
Virtru is an encryption service that works inside Gmail and Outlook. You keep your address. Recipients open the message by clicking “Unlock Message” and verifying with a Google or Microsoft sign-in or an emailed link, with nothing to install. Organizations can choose to hold their own keys.
What is MailHippo?
MailHippo is a HIPAA-focused email encryption service that works with your current address on any provider. It signs a business associate agreement at signup. Recipients read messages on MailHippo’s website. Paid plans follow a free 30-day trial; prices are in the section above.
How does email work?
Your provider’s server looks up the recipient’s domain in DNS to find its mail server, then hands the message over, encrypted with TLS when both sides support it. The receiving server checks SPF, DKIM and DMARC to judge whether the mail is really from you. Then it stores the message in the recipient’s mailbox.
Is an address on my own domain more secure than a Gmail address?
Not by itself. The mailbox is only as secure as the host and your sign-in. What your own domain adds is control: you set the records that stop forgery, and the address stays yours if you move. It also adds a registrar account you have to protect.
What is a security email address?
It usually means one of two things. In your Google or Microsoft account, it’s the recovery address, which Google says is used “to help you get into your account if you forget your password or can’t sign in.” Put it on a different provider from the account it protects. For a business, it can also mean an address like security@yourfirm.com for people reporting problems. RFC 9116 defines a security.txt file that publishes that contact on your website.
What is the most secure email address to have?
An address on a domain you own, hosted by a provider whose storage model fits what you protect, behind a passkey or security key, with DMARC at reject. The providers themselves are compared in the most secure email, ranked honestly.
Do I need a paid plan to use my own domain?
On secure providers, usually yes. Proton lists custom domains on its paid plans, not on Proton Mail Free. Google Workspace and Microsoft 365 are paid business plans too. The free options are compared in free secure email.