Why do you need a Branded Sending Domain?
Setting up a Branded Sending Domain (also known as domain Masking) is the process of applying a custom domain as the from/reply-to address for an email campaign. It allows your brand to appear in the email header and links within the email – improving deliverability and open rates.
Each profile in Pure360 can have one Branded Sending Domain. This domain or sub-domain is registered by you, for the sole purpose of emailing via Pure360 – it should not be used to host websites or for any other service.
How to add your Branded Sending Domain
1) Choose a domain
For this example let’s assume your company website has the domain ‘yourwebsite.com’. Your email mask could be either of the following options:
-
A brand new full domain (i.e. ‘yourwebsite-news.com‘, or ‘yourwebsite-email.com‘)
-
A sub-domain of your existing domain (i.e. ‘news.yourwebsite.com‘, or ‘email.yourwebsite.com‘)
We’d suggest you don’t use prefixes or words that are likely to trigger spam filters, such as ‘offers.yourwebsite.com‘.
2) Set up your domain for masking
Once a domain or sub-domain has been chosen and registered with your domain provider, it will need to be pointed towards our broadcast system’s DNS and hold authentication for us to send of you.
The best way is to set up the A, MX and TXT records as per the table below. Once you have done this, contact Pure360 to have a DKIM key created for you.
| Your new domain/ sub domain | TTL | Record type | Value |
| email.example.com | 300 | A | 15.197.176.170 |
| email.example.com | 300 | A | 3.33.173.208 |
| email.example.com | 300 | MX | mx0.pur3.net (priority: 10) |
| email.example.com | 300 | TXT | v=spf1 include:_spf.pur3.net ~all |
| _dmarc.email.example.com | 3600 | TXT | v=DMARC1; p=none; |
| pureresponse._domainkey.email.example.com | 300 | TXT | (DKIM Key provided by Pure360 - ask from your account's chat or email support @ pure360.com) |
3) Testing
Please test your newly registered domain before submitting it to us. After you complete step 2, it may take up to 48 hours for the changes to propagate around the internet. If you would like any help checking the domain is working correctly, please let us know.
4) Contact us to add the mask to your profile
Either log in to your account and use the support widget, or email us at accountmanagers@pure360.com, with the following information:
-
The domain or sub-domain you have pointed to us
-
The profile you’d like to use the new mask on
-
Whether you used the option of mapping the NS records or MX, A & TXT
-
The full required from address including the part to the left of the @ sign record
Assuming the domain has been set up correctly, we will be able to make your new domain mask available to use on your account within one working day.
Branded Sending Domain FAQs
Can I send from my normal company email address?
Yes: it will need to have our DKIM on it + You will still need a separate (sub)domain set-up fully for us to add behind it.
Can I have a different ‘from’ address for each campaign?
Changing the part of the ‘from’ address before the ‘@’ can be done by our Support team but is not advisable to change this regularly. It is also possible to use dynamic reply to personalise the prefix@ for each contact as long as that prefix has an address at your domain too.
You can also consider working from different profiles with different ‘from’ addresses.
Where do replies to email campaigns go?
When you have dedicated a (sub)domain to us all replies come back to us. Real replies are forwarded on to your specified email address per campaign. By default this is the profile's forwarding address; you can change this in "manage profile" from the profile menu in the top right.
More details can be found on our reply handling guide.
Should I increase my DMARC p= level from none to quarantine or reject?
Yes you should. Some inboxes give you better deliverabiltiy for having something higher than 'none'.
If you choose to do that, you should add dmarc report addresses first. To check to be sure it is working properly, so when you do increase it your email continue to get delivered and can continue to keep and eye on it. eg: if you increase your p to quarantine or reject the txt record will look like this (where you have actual email addresses where it says "email-address"...
| _dmarc.email.example.com | 3600 | TXT | v=DMARC1; p=reject; rua=mailto:email-address; ruf=mailto:email-address; fo=1 |
If you use an email address outside of your domain / the domain holding the dmarc record, then you will have more work to do to authenticate it at the domain. Sub-domains include the parent domain, eg:
A dmarc on email.example.com can send reports to @example.com without needing extra authentication.
But A dmarc on email.example.com cannot send reports to @mydomain.com without going through an extra step of authentication on mydomain.com. This usually only occurs if you use a 3rd party dmarc processor, in which case they'll help you configure it.
You previously asked me to add another domainkey record, do I need to remove it?
Previous versions of this table asked for a _domainkey txt record, like the below.
This is part of a deprecated version of dkim and is no longer required.
| _domainkey.email.example.com | 300 | TXT | o=~\ |
If you have it, it will simply be ignored by inboxes and will not do any harm at all.