Deliverability Tip: Identity behind a sending domain name

July 28, 2014

Some folks create a domain name (dedicated to email campaigns) linked to a non-functional, non-existent website. A good example is when an individual clicks on mynewsletter.ext and it doesn’t take you to an actual website (yet the email address noreply@mynewsletter.ext is still used as a sender address), but the user arrives at a blank page (or a 404 error page, etc).

Good news, this practice is very bad for at least three strong reasons:

a domain name without a website is a characteristic which portrays suspicious anomalous behaviour – normally used by spammers & phishers;
this affects the legitimacy of your email, which makes it harder to be verified by a recipient’s servers.
anti-spam filters & the average internet user may perceive your email as phish.

Solution

Create an easy-to-understand website with clear information that explains more about you/your entity.
Ensure that the sending domain’s whois records are public, and identify your business. Stay away from publishing private whois information.
Add an extra layer of “trust” by implementing at least SPF & DKIM email authentication techniques to validate your identity. SPF curbs domain spoofing, while DKIM prevents spammers from forging source addresses.

Conclusion: Always distinguish yourself from spammers by ensuring that the domain name you use in your emails allows user to verify your identity.

Author: The Sinch Mailjet Team The team at Sinch Mailjet

Cookie Subgroup	Cookies	Cookies used
documentation.mailjet.com	_cfuvid , __cfruid	First Party
.mailjet.com	OptanonConsent	First Party
mailjet.com	actualOptanonConsent , apt.sid , OptanonAlertBoxClosed , mail_session	First Party
app.mailjet.com	connect.sid , SERVERID	First Party
hello.mailjet.com	uvts , __cf_bm	First Party
m.stripe.com	m	Third Party

Cookie Subgroup	Cookies	Cookies used
hello.mailjet.com	ubpv , ubvs	First Party
dev.mailjet.com	_an_uid	First Party
app.mailjet.com	rl_page_init_referring_domain , rl_anonymous_id , rl_group_trait	First Party
mailjet.com	_vwo_ds , test_rudder_cookie , _vis_opt_s , rl_group_id , rl_user_id , _ga , rl_session , rl_page_init_referrer , ubvt , _vwo_uuid , apt.uid , optimizelyEndUserId , _gat , _vwo_sn , _ga_xxxxxxxxxx , _gid , _uetvid , _vis_opt_test_cookie	First Party
hello.learn.mailgun.com	visitor_id	Third Party

Cookie Subgroup	Cookies	Cookies used
hello.mailjet.com	_gd_session	First Party
mailjet.com	__q_state_zkTi4FmbUJniF8K2 , _vwo_uuid_v2 , apt.temp-xxxxxxxxxxxxxxxxxx , __tld__	First Party
demo.mailjet.com	_gd_visitor	First Party
dev.mailjet.com	_pin_unauth , __uvt	First Party
app.mailjet.com	__stripe_mid , __stripe_sid	First Party
mailgun.zendesk.com	_cfuvid, __cf_bm, __cfruid	Third Party
vimeo.com	_cfuvid, __cf_bm, vuid	Third Party
producthunt.com	__cf_bm	Third Party
goldcast.io	__cf_bm	Third Party

Cookie Subgroup	Cookies	Cookies used
www.mailjet.com	pardot	First Party
app.mailjet.com	rl_trait	First Party
hello.mailjet.com	visitor_id	First Party
mailjet.com	_gat_gtag_xxxxxxxxxxxxxxxxxxxxxxxxxxx , _uetsid , _fbp , _tt_enable_cookie , _ttp , _rdt_uuid , __q_domainTest , _gcl_au	First Party
linkedin.com	bcookie, lidc, li_gc	Third Party
pi.pardot.com	pardot, lpv830283	Third Party
bing.com	MSPTC, MUID	Third Party
hello.learn.mailgun.com	pardot	Third Party
pardot.com	visitor_id	Third Party
doubleclick.net	IDE, test_cookie	Third Party
youtube.com	VISITOR_PRIVACY_METADATA, VISITOR_INFO1_LIVE, __Secure-xxxxxxx	Third Party
www.google.com	_GRECAPTCHA	Third Party

Deliverability tip: Identity behind a sending domain name

Solution

Related articles

The difference between email deliverability and your delivery rate

Why email deliverability issues will ruin the customer experience

How can marketers help improve email deliverability?