# Do I Need A Domain To Send Emails With Amazon SES ?

To send email, Amazon SES requires that you verify your email address or your domain.

If you send emails without verifying your domain, the recipient’s email client displays **“sent via amazonses.com”**. This is because by default emails from Amazon SES are sent from their domain *amazonses.com*. &#x20;

When you verify your domain with Amazon SES …

1. Your emails are sent as originating from your domain and not from *amazonses.com*. Trust-wise, it is always better to show the recipient of your email that the email originated from your organization/company’s domain.
2. You can also setup other things like [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework), [DKIM](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail), [DMARC](https://en.wikipedia.org/wiki/DMARC), etc., which greatly enhance email deliverability.
3. You are verifying all email addresses from that domain, so you don’t need to verify individual email addresses from that domain. For example, if you verify the domain *xyz.com*, you can send email from *<user1@xyz.com>*, *<user2@xyz.com>*, or any other user at *xyz.com*.

**So it is always recommended that you verify your domain with Amazon SES**.

While all this sounds technical and cumbersome, it is actually quite easy to do these setups via [**Send With SES**](https://sendwithses.com/).

**Need help? Write to <help@sendwithses.com>**


---

# 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://docs.sendwithses.com/faqs/email-faqs/do-i-need-a-domain-to-send-emails-with-amazon-ses.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.
