Email Domains
What is an Email Domain?
By default, eCourtDate sends email using an eCourtDate address (like {agency}@ecase.io). An email domain lets your agency send and receive messages from its own domain instead, so notifications come from an address like notifications@email.youragency.gov.
This works through DNS (Domain Name System), the internet's address book that maps domain names to servers. Setting up an email domain means adding a few DNS records that authorize eCourtDate to send email on behalf of your domain and that prove you control it.
Email domains are managed in the eCourtDate Console under the Domains section. Email delivery is handled through Amazon SES, so the DNS records you add point to Amazon SES infrastructure.
Why agencies use email domains
- Credibility and branding: messages come from your agency's domain, which recipients recognize and trust.
- Deliverability: SPF, DKIM, and DMARC authentication records improve inbox placement and reduce spam flagging.
- Security and privacy: authentication records protect against spoofing and phishing that impersonate your agency.
- Unlimited addresses: create as many email addresses as you need under a verified domain.
- Inbound email: receive email directly to your custom domain when MX records are configured.
Choosing your domain
Use a subdomain of your agency's domain for your eCourtDate email domain, such as notifications.agency.gov or email.agency.gov. A subdomain:
- Protects your primary email reputation. eCourtDate notification volume builds its own sending reputation on the subdomain, so a deliverability issue or the initial warm up period does not affect the email your staff send from your root domain.
- Supports inbound email safely. Inbound email requires MX records. Adding MX records to your root domain would redirect all of your agency's mail to eCourtDate. A subdomain keeps inbound separate.
- Avoids SPF conflicts. A domain can have only one SPF record. On a dedicated subdomain you add the eCourtDate SPF record cleanly, instead of editing the SPF record your existing mail already depends on.
- Keeps your branding. A subdomain such as
notifications.agency.govstill clearly identifies your agency to recipients.
Do not use your root agency domain (for example, agency.gov) for an eCourtDate email domain. Adding MX records redirects all inbound mail for that domain to eCourtDate, editing its SPF record can disrupt your existing mail, and eCourtDate sending volume can affect the reputation your staff email depends on. Always use a subdomain.
Next steps
- Email Domain Setup: create and configure an email domain in the Console.
- DNS Records: the verification, SPF, DKIM, DMARC, and MX records to add.
- Verification and Monitoring: confirm ownership and read the Monitoring Report.
- Troubleshooting: resolve deliverability and inbound email issues.