Features
What we do
Explore all our features
Get a demo
Join our
Live Product Tour
Playbooks
By need
Explore all playbooks
Resources
Learn with us
Free Resources
ACADEMY
HOT TOPICS
Academy
Wall of love
Pricing
First off, a bit a definition :
Sender Policy Framework (SPF) is an email authentification method that allows checking during mail delivery that a mail claiming to come from a specific domain is submitted by an IP address authorized by that domain’s administrators.
It basically verifies the sender’s IP address.
DomainKeys Identified Mail (DKIM) helps prevent spoofing on outgoing messages sent from your domain by adding an encrypted signature to the header of all outgoing messages.
It basically verifies who’s sending the email.
Domain-based Message Authentication, Reporting, and Conformance (DMARC) help mail administrators prevent hackers and other attackers from spoofing their organization and domain. Spoofing is a type of attack in which the From address of an email message is forged. A spoofed message appears to be from the impersonated organization or domain.
It basically prevents your email from being forged by someone else.
Mail Exchanger Record (MX Recor) specifies the mail server responsible for accepting email messages on behalf of a domain name.
It basically lets another know which server can send an email for you, and where incoming emails should be routed to.
All four elements allow verifying the authenticity of each email sent. The more you’re set-up, the better another server will trust you, enhancing your deliverability.
It’s that logic! Now let’s set up everything up.
You need to include Google and La Growth Machine in your SPF.
v=spf1 include:_spf.google.com include:spf.lagrowthmachine.com ~all
If you already have an SPF record, you must merge them into one line. You can’t have two separate SPF records.
Google handles DKIM, and you must activate it in your Google Admin console:
To monitor and enforce your email authentication policy:
Add the following TXT record to your DNS:
Name: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]
Replace “[email protected]” with your actual monitoring address. You can later change “p=none” to “p=quarantine” or “p=reject” once you’re confident everything is working.
To check if it’s correctly set up you can use Google Admin Toolbox CheckMX or test a sent email at “mail-tester.com”
v=spf1 include:spf.protection.outlook.com include:spf.lagrowthmachine.com ~all
You can only have one SPF record. If you already have one, you must merge it with the one above.
Go to your Microsoft 365 admin interface: https://security.microsoft.com/dkimv2
Navigate to:
Email & collaboration → Policies & rules → Threat policies → DKIM
Select your domain.
Copy the two CNAME records provided by Microsoft.
Add them to your domain’s DNS zone.
Once the DNS changes have propagated, return to the admin interface and click Enable.
Name: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]
Replace “[email protected]” with your own email to receive reports. You can change “p=none” to “quarantine” or “reject” later if needed.
To check if everything is working you can send a test email from your account to https://www.mail-tester.com or use Microsoft’s built-in reporting in the Microsoft 365 Admin Center.
Most outreach tools track clicks on links using redirect domains. The problem is that when hundreds or thousands of users share the same default tracking domain, it often gets flagged or blacklisted.
That’s why setting up your own custom tracking domain is a game-changer.
Instead of using a shared link like “tracking.emailplatform.com”, you can create your own, like “click.yourcompany.com”.
This creates a consistent digital footprint and builds trust with both email providers and recipients. It also reduces the likelihood that your links are filtered or flagged, which directly improves click-through rates and deliverability.
To set-up your CDT login to your domain provider, access the DNS settings and create your new CNAME record.
Here are the instructions for the most common domain providers:
• BlueHost
• Cloudflare (your proxy must be deactivated)
• GoDaddy
• OVH
That’s it, let’s move on to the next chapter : How to succeed with warm calling?
Course content
Resources
Congrats
You are now an expert ! 🎉
Not an LGM user yet? Sign up and put everything you’ve just learned into practice!
Leaving already?
Discover our B2B outreach expert community