Custom Domain Email Aliases: Use Your Own Domain with MyShield

If you want the privacy benefits of aliasing without using @myshield.world, custom domains let you put MyShield behind your own address space.

What Custom Domains Give You

With a custom domain connected to MyShield, you can:

• create aliases like [email protected] or [email protected]
• receive mail for those aliases through MyShield
• use labels, pause/resume, delete, and reply-from-alias on paid plans
• keep your real inbox private behind a branded public address

In the current product, those aliases still forward to the email address on your MyShield account. They are not independently routed to different inbox destinations per alias.

The DNS Records Involved

MyShield's dashboard currently shows three key DNS records for custom-domain use:

1. MX

This routes inbound mail for your domain to mail.myshield.world.

2. Ownership verification TXT

This is the _myshield TXT record used to verify that you control the domain.

3. DKIM TXT

This publishes the DKIM public key MyShield generates for your domain, which matters for reply-from-alias deliverability from your custom domain.

What the Current Verification Check Actually Confirms

The current domain verification endpoint checks the _myshield TXT record for the expected verification token.

That means domain ownership verification is not the same thing as full mail deliverability validation. You should still add the MX and DKIM records shown in the dashboard if you want custom-domain aliases to work properly in practice.

How Mail Flows

For verified custom domains, MyShield's SMTP service validates the recipient first. If the alias is active, the raw message is handed to the main application and forwarded to your account email.

If reply-from-alias is available on your plan, replies can be sent back out from the alias address on your custom domain as well.

Pro and Business

Custom domains are available on Pro and Business.

Connect your domain →