Sending Domains
Add and verify sending domains, then create sending addresses your workspace can use for live email delivery.
Overview
The Domains area in workspace settings is where you manage the sending domains and sending addresses used by a workspace. This is the workspace-level view of the email identity setup required before live sending.
From this page, you can:
- add a new top-level sending domain
- choose the configured provider for that domain
- open the DNS records required for verification
- verify the domain after DNS is published
- add sending addresses under a verified or pending domain
- review and delete existing domains or sending addresses
If you are setting up a workspace for the first time, you may also want the broader onboarding guide at Add a Sending Domain.
Before you start
- Open the correct workspace before managing domains, since domains and sending addresses are workspace-specific.
- You need write access in the workspace to create or delete domains and addresses.
- Have access to the DNS settings for the domain you plan to use.
- Have a monitored inbox ready for each sending address so you can receive its verification email.
Before you can send live email, the top-level domain must be verified through DNS, and each sending address also requires its own verification email step.
Open Domains in the dashboard
Open your workspace
Go to the Dashboard and switch into the workspace you want to manage.
Open Settings
Use the main navigation to open Settings.
Go to Domains
Open Domains from the Email section.
Add a sending domain
Click the Domain button
On the Domains page, click the Domain button in the top-right corner.
Enter the domain
Provide the top-level sending domain, such as example.com.
Choose the provider
Select the configured provider for the domain:
LeadpushAWS SES
Create the domain
Click Create to add the domain record to the workspace.
View DNS records and verify the domain
Find the domain
Locate the domain in the Domains table.
Open View DNS
Use View DNS to open the domain verification modal.
Add the DNS records
Copy the records shown in the modal and publish them with your DNS provider.
Run verification
Click Verify after the DNS records are published.
Confirm the status
Return to the Domains table and confirm the domain verification status updates appropriately.
The Domains table also shows:
- the domain name
- the configured provider
- the current verification status
- the created date
Add a sending address
Expand the domain row
Open the domain row to reveal the Sending Addresses section.
Click Add Sending Address
Use Add Sending Address for the domain you want to send from.
Enter the sender details
Complete the required fields:
- sending address local part
- display name
- reply-to address
- company address
- city, state, and zip
- country
Create the address
Click Create to save the sending address.
Complete address verification
Check the inbox for that address and click the verification link within 24 hours.
Review sending addresses
Each expanded domain row shows the sending addresses currently available for that domain.
Use that list to review:
- the full sending address
- the display name
- the current verification status
Delete a domain or sending address
Find the record
Locate the domain in the Domains table or the sending address in the expanded addresses list.
Open row actions
Use the action menu for the domain, or the delete action shown next to the sending address.
Confirm the deletion
Choose Delete and confirm the action.
Verify it is gone
After deletion, the domain or address should no longer appear in the list.
DKIM selectors
DKIM selectors are the label portion of a DKIM DNS record that appears before ._domainkey. For example, in s1._domainkey.example.com, the selector is s1.
Leadpush creates two DKIM records for each Leadpush-managed sending domain. By default, those selectors are s1 and s2.
What DKIM is
DKIM stands for DomainKeys Identified Mail. It is an email authentication standard that lets a sending provider sign outbound messages with a private key.
The matching public key is published in DNS. When a receiving mailbox provider gets the message, it can look up that public key and verify that:
- the message was signed by a sender authorized to use the domain
- the signed parts of the message were not changed in transit
In practice, DKIM helps mailbox providers trust mail from your domain and is a core part of modern domain authentication alongside SPF and DMARC.
Why there are two DKIM selectors
Leadpush creates two DKIM selectors so the domain has more than one signing key available.
This makes key rotation and provider-side maintenance safer. One selector can remain active while another is introduced, updated, or promoted without forcing an immediate DNS replacement on a live sending domain.
You can think of S1 and S2 as two DKIM slots for the same domain. Most of the time you do not need to manage that directly, but both records should be published exactly as shown in the DNS instructions.
Why you might need custom selectors
You may need custom selectors if the domain already has DKIM records using s1 or s2 from another email provider, an older email platform, or a previous Leadpush setup.
This matters because DNS providers only allow one record set for the same host name. If s1._domainkey.example.com already exists and points somewhere else, the new Leadpush DKIM record will conflict with it.
Choosing custom selectors gives Leadpush unique DKIM host names, such as primary._domainkey.example.com and backup._domainkey.example.com, so you can publish the records without overwriting another provider's DKIM setup.
If you are replacing another provider, do not delete or overwrite working DKIM records until you are ready to move traffic. Use unique selectors first, then cut over deliberately.
Set custom selectors when creating a domain
Custom selectors are available when the provider is set to Leadpush.
Open the create domain slider
From Settings > Domains, click the Domain button.
Enter the domain and select Leadpush
Provide the top-level domain and choose Leadpush as the provider.
Open Custom DKIM Selectors
Expand the Custom DKIM Selectors accordion in the create form.
Enter the selector values
Fill in S1 Selector and S2 Selector with DNS-safe labels up to 10 characters each.
Good examples:
primarybackupmktgtxnl
Create the domain
Click Create. Leadpush will generate DNS records using the selector values you entered.
Publish the returned DNS records
Open View DNS for the new domain and publish the DKIM records exactly as shown.
Custom tracking domains
A custom tracking domain is the branded subdomain Leadpush uses for click tracking links, such as click.example.com.
Using a branded tracking domain can make tracked links look more consistent with your sending domain instead of using a shared provider hostname.
Add a custom tracking domain when creating a domain
Custom tracking domains are available when the provider is set to Leadpush.
Open the create domain slider
From Settings > Domains, click the Domain button.
Enter the domain and select Leadpush
Provide the top-level domain and choose Leadpush as the provider.
Open Custom Tracking Domain
Expand the Custom Tracking Domain accordion in the create form.
Enter the tracking subdomain
Fill in Tracking Subdomain with a single DNS label, such as click or links.
Do not enter the full hostname. If the domain is example.com, entering click will create the tracking hostname click.example.com.
Choose the tracking mode
Select the tracking mode that matches how you want the tracking hostname to work.
Directis the default option and uses the standard Leadpush tracking CNAME setup.Cloudflareis for tracking hostnames that will be proxied through Cloudflare.
Create the domain
Click Create. Leadpush will generate the tracking-domain DNS record along with the rest of the required DNS records for the domain.
Publish the returned DNS records
Open View DNS for the new domain and publish the tracking-domain CNAME exactly as shown.
If the tracking hostname already exists in DNS, choose a different subdomain label instead of overwriting an active record without planning the cutover.
Tracking modes
When you create a custom tracking domain, Leadpush lets you choose how the tracking hostname should be routed.
Direct
Use Direct when you want to publish the tracking CNAME directly in DNS without putting the hostname behind Cloudflare proxying.
This is the simplest setup and is the default mode in the create domain form.
Cloudflare
Use Cloudflare when the tracking hostname will be managed through Cloudflare and proxied there instead of resolving as a standard DNS-only CNAME.
Choose this mode only if the tracking hostname is on a domain you control in Cloudflare and you plan to proxy the returned tracking host through Cloudflare.
If you choose Cloudflare, publish the returned tracking hostname in Cloudflare and keep the record proxied so the branded tracking host can be verified correctly.