> For the complete documentation index, see [llms.txt](https://docs.keeping.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeping.com/help/setup/connecting-a-mailbox/custom-domains.md).
# Custom domains
## What is a custom domain?
When you connect your shared mailbox to Keeping using forwarding, Keeping sends support mail to your customers on your behalf. So while your customers **will always receive email from your shared mailbox's email address**, some email providers append a *via keeping.com* in the header of your reply.
If you'd like to remove the *via keeping.com* from your support mail replies, Keeping offers the ability to set up a custom domain. This requires that you have the ability to add two `TXT` records to your DNS settings. Once configured, the *via keeping.com* will be removed from all replies to your customers.
{% hint style="success" %}
If you use "Sign in with Google" to connect your mailbox to Keeping, you do NOT need a custom domain.
{% endhint %}
## Setting up a custom domain
{% hint style="warning" %}
You, or someone in your organization, will need to be able to access your DNS settings for your domain in order to set up a custom domain.
{% endhint %}
You can generate them yourself from your mailbox settings.
1. Go to **Settings → Mailboxes** and click the "pencil" icon next to the mailbox you want to set up.
2. Click **Get DNS Records**. (This option appears for mailboxes connected via forwarding on a custom domain. It won't show for mailboxes signed in with Google.)
3. In the window that opens, click **Email Records to Me**. Keeping generates your two TXT records — one **SPF** and one **DKIM** — and emails the exact values to your account's email address within a few moments.
4. Add both records to your DNS provider, following the step-by-step values in the email.
* If you already have an SPF record for your domain, **don't add a second one** — DNS allows only one SPF record per domain. Instead, merge `include:mailgun.org` into your existing record (e.g. `v=spf1 include:_spf.google.com include:mailgun.org ~all`).
5. Once both records are live, **reply to the records email** so our team can verify everything is configured correctly and finish enabling your custom domain.
That's it — once verified, your replies will send from your own domain with no "via keeping.com" tag.
### How do custom domains work?
When you request a custom domain, we'll supply you with a SPF and DKIM records. Email providers (ISPs) use SPF and DKIM records to confirm that you have approved the sending of email from a specific third party (such as Google or Keeping).
In most cases, Keeping works fine without a custom domain. However, if your organization has implemented [a DMARC policy ](https://www.dmarcanalyzer.com/what-is-a-dmarc-policy/)of `reject` or `quarantine`, **then a custom domain is essential**. This is because these policies tell other ISPs that you do NOT approve of any email sent from domains without appropriate SPF and DKIM records, and replies sent via Keeping *could* end up in your customer's spam folder.
{% hint style="info" %}
Read More: [**SPF and DKIM Explained** ](https://netcorecloud.com/tutorials/spf-dkim-dmarc/)(on netcorecloud.com)
{% endhint %}
### Do I need a custom domain if I connect my mailbox directly to Keeping?
If you use "Sign in with Google" to connect your mailbox to Keeping, then **you do NOT need a custom domain**. This is because Keeping is sending email directly from your own domain and it will never show up with the *via keeping.com* callout.
### Is there an extra charge or fee for a custom domain?
Nope! Custom domains are offered for all plans **free of charge**.
#### Still have questions? Then drop us a line at and someone will jump in to lend a hand.