simpliloquy.com is a sending domain.
It carries transactional mail for BeargrassAI clients and hosts nothing else. If an email from here surprised you, start at report.
What leaves here
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, including you, right now.
$ 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:[email protected]"
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.
Lanes
Higher volume, a stricter compliance posture, or a client who wants their own name in the sender gets a dedicated subdomain and its own signing keys. One neighbour's bad month cannot reach the others.
simpliloquy.com
book.clientname.simpliloquy.com dedicated, own keys
pay.clientname.simpliloquy.com dedicated, own keys
mail.yourbusiness.com your domain, we configure it
Report a message
If you received mail from this domain and did not expect it, send it to us with full headers. You will get an answer within one business day about whether it left our systems.
The report leaves through this domain, which is the only thing it does. No inbox lives here either, so there is nothing to email directly.
What real mail from us looks like
FAQ
Why did I get an email from simpliloquy.com?
Because you booked or paid with a business that uses BeargrassAI. The confirmation left through this domain rather than theirs, so their own mail keeps a clean sending reputation. The message should name the business and what you booked or paid for.
What is a sending domain?
A domain used only to send mail on behalf of an application, kept apart from the domain a company uses for everyday correspondence, so that automated mail and human mail do not share one reputation.
Should transactional email come from my primary domain?
Usually not. Send it from a subdomain, or from a dedicated sending domain. Your primary domain then keeps its reputation for the mail you write yourself, which is the mail that hurts most when it lands in junk.
Does a subdomain have its own reputation?
Largely, yes. Receiving providers evaluate a subdomain substantially on its own history, which makes a subdomain a real isolation strategy rather than a cosmetic one. It is not absolute: severe abuse at the registrable domain can still affect everything beneath it.
Do I need SPF, DKIM and DMARC?
All three. SPF says which servers may send. DKIM signs each message. DMARC tells a receiving server what to do when the visible sender does not align with either, and it is the one that turns the first two from advice into policy. Major mailbox providers now require them from bulk senders.
Is simpliloquy.com a company?
No. It is a sending domain operated by BeargrassAI, a one-person software studio in Columbia Falls, Montana. No website lives here, which is why this page looks the way it does.