# Why should I configure a sending domain for an email signature tool?

### Why DNS?&#x20;

When you set up a signature in Scribe, it contains numerous URLs (such as logos, profile pictures, icons, website addresses, etc.)\
\
To track the conversion rate from your signature's marketing elements, all these URL domains are shortened using our default domain, sendassets.io.\
\
While you can retain this domain, it's not the optimal choice. Spam filters tend to flag emails containing numerous URLs that point to a different domain than the sender's email domain.\
\
That's why we offer the option to replace this default domain with a subdomain from your primary domain. This subdomain is referred to as a sending domain.\
\
For instance, if your email address is <joe@my-company.com> you can configure a sending domain such as `email-signature.my-company.com` to keep spam filter content.

{% embed url="<https://www.youtube.com/watch?v=ZaqAxlI656Y>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.scribe-mail.com/scribe/dns/why-should-i-configure-a-sending-domain-for-an-email-signature-tool.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
