Outbound infrastructure
Will your outbound actually land?
Paste your sending domains. In seconds you get each domain scored against the published Gmail and Yahoo bulk sender requirements, with the exact DNS record to publish for every failure. Nothing is stored, and nothing here is a guess about where your mail landed.
Up to 25 domains per run. Free, no account.
What gets read
- SPF, including the ten lookup limit
- DKIM keys at sixteen selectors
- DMARC presence and policy strength
- MX and mail host reverse DNS
- MTA-STS, TLS reporting, domain age
List hygiene
Clean the list before you send
Paste a prospect list. Duplicates, dead domains, role inboxes, and disposable addresses are the rows that cost you reputation. They get flagged here, before a sequence ever touches them.
Up to 5,000 addresses. Processed in the request and never stored.
What gets flagged
- Duplicate
- Not a valid address
- Domain accepts no mail
- Role inbox
- Disposable domain
- Free provider
Mailbox existence is not checked. Proving a mailbox requires probing the receiving server, which damages the reputation this tool protects.
Why this broke
Why this broke in the first place
Gmail moved from filtering non-compliant senders to rejecting them, and Yahoo followed. At the same time, outbound tooling pushed teams onto portfolios of thirty to a hundred sending domains, each one needing its own SPF, DKIM, and DMARC. One domain drifting out of compliance quietly sends a month of sequences to spam. Every free checker on the market reads one domain at a time, and the score inside your sending platform comes from the vendor whose product caused the problem.
Honest limits
What this does not do
Inbox placement, spam-complaint rate, and warmup state cannot be read from outside your account, so this tool does not claim them. It reads what receivers read: your public DNS. Blacklist status is deliberately left out of the score, because public resolvers return a refusal code rather than a real verdict, and a tool that reports that as a listing is reporting noise.
Pricing
Free to run. Paid when you want it watched.
- 01Free
- Free
- Three domains per run, list hygiene included, no account.
- 02Operator
- $149 per month
- Twenty five domains, weekly re-checks, drift alerts when a record changes.
- 03Agency
- $499 per month
- One hundred and fifty domains across client workspaces, white-label reports.
- 04Managed
- $6,000 per month
- Orme runs the sending infrastructure and the fix cycle with your team.
Checkout opens Monday. Until then the free run is genuinely free, and the paid tiers start with a call.
Questions people ask before they paste a domain
- What does Deliverability Command actually check?
- Twelve things receivers read before they decide what to do with your mail: SPF presence, SPF validity including the ten lookup limit, whether SPF still allows the whole internet, DKIM signing keys across sixteen common selectors, DMARC presence, DMARC policy strength, DMARC reporting, MX records, mail host reverse DNS, MTA-STS, TLS reporting, and domain age.
- Is a high score a guarantee my email reaches the inbox?
- No, and any tool that says otherwise is selling you something. This measures compliance with the published sender requirements, which is the part you control from DNS. Content, list quality, sending volume, and recipient engagement decide the rest.
- Do you store my domains or my prospect list?
- No. Both run inside the request and nothing is written to a database. The list checker resolves one MX lookup per unique domain and discards the addresses when the response is sent.
- Why does my brand new domain score badly?
- Because receivers treat new domains sending cold volume as the highest risk. The age check flags anything under thirty days. The fix is patience plus low daily volume, not another DNS record.
Building the inbound side too? Answer Factory turns your own data into pages AI engines can cite.
Bring the problem. We will scope the work on the call.
The first call is a real working conversation, not a pitch.