All Collections
Getting Started
Recommended setup
Authenticate your domain with Peptalkr
Authenticate your domain with Peptalkr

Send email from your own domain. This guide is a must read.

Updated over a week ago

IMPORTANT - Google & Yahoo's anti-spam policies mean you must have a fully verified domain to avoid junk mail filters.


This applies to ALL USERS WHO SEND EMAIL and want to use a domain other than @peptalkr.app


Starting in February 2024, Google and Yahoo are upping their game in domain authentication – a welcome step for the email community to reduce scams.
​

In this article, we dive into what's changing. These changes ensure that all those genuine emails (like yours!) have a better chance of landing right where they should - in inboxes and not spam filters.

So, here's the lowdown on what you need to do before February 2024 to keep your emails flying high:

  1. All email sent from Peptalkr must be sent with a fully verified domain that belongs to you or us. If you have not verified a domain with us, you will only be able to send email with the @peptalkr.app domain - this applies to ALL email including campaigns, automations and transactional email.
    So, now's the perfect time to verify your own domain with Peptalkr.
    ​

  2. It is now a requirement to authenticate your domain using all three methods: DKIM, SPF, and DMARC. Historically, we have only required DKIM. So even if you have verified your domain with us, you will still need to add SPF and DMARC verification records.
    ​

  3. Ensure you have permission to email your recipients. Refer to the privacy laws relevant to your location. If you are emailing people who you don't have permission to email, you may receive spam reports from those recipients. Spam reports can result in permanent damage to the deliverability of emails sent by your domain.

πŸ™‹πŸ»β€β™€οΈ Remember, we're here to help guide you through these changes. If you've got any questions or need a bit of a nudge in the right direction, our team is here.

What is domain authentication?

In simple terms - it's where you prove that you own a domain - e.g @yourdomain.com and provide Peptalkr with permission to send emails on your domains behalf.

For example, if you want your Peptalkr emails to come from an email address such as [email protected] - you need to:

  1. Inform us you want to send email from that domain (use the chat bubble).

  2. Verify you own that domain by adding DNS records to your domain settings

  3. Speak with us again once step 2 is complete so that we can confirm your domain is verified βœ… (failure to receive the green light from us will result in your emails failing to send).

Do I have to do this?

Verification has historically been optional. This is changing on February 1, 2024.

Verification will then be mandatory.

🚨 If you do not verify a domain name you own - your only option to send email will be to use the @peptalkr.app domain that is already available in your account.

Why are things changing suddenly? This feels rushed.

Notice how many more scams, spam and email interceptions are happening in the news - and perhaps to you - lately? Google and Yahoo, two of the biggest players in the email arena, are updating their policies to enhance email security and authenticity. These changes are primarily focused on verifying the identity of email senders to combat spam and phishing attacks.

In 2024, they will require stricter Domain Name System (DNS) verification for anyone sending emails using their own domain. This means that if you use ~or~ want to use a custom email domain (like [email protected]) to send email from Peptalkr, you need to pay attention to these updates.

Google & Yahoo announced this change towards the end of last year, and we have worked hard to digest these changes and prepare instructions you can follow.

We are now handing the baton over to you to do your bit. And yes, this applies to ALL email - campaigns, automations AND transactional email.

πŸ‘‰ If you do nothing - yes, you can still send email with Peptalkr. However, all emails will need to be edited to change the sending domain to @peptalkr.app - failure to do so will result in emails failing to send.


🫡 Here's what you need to do:

πŸŽ₯ Full video instructions

πŸ€” Looking for the copy-paste codes you need to add? Please click the steps below and answer the questions to find the instructions relevant to you.
​It is important you follow the steps so you do not make a mistake.


πŸ“ Full written instructions

You must ensure all 3 DNS records are added:

  1. DKIM

  2. DMARC

  3. SPF

πŸ‘‰ First, select the option below that applies to you and click it to expand the steps you must take - this includes the copy/paste for DMARC/SPF. Read the instructions carefully.

I have verified my domain with Peptalkr in the past

All users, even if you have already verified your domain in the past, must follow these steps (watch the video above for a full tutorial!):

1. Go to your DNS settings for your verified domain

Depending on your domain configuration, your DNS may be hosted at either:

  1. Your domain registrar - the place you purchased your domain.

  2. Your website hosting account - if you bought your domain in one place - e.g. Crazy Domains, but your website is hosted in another place - e.g. Squarespace - your DNS may be managed on Squarespace.

  3. A DNS intermediary - such as Cloudflare.

If you're not sure - please ask your IT person/website developer. Generally, your DNS is managed wherever your 'Name servers' are pointing.

2. Search for your existing Peptalkr TXT record

If you have verified your domain with Peptalkr in the past, you should find a record that looks something like this:

Try search for:

cm._domainkey

πŸ‘Yes I see it! click here.

Great. Do nothing. Go to the next step.

❌ I don't see it... click here.

If it's missing - you're either in the wrong place for DNS, or your have not verified your domain with Peptalkr. Feel free to chat with us if you need a hand.


3. Search for any existing TXT record containing 'v=spf1'

If you use Gsuite, Outlook or some other email provider to send emails from your business domain - chances are you already have an SPF record.

Try search for:

v=spf1

πŸ‘Yes I see an SPF record. click here.

If you find a record where the 'Name' is your root domain (yourdomain.com or '@') then you need to edit it.

🚨If you see an SPF record, but it is under a subdomain - for example:

mg.yourdomain.com.au and not just @ or yourdomain.com.au then go to:
'❌ I don't see one' below

  1. Click 'Edit'

  2. In the 'Content' or 'Value' field paste in the following text EXACTLY as it appears here in the grey box below. But paste it AFTER the existing content in your SPF record, but BEFORE the '~all' - and press 'Save'.

include:_spf.createsend.com

​For example, if your current SPF record is:


​It will become:


​3. Press SAVE

❌ I don't see one. click here.

No problem, you need to add one.


Create/Add a new record and select 'TXT' from the 'Type' dropdown.

In the 'Name' field enter '@' (this means it will be added to your root domain - e.g. yourclinic.com).

Set the TTL to '300 seconds' or '30 minutes'.

In the 'Content' or 'Value' field, enter the following text EXACTLY as it appears here - and press 'Save'.
​

v=spf1 include:_spf.createsend.com ~all


​For example:
​


4. Search for any existing TXT record that contains: '_dmarc'

If you use Gsuite, Outlook or some other email provider to send emails from your business domain - you may already have a DMARC record.

Try search for:

_dmarc

πŸ‘Yes I see a DMARC record. click here.

Do nothing. Move to the next step.

🚨If you see a DMARC record, but it is under a subdomain - for example:

_dmarc.mg.yourdomain.com.au and not just @ or yourdomain.com.au then go to:
'❌ I don't see one' below

❌ I don't see one. click here.

No problem, you need to add one.

Create/Add a new record and select 'TXT' from the 'Type' dropdown.

In the 'Name' field enter '_dmarc'

Set the TTL to '300 seconds' or '30 minutes'.

In the 'Content' or 'Value' field, enter the following text EXACTLY as it appears here - and press 'Save'.​

v=DMARC1; p=none;


6. LAST STEP - message us using the chat bubble

Message us using the chat bubble while logged into your Peptalkr account and say:

I have a verified domain, but I just added DMARC and SPF. My domain name is: [insert your domain].

I have never verified a domain with Peptalkr

Watch the video above for a full tutorial.

No problem. Start by searching your email inbox (the email you used to sign up to Peptalkr) for an email from us with the following subject line:
​

[IMPORTANT] Your DNS Settings

βœ… Found it? Great. That's the 'DKIM' record you need to add. Once you add it, follow steps 3-6 in the section above "1️⃣ I have verified my domain with Peptalkr already"

❌ Didn't find it? Send us a message using the chat bubble and ask the following:

I want to verify my own domain with Peptalkr, can you please send me the instructions. My domain name is [insert your domain name - e.g my clinic.com]


I'm not sure - HELP

Use the chat bubble to message us and say:

I have read the domain authentication article - I am not sure if I have a verified domain or not. Please help.

Our team will get back to you as soon as possible 😊


​

Did this answer your question?