Domain forwarding and MX records for cold-email domains

Draft — written from product facts + domain knowledge; UI labels to be verified before publishing.

A cold-email domain should behave like a real company domain. Two things make that true: the domain forwards to a real website, and it can receive mail. Spam filters and curious prospects both check. This article covers domain forwarding (redirects) and MX records for secondary sending domains, whether managed in Icemail or at your own registrar.

Why this matters

• Filters such as Google's look at whether a From domain resolves to a live website. A parked page or DNS error is a spam signal.
• Prospects who type your domain into a browser should land on your real site, not an error.
• Without MX records, replies, bounces and out-of-office messages have nowhere to go. You lose replies and cannot detect bounces, which pushes bounce rate up.
• A domain that receives mail but has no mailbox to store it (a "null MX") is also a red flag.

Steps: set up domain forwarding

In Icemail

1. Open Icemail from the OutreachFox dropdown (top-left icon → Icemail).
2. Open the domain and find the forwarding setting.
3. Enter your main website URL (for example https://www.acme.com).
4. Save. Icemail creates the redirect records; both acmehq.com and www.acmehq.com now redirect.

At a registrar

1. Open the domain's DNS or Forwarding section (GoDaddy: Forwarding; Namecheap: Domain → Redirect Domain; Porkbun: URL Forwarding; Cloudflare: Rules → Redirect Rules).
2. Add a forward from @ and www to your main site.
3. Choose 301 (permanent) and forward the whole domain, not a single path.
4. Remove any parked-page A/ALIAS records the registrar added.
5. Test by opening http://yourdomain.com and http://www.yourdomain.com in a private browser window.

Steps: set MX records

Icemail sets MX automatically for domains it manages. For your own domains, add the provider's MX at your DNS host.

1. Open the DNS editor for the domain.
2. Delete any placeholder MX records (registrar defaults such as mx1.parking...).
3. Add the provider's MX record(s) with the priorities shown.
4. Save and wait for propagation.
5. Send a test email to a mailbox on the domain and confirm it arrives.

What you see afterwards

The domain redirects to your main site, and test messages to the mailboxes arrive. In OutreachFox, replies to campaign emails show up in the campaign's replies and lead statuses update correctly.

Tips

• Forward to the homepage or a landing page that matches what your emails talk about.
• Keep the main brand domain out of cold outreach entirely; it holds your transactional and team mail.
• If you use catch-all on a sending domain, monitor it: catch-all inboxes collect spam that can trigger provider alerts.
• Mailbox-level forwarding (copying inbound mail from a cold mailbox to a central inbox) is available in Icemail per mailbox. Use it when a team member handles replies for many mailboxes.

Troubleshooting

• Forward works for the root but not www**.** Add the www forward separately or add a CNAME www → @.
• Redirect shows a certificate warning. Use a forwarding service that issues SSL (Cloudflare, Porkbun, Icemail). Plain registrar forwards over HTTPS often do not.
• Replies are missing. Check MX with a lookup tool. If MX points at the registrar's parking host, the messages are being discarded.
• Bounce rate looks like 0% but replies are also 0. Almost always missing or wrong MX; bounces are not being received.

Related articles

• Adding DNS records at Cloudflare, GoDaddy, Namecheap and Porkbun
• SPF, DKIM and DMARC: what they are and how to check yours
• Buy a domain through Icemail from inside OutreachFox
• Set up a custom tracking domain
• Deliverability fundamentals for cold email