# Does an AI agent need its own domain for email?

No. An agent can have a working email address without owning a domain:
an address on a provider's domain, such as `ada@botmail.pro`, sends and
receives like any other, and the provider maintains the DNS records that
make mail trusted. A domain of your own is worth it when the address
carries your brand, when you send enough mail that you want your own
reputation, or when you might change providers and need to keep the
address. Until then it's setup and upkeep you don't need.

## What a domain buys you

- **Your brand on the From line.** `support-agent@yourco.com` looks like
  part of your company. `ada@botmail.pro` looks like an agent, which is
  honest but not branded.
- **Reputation that's only yours.** Gmail
  [tracks volume, feedback and limits per domain and IP address](https://support.google.com/mail/answer/81126).
  On a shared domain, other senders' behaviour is part of the picture; on
  your own, only yours is.
- **Portability.** The address belongs to you, so you can move between
  email providers without telling anyone a new address.
- **Control of the policy.** You decide the DMARC policy, which servers may
  send as you, and where reports go.

## What a domain costs you

Registration is the cheap part. The work is in DNS and reputation:

| Task | Why it's needed |
| --- | --- |
| MX records | So mail to the domain reaches your provider |
| SPF or DKIM | Google requires one of them for anyone sending to Gmail accounts |
| SPF, DKIM and DMARC, aligned with the From domain | Required by Google once you send more than 5,000 messages a day to Gmail |
| Reverse DNS on sending IPs | Also on Google's list; your provider usually handles it |
| One-click unsubscribe | Required for marketing and subscribed mail at bulk volume |
| Warming up | Google advises increasing volume slowly on a domain, and monitoring it in Postmaster Tools |

The requirements above are from Google's
[email sender guidelines](https://support.google.com/a/answer/81126),
checked in October 2026. Google also says that new domains face
[faster enforcement](https://support.google.com/a/answer/14229414) of those
rules. A brand-new domain that starts sending an agent's cold outreach is
exactly the pattern spam filters are built to catch.

A mistake costs more on your own domain, too: if an agent misbehaves and
the domain's reputation drops, your people's mail from that domain can
suffer with it. If you do use your own domain, consider a separate
subdomain such as `agents.yourco.com` for agent mail, so problems are
easier to spot and contain.

## Shared domain vs your own

| | Address on a provider's domain | Your own domain |
| --- | --- | --- |
| Setup | Minutes, no DNS | Registrar, DNS records, verification |
| Authentication records | Maintained by the provider | Yours to set up and keep correct |
| Reputation | Shared, managed by the provider's limits and checks | Yours alone, built over time |
| Branding | Provider's name | Yours |
| Keep the address if you switch | No | Yes |
| Good for | Verification codes, notifications, prototypes, agent-to-agent mail, low-volume replies | Customer-facing mail, high volume, regulated industries |

## When to get one

Get a domain when one of these is true:

1. Customers will see the agent's address and should recognise your brand.
2. The agent sends thousands of emails a day, or marketing-style mail.
3. You need the address to outlive the provider you use today.
4. Your security or compliance team requires mail from your own domain.

Skip it when the agent mostly receives mail (sign-up codes, receipts,
reports), sends a few replies a day, or is still an experiment.

## How Botmail handles it

Botmail gives each agent an address on `botmail.pro`, with no domain or DNS
on your side. The domain signs mail with DKIM, publishes SPF on an aligned
sending subdomain, and has a DMARC policy of `quarantine`. Because the
domain is shared, Botmail protects it for everyone: mail to new recipients is
checked for spam and phishing before it's sent, and new accounts can email
25 new recipients a day at first, rising as the account earns trust.

Botmail doesn't support custom domains. If you need the agent on
`yourco.com`, use an email provider that sends from your domain and accept
the setup above. You can still start on Botmail and move later, as long as
you tell the services the agent signed up for about the new address.

Read more in [How do AI agents send and receive email?](https://botmail.pro/questions/how-do-ai-agents-send-and-receive-email)
or set one up with [Give your AI agent an email address](https://botmail.pro/guides/give-your-ai-agent-an-email-address).

## Questions

### Can I get an email address for an AI agent without a domain?

Yes. A service like Botmail gives the agent an address such as ada@botmail.pro on its own domain, with the DNS and authentication records already in place. There's nothing to register or configure.

### What DNS records does a domain need to send email to Gmail?

Google requires SPF or DKIM for all senders. Above 5,000 messages a day to Gmail accounts you also need DMARC, with the From domain aligned to SPF or DKIM, plus valid reverse DNS and one-click unsubscribe for marketing mail.

### When should an AI agent use my company's domain?

When customers see the address and should recognise your brand, when the agent sends high volumes, when you need to keep the address across providers, or when compliance requires your own domain.

---

Source: https://botmail.pro/questions/does-an-ai-agent-need-a-domain
Agent instructions: https://botmail.pro/skill.md
All guides: https://botmail.pro/llms.txt