Domains

The Domains screen helps you set up everything that makes your emails look trustworthy to inbox providers: the DNS records of your sending domain, proof that you own your from addresses, and an optional tracking domain for the links in your emails. Landing pages can also get their own domain; that is set on the landing page itself.

You need the Admin role or higher to use this screen. Open it from Settings: click Open domains in the Authenticate your domain box.

Add a sending domain

Your sending domain is the part after the @ in your from address, for example example.com in news@example.com.

  1. Go to Settings and click Open domains.
  2. In the Sending domains box, type the domain in the Domain field. Type only the name, without http:// or a path.
  3. Click Add domain.

The domain's page opens and lists the three records it needs, under Records to add.

Record Type Name What it does
SPF TXT your domain Lists the servers that may send email for your domain.
DKIM TXT or CNAME selector._domainkey.your domain Holds the key that inboxes use to check your emails' signature.
DMARC TXT _dmarc.your domain Tells inboxes what to do with emails that fail SPF and DKIM, and where to send reports.

When you add a domain, SendKettle fills in the SPF include and, for SendGrid and Resend, the DKIM selector of the provider you picked under Settings. For other providers the selector starts as mail.

Make the records match your provider

Your sending provider creates the DKIM key, so its dashboard shows the exact values. Copy them into SendKettle so the records on screen match exactly.

  1. Open your provider's dashboard and find the page for your domain.
  2. On the domain's page in SendKettle, go to the Record settings box.
  3. In DKIM selector, type the part of the DKIM name before ._domainkey, for example s1 or pm.
  4. In SPF include, type the name after include: in your provider's SPF value, for example mailgun.org.
  5. In DKIM value, paste the DKIM value. This is either a TXT value with p= in it, or, for providers that use a CNAME, the name the CNAME points to.
  6. Click Save record settings.

Changing these settings clears the last check, so check the records again afterwards.

With Built in sending: SendKettle makes the DKIM key

When your workspace sends Built in in SendKettle Cloud (see Sending and deliverability), there is no provider dashboard to copy from. SendKettle makes a DKIM key for each sending domain instead, and the domain's page shows these records:

Record Name Value
SPF (optional) your domain v=spf1 include:_spf.sendkettle.com ~all, or add include:_spf.sendkettle.com to the SPF record you have. Not needed: bounces come back to SendKettle, so SPF passes for SendKettle's own address.
DKIM sk1._domainkey.your domain v=DKIM1; k=rsa; p=..., the exact value from the page
DMARC _dmarc.your domain v=DMARC1; p=none; rua=mailto:dmarc@your domain

Copy the whole DKIM value into one TXT record. It is longer than 255 characters; most DNS hosts split it for you, and the check reads it back as one value. The private key stays on our server and is never shown, so there is nothing to keep safe on your side. The DKIM key box replaces Record settings.

Your emails are signed with the key once DKIM and DMARC pass; a failing SPF check is shown as a warning and doesn't stop that. DKIM alone already lines up with your from address, which is what DMARC checks.

When you switch the workspace between your own provider and Built in under Settings, every sending domain is checked again with the records the new route needs. A domain that passed with your provider's DKIM record is not verified for Built in until the record for SendKettle's own key passes, and the other way round. You can only send from it once it shows Verified again.

Rotate the key

To replace the key, for example once a year, click Rotate key in the DKIM key box. SendKettle makes a new key with the next selector, such as sk2, and shows its record as DKIM (new key):

  1. Add the new TXT record. Keep the old one for now: emails are still signed with the old key.
  2. Click Check DNS records. As soon as the new record passes, the new key signs your emails and the old key is removed.
  3. Delete the old record, for example sk1._domainkey.your domain. The message after the check names it.

Add the records and check them

  1. Log in at the company where you manage your domain's DNS, often the place where you bought the domain.
  2. Add each record from Records to add with the type, name and value shown. Some DNS hosts add your domain to the name for you; if so, type only the part before your domain.
  3. Back in SendKettle, click Check DNS records at the top of the domain's page.

Each record then shows Passed or Failed, what was found, and how to fix it. When SPF, DKIM and DMARC all pass, the domain shows as Verified. DNS changes can take from a few minutes to a few hours to show up, so if a record you just added fails, wait a while and check again.

SendKettle checks every verified domain again once a day. If its records are missing three days in a row, the domain loses its verification and the workspace's Admins get an email. Email from that domain is then no longer sent as the domain until you add the records again and click Check DNS records.

What the checks look for

Record Passes when
SPF There is exactly one SPF record, it contains the include for your provider, and it doesn't end with +all.
DKIM A key is published at the selector name and isn't empty. If you pasted a value, the published key must be the same. If your provider uses a CNAME, the CNAME must point to the name you pasted.
DMARC There is exactly one DMARC record and it has a policy: p=none, p=quarantine or p=reject.

Start DMARC with p=none. That only collects reports. Once the reports look clean, you can move to p=quarantine and later p=reject.

Verify a from address

Verifying a from address proves that you can receive email there, so nobody on your team sends as an address that isn't yours.

  1. Go to Settings and click Open domains.
  2. In the From addresses box, type the address in Email address and click Send code.
  3. Open the email we sent to that address and copy the six digit code.
  4. Type the code next to the address in the Code field and click Verify.

The address then shows as Verified. A code works for 30 minutes. After five wrong tries it stops working; click Send a new code to get a fresh one. You can ask for a new code once a minute, and at most five times a day. Each address gets ten wrong codes a day in total, also across new codes and after removing and adding it again; after that, try again the next day.

Sending needs a verified, authenticated sender

Once a sending provider is connected under Settings, a campaign only goes out when:

  • its from address is verified with a code, or its domain is a verified sending domain, and
  • SPF, DKIM and DMARC passed for the from domain itself, so DKIM signs for that domain and the email passes DMARC alignment. Gmail and Yahoo require this for bulk mail. A parent domain doesn't count: for news@mail.example.com, add mail.example.com as its own sending domain.

The From and Sender authentication items on the Preview & checklist screen show red until both are true, and Send now and Schedule stay blocked. The rules are checked again for every email while a campaign goes out: if a domain or address loses its verification halfway, the campaign is paused and a red message on it says why. Fix the domain or address, then click Resume sending. Automation emails from an unverified sender are marked as failed instead.

A passed check stays valid, but after 30 days the checklist shows a warning so you look at the records again.

While emails only go to the log (no provider connected), nothing is blocked and the items are warnings.

If you have to send from a verified address on a domain you can't authenticate, an Admin can tick Also allow verified from addresses on domains without SPF, DKIM and DMARC in the Sender authentication box and click Save. The checklist then shows a warning instead of an error. Such emails often fail DMARC and land in spam, so use this only as a stopgap. Unverified addresses are never allowed. The change is recorded in the audit log.

In the cloud: your email goes out right away

In SendKettle Cloud you can send from the first day, without a domain of your own. Until your domain is connected, every email goes out from your own SendKettle address, for example:

Duranet via SendKettle <duranet@send.sendkettle.com>

  • The name is your from name, followed by "via SendKettle". It falls back to your default from name under Settings, Sender defaults, which starts as your company name.
  • The address is fixed for your workspace and made from your company name. A name with a well-known brand or SendKettle in it gets a neutral address such as team-x7k2pq instead. You can't pick or change it, and no other account ever gets it.
  • Replies go to your own address: the campaign's reply-to address if you set one, otherwise your from address.
  • If someone still replies to the SendKettle address itself (some mail programs and automatic replies do), we forward that reply to the Reply-to email under Settings, Sender defaults (or else your default from address), and it also shows in the shared inbox. A paused account gets no forwarded replies.
  • The footer still shows your company name and postal address, and the unsubscribe link works as always.
  • SPF, DKIM and DMARC pass for SendKettle's address, so these emails don't land in spam because of authentication.

This works for campaigns, journeys, test emails, transactional email and answers from the shared inbox. A message sent as raw MIME (the send-raw API and the SMTP relay) is passed on exactly as it is, so it can't be rewritten: it still needs a connected domain.

The checklist shows one From item with what recipients will see, and the campaign shows a tip once: Tip: send from your own address. Click Hide this tip to hide it for the whole workspace.

Connect your own domain

Connecting your domain is optional. Once it is connected, your email goes out from your own address, such as jayden@duranet.nl. Click Connect domain in the tip, or add the domain under Settings, Domains. The domain's page offers three ways:

  • Send to my IT person: type their email address and an optional note. They get the exact records with a short explanation in an email from SendKettle that names your email address, and their reply comes to you. Links in the note are left out. You need to have confirmed your own email address. You can send this five times a day per account, and the same address gets it at most three times a day; it is recorded in the audit log.
  • Connect automatically at …: shown only when your DNS host supports it (see below). You sign in at your DNS host and approve the record there.
  • Add the records myself: copy the records and click Check DNS records.

On a paid plan the page stays simple: the records themselves and the provider settings are only shown on the free plan or in developer mode. Your IT person gets the records by email, and Check again tells you when the domain is connected.

With Built in sending, the DKIM record (sk1._domainkey) and DMARC are what count. SPF is optional: bounces come back to SendKettle's own address, so SPF passes there and your SPF record needs no change. If your domain already has a DMARC record, keep it.

Connect automatically

Some DNS hosts support Domain Connect: SendKettle sends you to your DNS host, you approve the DKIM record there, and you come back to the domain's page. The button only shows when your DNS host has said it knows SendKettle's template. Until then, use one of the other two ways.

With a sending provider of your own

When your workspace sends through its own provider under Settings, Sending provider, that provider can't send SendKettle's address. Your from domain then has to be connected before you can send, and the domain's page shows one more record, Ownership (_sendkettle-verify.your domain), which proves the domain belongs to your workspace. A DKIM record alone proves too little, because anyone can publish a key at a selector they choose.

The platform's own domains and their subdomains can't be added as sending domain, from address, tracking domain or page domain. A domain connected in another workspace or another account doesn't count: each workspace connects its own.

Use your own tracking domain

The links in your emails (open tracking, click tracking, unsubscribe and the web version) normally use the address of your SendKettle. With a tracking domain they use a domain of your own, such as links.example.com.

  1. Go to Settings and click Open domains.
  2. In the Tracking domain box, type the domain in Domain and click Save tracking domain.
  3. At your DNS host, add a CNAME record with the name shown under Name and the value shown under Value. The value is the address of your SendKettle. Also add the TXT record shown under it, on _sendkettle-verify. followed by your domain. Its value is different for every workspace and proves the domain belongs to this one, so nobody in another workspace can use a domain you pointed here.
  4. Click Check CNAME.

When the CNAME and the TXT record are right, the box shows In use and every new email uses the tracking domain. Emails that were already sent keep their old links, and those keep working. If a landing page saved the domain first without ever verifying it, add the CNAME and your TXT record and save again: the domain then becomes your tracking domain.

Check that the domain works over HTTPS

The CNAME only tells inboxes where to go. Your server also needs a certificate for the domain, and it has to pass the requests on to SendKettle. Once the CNAME passes, the box shows an HTTPS line.

  1. Click Web server settings under HTTPS. You see a ready-made setup for Caddy and for nginx with your domain filled in. Send it to whoever runs your server, or follow Custom domains on your server.
  2. When the server is set up, click Check HTTPS.
  3. SendKettle opens https:// followed by your domain and /.well-known/sendkettle-check. If the answer comes from this SendKettle installation, the line shows Ready.

If the check fails, the box shows Not working yet and what went wrong, for example a certificate problem or another website answering on the domain. Fix it and click Check HTTPS again. New emails use the tracking domain as soon as the CNAME passes, so do the HTTPS check before you send a campaign.

To stop using the tracking domain, clear the Domain field and click Save tracking domain.

Buy a domain

You can buy a new domain for a website or landing page without leaving SendKettle. The purchase goes through your own Name.com account and is paid with the payment method saved there. You need the Admin role.

  1. At Name.com, open Account, Settings, Security, API Access and create an API token.
  2. In SendKettle, open Settings, Domains and click Buy a domain.
  3. Under Name.com account, type your Username and API token and click Save Name.com settings. The token is stored encrypted. Tick Test mode to try it with the Name.com test environment and a test token first; nothing is bought then.
  4. Under Find a domain, type a name such as corner-bakery and click Search. SendKettle tries .com, .net, .org, .shop, .nl and .eu. Type a full name such as cornerbakery.de to check just that one.
  5. Next to a free domain you see the price for the first year and for each year after. Tick I want to buy it and click Buy, then confirm.

SendKettle checks the price again just before it buys. If it changed, nothing is bought and you are asked to search again. Every purchase is in the audit log. The domain is registered for one year with the contact details, privacy and automatic renewal of your Name.com account.

Point the domain at a website

Under Your domains:

  1. Type the Name to use, for example www for www.corner-bakery.com.
  2. Under Use it for website, choose the website, or leave No website yet.
  3. Click Point at SendKettle.

SendKettle adds the CNAME record at Name.com. When you chose a website, the name is filled in as its custom domain. Click Check CNAME on the website a few minutes later, then follow the HTTPS steps (see Websites).

Transfers, renewals and contact details stay in your Name.com account.

Common problems

"Enter a domain name such as example.com, without http:// or a path."

Type only the name, for example example.com or links.example.com. Addresses such as https://example.com/page, IP addresses and internal names like localhost are not accepted.

"There are 2 SPF records."

A domain can only have one SPF record. Combine them into one: keep one v=spf1 at the start and one ~all at the end, and put all the include: parts in between.

The DKIM check fails but my provider says the domain is verified

Check that the DKIM selector matches the name your provider uses. The DKIM record lives at selector._domainkey.yourdomain, so a different selector means SendKettle looks in the wrong place.

The CNAME check fails for my root domain

A root domain such as example.com can't have a CNAME. Point its A record at the same IP address as your SendKettle instead. The check passes when both addresses match.

"answered, but not with this app's check code"

The domain reaches a web server, but not this SendKettle installation. Often the web server shows its own welcome page or another website for that name. Add the domain to the server block of SendKettle, see Custom domains on your server.

"Addresses on private or internal networks are not allowed."

The domain points to an address inside your own network. The HTTPS check only calls public addresses, so it can't check this domain. Inboxes outside your network can't reach it either.