Cold Email Question

[Seopreneur01]

Hi folks, I’m starting a fresh campaign for cold email outreach to a list of prospects (B2B). And for sending the emails, I’ll use a different domain name that resembles my company name (to keep my main domain’s reputation untouched).

For example, if the company name is ‘royalwebdesign.com’, I’ll buy other domains such as ‘royalwebdesigns.com’ or ‘royalwebdesign.net’ etc.

Now I believe some of the email recipients will actually visit the domain name mentioned in my email address (either to check the authenticity or to know more about my service - because I usually do the same).

I was thinking of just redirecting this domain name to my main company’s domain. But the question is – Would this impact my original domain’s sender reputation in any way?

Which route do you guys follow?

1. Leave the new domain blank (because no one visits the domain), or

2. Create/duplicate a landing page for each individual domain, or

3. Redirect to the main domain

Thanks in advance!

 

[lawrencelau]

i don't think redirect will hurt anything.

Common sense, if this hurt,
I will create the same scenario for my competitor, spam people with a domain similar with theirs and redirect the site to them.

 

[Novus]

3.Redirect to the main, I don't see how it will impact your main domains sender reputation.

 

[code API]

Don't redirect. It will affect the A records pointed to the Email domain in your DNS. You are essentially telling the sending server IP that the hosting had moved to a new IP. So after redirection, your email sender app or website will stop doing it's job.

I have tested this scenario due to my experience in email marketing even with multiple IP rotation, custom SMTP, PowerMTA etc.

Here is what you should be doing instead:

Use the email domain as is without redirecting. Simply hyperlink your offer or money site from within the email copy. Any references to links in the copy should be related to your main CTA or conversion goal (not the URL of your email domain of course).

 

[Amaz0n]

Don't redirect. It will affect the A records pointed to the Email domain in your DNS. You are essentially telling the sending server IP that the hosting had moved to a new IP. So after redirection, your email sender app or website will stop doing it's job.

That's wrong. You should read some newbie guides regarding SMTP behavior.

The sending domain for the server is not automatically the domain of the email address used.

F. ex. if you are adding your domain to Gmail it is still using the Gmail sending server IP and domain.

Also redirection based on meta refresh or javascript does not affect the IP anyway, so saying "don't redirect" is essentially wrong.

For the OP: Yes, you can redirect without issues, or use Cloudflare or an own Nginx reverse proxy.

 

[code API]

That's wrong. You should read some newbie guides regarding SMTP behavior.

The sending domain for the server is not automatically the domain of the email address used.

F. ex. if you are adding your domain to Gmail it is still using the Gmail sending server IP and domain.

Also redirection based on meta refresh or javascript does not affect the IP anyway, so saying "don't redirect" is essentially wrong.

For the OP: Yes, you can redirect without issues, or use Cloudflare or an own Nginx reverse proxy.

I am telling OP what I have tested with custom SMTP, and I did the redirection from server side. Not Cloudflare. Maybe we have different setup as I don't use Gmass. But Goodluck hitting inbox with your setup.

 

[xcodes]

1) Re-direction of traffic from email source will never damage your primary domain so don't worry on that.
2) Add 301 url forwarder on DNS to business domain.
3) If your primary domain is royalwebdesign.com , And when your sending emails from royalwebdesigns.com make sure to set reply address as [email protected] ONLY, But never mention your primary domain as reply cause it will create MX relay host issues and leads to primary domain reputation down or even blacklist sometimes.

Instead setup email forwarder on [email protected] to [email protected]

Good luck

 

[Seopreneur01]

Don't redirect. It will affect the A records pointed to the Email domain in your DNS. You are essentially telling the sending server IP that the hosting had moved to a new IP. So after redirection, your email sender app or website will stop doing it's job.

I have tested this scenario due to my experience in email marketing even with multiple IP rotation, custom SMTP, PowerMTA etc.

I think this issue depends on the type of redirects we make. Directly making redirection in the nameservers/dns could cause these issues.

So I guess the safest option is to make redirect using javascript or some plugin. Basically not changing any server settings, and redirecting the user automatically using code once the alternate domain loads up fully.

Here is what you should be doing instead:

Use the email domain as is without redirecting. Simply hyperlink your offer or money site from within the email copy. Any references to links in the copy should be related to your main CTA or conversion goal (not the URL of your email domain of course).

From what I've heard so far, adding URLs in the cold email might trigger spam filters and impact deliverability. So I'll refrain from mentioning my actual URL in the first email copy.

And hence, I'll need to ensure that the 'alternate domain' is more than a blank page.

Also redirection based on meta refresh or javascript does not affect the IP anyway, so saying "don't redirect" is essentially wrong.

For the OP: Yes, you can redirect without issues, or use Cloudflare or an own Nginx reverse proxy.

That makes total sense, thanks.

I've worked with cloudflare before and I think I'm gonna go that route. Just to clarify, I don't need to set up a hosting for doing this, right? And for redirecting, it'll require me to change some of the A/TXT records in cloudflare while STILL keeping the email records intact?

1) Re-direction of traffic from email source will never damage your primary domain so don't worry on that.
2) Add 301 url forwarder on DNS to business domain.
3) If your primary domain is royalwebdesign.com , And when your sending emails from royalwebdesigns.com make sure to set reply address as [email protected] ONLY, But never mention your primary domain as reply cause it will create MX relay host issues and leads to primary domain reputation down or even blacklist sometimes.

Thanks for all the points. That cleared a lot of stuff! So I think I have two options now:

1. To create a redirect via cloudflare
2. 301 redirect in DNS

Are these both essentially the same thing? Would you prefer one over the other?

Instead setup email forwarder on [email protected] to [email protected]

Good luck

Great suggestion. Though I won't need this because I'll be using instantly.ai which has a great 'unibox' feature

 

[Seopreneur01]

I came across another small hiccup while setting things up. And any help is appreciated!

So let's say I am using two 'burner' domains or 'alternate' domains for sending emails. I will be buying through Google domains and setting up Google workplace account for both the domains. (And future subsequent domains, if need be).

My question is: Can I buy both the domains from a single 'Google domains' account? Is there such a thing like 'Domain IP' which could carry over one's reputation to the other?

From what I've learnt so far the Sender's IP and the domain name are the only two factors impacting reputation. Since I'll be using Instantly.ai, I'm sure they use flexible/rotating IP for different domains. So that's covered.

But is it safe to keep one Google Domains account where I buy all additional domains? I'd like to keep them in the same account for convinience's sake.

Thanks in advance!

 

[xcodes]

1. To create a redirect via cloudflare
2. 301 redirect in DNS

You cannot achieve that through DNS rules, but it is possible to accomplish it using page rules in Cloudflare.

Great suggestion. Though I won't need this because I'll be using instantly.ai which has a great 'unibox' feature

Using a third-party warmup service can be beneficial, but it's important to exercise caution when configuring the reply settings. Set the reply rate as low as possible and consider incorporating randomization to avoid the risk of your sender being blacklisted. It's worth noting that the majority of warmup services rely on similar open and reply logic without utilizing AI

My question is: Can I buy both the domains from a single 'Google domains' account? Is there such a thing like 'Domain IP' which could carry over one's reputation to the other?

You can purchase all your domains from the same registrar and effectively transfer reputation to multiple domains through SPF rules. However, this is only feasible when you are utilizing appropriate senders that are associated with the domains included in the SPF records.

Good luck

 

[Seopreneur01]

You can purchase all your domains from the same registrar and effectively transfer reputation to multiple domains through SPF rules. However, this is only feasible when you are utilizing appropriate senders that are associated with the domains included in the SPF records.

Good luck

Actually I DON'T want to transfer the reputation of one domain to another. In fact, I want them as distinct as possible (that's why buying two in the first place). So can I still buy them from the same registrar's account (Google Domains) and keep them there?

Will both the domains use the same SPF? Because if they do, I'll have to change my route

Thanks

 

[xcodes]

Actually I DON'T want to transfer the reputation of one domain to another. In fact, I want them as distinct as possible (that's why buying two in the first place). So can I still buy them from the same registrar's account (Google Domains) and keep them there?

Will both the domains use the same SPF? Because if they do, I'll have to change my route

Thanks

If you are dealing with different servers, your SPF record will be different for each server. However, SPF has the ability to combine multiple servers, allowing the passing of reputation from domain to domain. Alternatively, you can simply specify the SPF record for that specific machine.

Of course, you can maintain multiple domains from the same registrar without encountering any issues.

Cheers

 

[Algo]

There's no problem with redirecting to your main domain.

The majority doesn't care about visiting the sender domain website, you can start without it.

 

[IceActually]

This is smart and I stumbled upon this thread just in time. I want to rewarm some large mailing lists that havent received email in over a year and a half and this would be an excellent way to filter out the engaged emails from those who'd just bounce and what not.

 

[Seopreneur01]

This is smart and I stumbled upon this thread just in time. I want to rewarm some large mailing lists that havent received email in over a year and a half and this would be an excellent way to filter out the engaged emails from those who'd just bounce and what not

Yeah, it's a great way to safeguard your original domain's sender reputation especially when doing it with an abandoned list

 

[IceActually]

Yeah, it's a great way to safeguard your original domain's sender reputation especially when doing it with an abandoned list

Yep - I actually just used it over the weekend, and in hindsight it was unnecessary with the list. 54% open rate (on a ~50k subscriber list!) but still something I'll keep in my back pocket for the future

 

[gaikwadharsh]

thank find answer