# simpliloquy.com is a sending domain.

It carries transactional mail for BeargrassAI clients and hosts nothing else.
If an email from here surprised you, see "Report a message" below.

## What leaves here

| | |
|---|---|
| booking confirmations | yes |
| payment receipts | yes |
| password resets | yes |
| newsletters | never |
| cold outreach | never |
| marketing campaigns | never |
| list rentals | never |

There is no mailing list on this domain. Nothing is sent that a person did not trigger by booking, paying, or asking.

## Why transactional mail needs its own domain

Every mail provider keeps a reputation score against the domain a message is sent from. Bounces, spam complaints and sudden volume all push that score down, and once it is down, mail from that domain starts landing in junk folders.

Transactional mail is exactly the traffic that damages a score. It goes out in bursts, it goes to addresses a customer typed themselves and may have typed wrong, and every hard bounce counts against the sender.

So it leaves through a domain that exists for the purpose. A client's primary domain then keeps a clean reputation for the mail they write by hand: quotes, invoices, the note to their accountant. Those are the messages that must not land in junk, and they are the ones that suffer when automated mail shares the same reputation.

## Subdomain, or a separate domain?

A subdomain of your own domain is the common answer and a good one. Receiving providers evaluate a subdomain substantially on its own history, so `mail.yourbusiness.com` can carry the automated traffic while `yourbusiness.com` stays clean. It also keeps your name in the sender, which customers recognise.

A separate domain goes further. There is no shared registrable domain at all, so nothing that happens on the sending platform can reach your primary reputation, and you can change providers without touching your own DNS. The cost is that the sender is a name the recipient does not know, which is the entire reason this page exists.

## How to check a message is genuine

Three DNS records decide whether a receiving server believes a message, and anyone can look all three up.

- **SPF** — which servers may send as this domain
- **DKIM** — a cryptographic signature on every message
- **DMARC** — what to do when the first two disagree

```
$ dig +short TXT simpliloquy.com
  "v=spf1 include:_spf.resend.com ~all"

$ dig +short TXT resend._domainkey.simpliloquy.com
  "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEB..."

$ dig +short TXT _dmarc.simpliloquy.com
  "v=DMARC1; p=quarantine; rua=mailto:dmarc@simpliloquy.com"
```

Alignment is the part that matters. The domain that signed the message and the address you can see in the From line have to agree, and DMARC is what tells a receiving server to act when they do not. A message claiming to be from this domain that fails these checks is not ours.

## Report a message

If you received mail from this domain and did not expect it, use the form at <https://simpliloquy.com/#report> with full headers. You will get an answer within one business day about whether it left our systems.

A sending domain has no inbound mail, so there is no address here to write to directly. The report leaves through this domain, which is the only thing it does.

### What real mail from us looks like

- Names your booking or payment: always
- Asks for a password: never
- Asks you to pay through a new link: never
- Attaches an invoice you must open: never

## Operator

[BeargrassAI](https://beargrass.ai), a one-person software studio in Columbia Falls, Montana.

beargrassai.com never sends marketing emails from this domain. Period.