By default, SahlSign emails go from our verified domain with your display name swapped in ("Acme Legal" <noreply@smtp.sahlsign.com>). Most inbox previews only show the display name, so this gets you 90% of the way to a branded experience.
For the remaining 10% — recipients who expand the From line, mail clients that surface the envelope address, brand-conscious enterprises — you can verify your own domain and send from contracts@yourcompany.com directly.
The flow
- Open Settings → Email branding → Send from your own address
- Enter the address you want to use as sender (any local-part works; we verify the domain)
- Click Set up — we register your domain with our email provider (Resend) and return a list of DNS records
- Copy those records into your DNS provider (Cloudflare, Route 53, Namecheap, GoDaddy, etc.)
- Come back, click Check verification. The badge flips to "Verified" once DNS has propagated
Time to complete
- You: 5 minutes (entering records into your DNS provider)
- DNS propagation: minutes to 48 hours depending on your provider and previous TTL settings
- Active immediately on verify: as soon as the badge turns green, every email goes from your address
What records we ask for
Typically 3-4 records:
- One TXT for SPF (
v=spf1 include:amazonses.com ~allor similar) - One MX for return-path / bounce handling
- Two CNAME records for DKIM signing keys
We show you the exact values to paste — names, types, TTLs — with copy buttons next to each.
Removing the override
Click the trash icon next to "Check verification" to clear the custom address. Outbound mail immediately reverts to the SahlSign default. We also delete the domain from our Resend account so it doesn't accumulate cruft.
Why this matters
For B2B SaaS in regulated regions (finance, government, healthcare), having SahlSign's domain anywhere in the envelope is sometimes a procurement-blocking issue. Domain verification removes the entire attribution and makes the email indistinguishable from anything else your team sends.