Skip to main content

Email Domains

What is an Email Domain?​

By default, eCourtDate sends email using an eCourtDate address (like {agency}@ecase.io). An email domain lets the 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 the domain and that prove control of it.

Email domains are managed in the eCourtDate Console under the Domains section. Email delivery is handled through Amazon SES, so the DNS records added point to Amazon SES infrastructure.

Why agencies use email domains​

  • Credibility and branding: messages come from the 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 the agency.
  • Unlimited addresses: create as many email addresses as needed under a verified domain.
  • Inbound email: receive email directly to the custom domain when MX records are configured.

Choosing the domain​

Use a subdomain of the agency's domain for the eCourtDate email domain, such as notifications.agency.gov or email.agency.gov. A subdomain:

  • Protects the 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 the staff send from the root domain.
  • Supports inbound email safely. Inbound email requires MX records. Adding MX records to the root domain would redirect all of the 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 the eCourtDate SPF record is added cleanly, instead of editing the SPF record the existing mail already depends on.
  • Keeps the branding. A subdomain such as notifications.agency.gov still clearly identifies the agency to recipients.
caution

Do not use the 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 the existing mail, and eCourtDate sending volume can affect the reputation the staff email depends on. Always use a subdomain.

Next steps​