Domain reputation
On a shared IP, the domain is the asset that is genuinely yours. It is what providers increasingly weight most heavily, it follows you if you ever change provider, and it is the one part of this you control end to end.
What builds it
Authentication, aligned. SPF, DKIM and DMARC alignment are evaluated against your domain. An unauthenticated or misaligned message damages the domain specifically, not the IP. See Email authentication.
Consistent, wanted volume. Reputation is a rolling judgement about what mail from this domain has looked like lately. Steady beats spiky, and engaged beats large.
A low bounce and complaint rate from that domain. Bounce data is per workspace here, but providers attribute it to the sending domain.
Time. A new domain has no history. That is what warm-up is for, and 97 of 181 verified domains on the platform are currently inside that 30-day ramp, so a new domain being capped is the normal case rather than a fault.
Use subdomains to separate risk
The single most useful structural decision, and it has to be made before you start sending because it is painful to change later.
| Subdomain | For |
|---|---|
yourcompany.com |
Your people’s own mail. Keep automated sending off it. |
mail.yourcompany.com |
Transactional: receipts, resets, alerts. |
news.yourcompany.com |
Bulk and marketing. |
The point is containment. A marketing campaign that attracts complaints
damages news., and your password resets keep arriving from mail., which
is the outcome you want when something goes wrong. Keeping both off your root
domain protects your employees’ own correspondence from either.
Each subdomain is a separate domain here: verified separately, warmed separately, and judged separately by providers.
Seeing it
Providers do not publish a domain reputation score through any API, so this is mostly indirect.
Google Postmaster Tools is the closest thing to a direct read for Gmail, covering domain reputation, spam rate, authentication results and delivery errors. Verify your sending domain there; it is free and it is the single most useful external signal available.
DMARC aggregate reports tell you who is sending as your domain and whether it authenticates. The platform ingests them for domains hosted here and exposes them over the API:
DOMAIN=news.yourcompany.com
curl -s https://api.lockally.com/v1/domains/$DOMAIN/dmarc \
-H "Authorization: Bearer $LOCKALLY_API_KEY"
Scope domains:read. There is no console view for this, so the endpoint is
the only way to read them.
Your own outcome counts, from GET /v1/messages/stats, filtered to the
sending domain. See Monitoring.
Protecting it
Publish DMARC, and move toward enforcement. A p=none policy gives you
reports; quarantine and then reject stop other people sending as you. A
domain that anybody can spoof cannot hold a good reputation.
Do not send bulk from your root domain. Covered above, and the most common avoidable mistake.
Do not abandon a warmed domain. Reputation decays. A domain that sends nothing for months is close to cold again.
Do not rotate domains to escape a problem. It reads exactly like what spammers do, and it discards the only asset you were building. Fix the list.