​
Overview

To use our outbound SMTP service, your domain must have proper email authentication records configured. These authentication mechanisms work together to verify your emails are legitimate and help ensure successful delivery to recipient inboxes.
Domains without proper email authentication may experience delivery issues or have their emails rejected by our service.

​
Automatic vs Manual Setup

​
Dashboard Setup (Automatic)

If you set up your domain through our dashboard, these authentication records are automatically generated and configured for you. No manual DNS configuration is required.

​
Control Panel Setup (Manual)

If you’re using a control panel (such as cPanel, Plesk, or DirectAdmin) or managing DNS manually, you’ll need to ensure these records are properly configured yourself following the instructions below.

​
Required Authentication Records

​
1. SPF Record (Required)

Sender Policy Framework (SPF) specifies which mail servers are authorized to send emails on behalf of your domain. Required SPF Record: 
v=spf1 include:spf.jetemail.net ~all
Add this as a TXT record to your domain’s DNS settings. For detailed SPF configuration instructions, see our SPF Record guide.

​
2. DKIM Record (Required)

DomainKeys Identified Mail (DKIM) adds a digital signature to your emails, allowing recipients to verify that emails haven’t been tampered with during transit. Required DKIM CNAME Record: 
Name: dkim._domainkey.{your-domain}
Value: dkim.jetsmtp.net
Replace {your-domain} with your actual domain name. For example, if your domain is example.com, the CNAME record would be: 
Name: dkim._domainkey.example.com
Value: dkim.jetsmtp.net

​
3. Feedback Record (Required)

Feedback CNAME Record is required for proper email authentication and monitoring. Required Feedback CNAME Record: 
Name: jetemail._feedback._domainkey.{your-domain}
Value: feedback.jetsmtp.net
Replace {your-domain} with your actual domain name. For example, if your domain is example.com, the CNAME record would be: 
Name: jetemail._feedback._domainkey.example.com
Value: feedback.jetsmtp.net

​
4. DMARC Record (Required - Can be Non-Enforcing)

Domain-based Message Authentication, Reporting & Conformance (DMARC) builds on SPF and DKIM to provide additional protection against domain spoofing. Minimum Required DMARC Record: 
v=DMARC1; p=none
This creates a monitoring-only policy that doesn’t reject emails but provides visibility into authentication results. For detailed DMARC configuration, see our DMARC guide.

​
Why These Records Are Required

​
Email Deliverability

Modern email providers (Gmail, Outlook, Yahoo, etc.) increasingly require proper authentication to accept emails. Without these records:
  • Your emails may be marked as spam
  • Recipients may reject your emails entirely
  • Your domain reputation may be damaged

​
Security Benefits

  • Prevents domain spoofing: Stops attackers from impersonating your domain
  • Protects your reputation: Ensures only authorized servers can send on your behalf
  • Builds trust: Recipients can verify your emails are legitimate

​
Compliance

Many email providers now require DMARC records as a minimum standard for email authentication.

​
Getting Started

  1. Configure SPF: Add our SPF record to your DNS
  2. Set up DKIM: Add the DKIM CNAME record to your DNS
  3. Add Feedback Record: Configure the required feedback CNAME record
  4. Create DMARC: Start with a monitoring policy (p=none)
  5. Test your configuration: Use email authentication testing tools to verify setup

​
Need Help?

If you need assistance configuring any of these authentication records, please contact our support team. We’re here to help ensure your domain is properly configured for optimal email delivery.