RegoMail infrastructure, deliberately small.

regomail.com is a private operational mail domain. Clear routing, stable delivery, no telemetry. The page you are reading is the entire public surface — there is nothing behind a login because there is no login to be had.

postmaster@regomail.com technical posture

session · smtp+starttls peer · mail.regomail.com

[2026-05-20 09:14:22.137 UTC] connection accepted from 198.51.100.41:51772
[2026-05-20 09:14:22.138 UTC] › 220 mail.regomail.com Stalwart ESMTP at your service
[2026-05-20 09:14:22.142 UTC] ‹ EHLO sender.example
[2026-05-20 09:14:22.143 UTC] › 250-mail.regomail.com you had me at EHLO
                                › 250-PIPELINING
                                › 250-SIZE 52428800
                                › 250-STARTTLS
                                › 250-AUTH
                                › 250-SMTPUTF8
                                › 250 ENHANCEDSTATUSCODES
[2026-05-20 09:14:22.145 UTC] ‹ STARTTLS
[2026-05-20 09:14:22.146 UTC] › 220 2.0.0 Ready to start TLS
[2026-05-20 09:14:22.171 UTC] tls handshake · TLS1.3 · TLS_AES_256_GCM_SHA384 · X25519
[2026-05-20 09:14:22.172 UTC] ‹ EHLO sender.example
[2026-05-20 09:14:22.173 UTC] › 250 OK (post-TLS capabilities)
[2026-05-20 09:14:22.181 UTC] ‹ MAIL FROM:<alice@sender.example>
[2026-05-20 09:14:22.182 UTC] › 250 2.1.0 sender accepted
[2026-05-20 09:14:22.183 UTC] ‹ RCPT TO:<postmaster@regomail.com>
[2026-05-20 09:14:22.184 UTC] › 250 2.1.5 recipient ok
[2026-05-20 09:14:22.184 UTC] ‹ DATA
[2026-05-20 09:14:22.185 UTC] › 354 end data with <CR><LF>.<CR><LF>
[2026-05-20 09:14:22.219 UTC] … 4.1 KB message body, 12 headers, 1 attachment …
[2026-05-20 09:14:22.227 UTC] › 250 2.0.0 queued as 01HZ6T3M4Q9V0WK0X8RGY2A1S5 ✓
[2026-05-20 09:14:22.228 UTC] ‹ QUIT
[2026-05-20 09:14:22.229 UTC] › 221 2.0.0 mail.regomail.com closing connection
[2026-05-20 09:14:22.229 UTC] session closed · 0.092s · 5 cmds · 4.2 KB · spf=pass dkim=pass dmarc=pass
[ready]

Operating principles four / four

▌ IDENTITY

One operator. One domain.

No shared infrastructure, no reseller stack. Addresses here do not churn — mail sent in 2026 resolves the same way in 2031. Identifiers are permanent; this one is treated that way.

▌ SURFACE

No public intake.

No signups, no web client, no consumer dashboard. The domain routes mail and does nothing else. Every feature not present is an attack surface not defended.

▌ STANDARDS

RFC-conformant throughout.

SMTP, IMAP, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, HSTS. All externally observable behavior is open protocol, inspectable by any compliant implementation, replaceable without vendor lock-in.

▌ TELEMETRY

Zero collection.

No analytics on this page. No tracking pixels in outbound mail. No third-party scripts, no external font requests. The static surface you see is the complete surface.

Technical posture public DNS · verifiable

dig @1.1.1.1 regomail.com any authoritative · TTL 3600

;; auth + delivery
regomail.com.            3600  IN  MX    10 mail.regomail.com.
regomail.com.            3600  IN  TXT   "v=spf1 a mx ip4:148.230.94.176 -all"
_dmarc.regomail.com.     3600  IN  TXT   "v=DMARC1; p=none; rua=mailto:dmarc@regomail.com"
v1-ed25519-20260519._domainkey.3600 IN  TXT   "v=DKIM1; k=ed25519; h=sha256; p=s+3FgOH…"
v1-rsa-20260519._domainkey.    3600 IN  TXT   "v=DKIM1; k=rsa; h=sha256; p=MIIBIjAN…"

;; transport security
_mta-sts.regomail.com.   3600  IN  TXT   "v=STSv1; id=20260528T155005z"
mta-sts.regomail.com.    3600  IN  A     148.230.94.176
_smtp._tls.regomail.com. 3600  IN  TXT   "v=TLSRPTv1; rua=mailto:tlsrpt@regomail.com"

;; issuance + posture
regomail.com.            3600  IN  CAA   0 issue "letsencrypt.org"
regomail.com.            3600  IN  CAA   0 iodef "mailto:security@regomail.com"
regomail.com.            3600  IN  A     148.230.94.176
mail.regomail.com.       3600  IN  A     148.230.94.176

;; abuse + role addresses (RFC 2142)
;;   postmaster · abuse · security · dmarc · tls

Authentication-Results · sample, last delivery 2026-05-20T09:14:22Z

Authentication-Results: regomail.com;
    spf=pass      smtp.mailfrom=alice@sender.example
    dkim=pass     header.d=sender.example header.s=2026 header.a=ed25519-sha256
    dmarc=pass    policy.p=none policy.dis=none
    tls=pass      version=TLS1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256
    mta-sts=pass  mode=testing mx=mail.regomail.com
    smtputf8=pass ; recipient header in punycode-free utf-8

Path of a message sender → mail → mailbox

  sender.example                                   origin MTA
  │
  │  resolution + connection
  ├─ ① RESOLVE   DNS · MX 10  →  mail.regomail.com
  ├─ ② CONNECT   tcp/25  →  mail.regomail.com · 220 ready
  │
  │  transport security
  ├─ ③ STARTTLS  TLS 1.3 · TLS_AES_256_GCM_SHA384     ✓
  ├─ ④ MTA-STS   policy id · testing mode · mx pattern ok  ✓
  ├─ ⑤ HSTS      strict-transport-security · enforced      ✓
  │
  │  authenticated submission
  ├─ ⑥ SMTP      EHLO · MAIL FROM · RCPT TO · DATA
  ├─ ⑦ VERIFY    spf ✓   dkim ✓   dmarc ✓   mta-sts ✓
  ├─ ⑧ QUEUE     id 01HZ6T3M4Q9V0WK0X8RGY2A1S5 · 250 2.0.0
  │
  │  delivery + reporting
  ├─ ⑨ DELIVER   mailbox · maildir/new/ · fsync · ack
  │
  ▼
  mailbox · postmaster@regomail.com
       ├─ tls-rpt    → daily aggregate · tlsrpt@regomail.com
       └─ dmarc-rua  → daily aggregate · dmarc@regomail.com

①–②resolution + connection ③–⑤transport security ⑥–⑧authenticated submission ⑨delivery + reporting

Role addresses RFC 2142

postmaster: postmaster@regomail.com
abuse: abuse@regomail.com
security: security@regomail.com