Domain forwarding for outreach domains
Forward a sending domain to your main site.
Forwarding helps recipients who visit a sending domain understand the brand behind the message.
What this helps you do
Forwarding helps recipients who visit a sending domain understand the brand behind the message.
Recommended workflow in Outlio
Choose where the sending domain should redirect, usually your main website.
Set forwarding at the registrar or host.
Keep email DNS records intact while forwarding web traffic.
Test http and https versions of the domain.
Document which domains forward to which site.
Quality checks
- Forwarding is separate from MX, SPF, DKIM, and DMARC.
- Use a real brand destination rather than a blank parked page.
- Check forwarding after changing nameservers.
Common mistakes to avoid
- Breaking email records while trying to forward web traffic.
- Forwarding to a page that does not match the sender brand.
Done well, this should leave you with
A cleaner Outlio setup, fewer avoidable campaign issues, and a more reliable path from setup to replies.
Related articles
Why do I need DNS records?
Understand SPF, DKIM, DMARC, MX, and tracking records.
How to setup MX, SPF, DKIM, DMARC
Step-by-step DNS setup for sending domains.
SPF, DKIM, and DMARC for Google Workspace
Configure Google Workspace authentication for outreach.
SPF, DKIM, and DMARC for Microsoft 365
Configure Microsoft 365 authentication.
Namecheap DNS with Google Workspace
Add Google Workspace records in Namecheap.
Namecheap DNS with Microsoft 365
Add Microsoft 365 records in Namecheap.
Was this article helpful?
Need more help? Contact Support