
InboxGuard
Actively maintained
≈ 3visits/mo
Little sign of use · estimate, read Oct 14, 2026
- For
- Email and operations teams fixing deliverability problems on the sending domains they manage
- Activity
- Actively maintainedsite updated yesterday
- Company
- Media, Inc.privacy policy
- Used for
- Scan a sending domain's SPF, DKIM and DMARC records
- Publish the exact DNS fix at your registrar
- Ingest DMARC aggregate reports and receive alerts
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsinboxguard.io ↗
- HeadquartersUSper their site
- Run byMedia, Inc.privacy policy ↗
These are InboxGuard's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverio.inboxguard/email-deliverabilityverified in the MCP registry
- Stateanswers, 28 toolschecked 2026-10-20
- Address to connectmcp.inboxguard.io/mcp
- OpenAPI spec30 pathsthe spec ↗
- API docsinboxguard.io/developersthe vendor's page ↗
- Status pagelinked from the homepageinboxguard.io/status.json ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use InboxGuard for?
Sign in to leave a noteWhat is InboxGuard?
Scans a sending domain's email DNS records such as SPF, DKIM and DMARC, then publishes the fixes at your registrar.
Who is InboxGuard for?
Email and operations teams fixing deliverability problems on the sending domains they manage
Do people use InboxGuard?
Little sign of use: ≈ 3 visits/mo · estimate, 2026-10.
Is InboxGuard still maintained?
Actively maintained: site updated yesterday.
Who owns InboxGuard?
InboxGuard is run by Media, Inc., per its privacy policy (2026-10-20).
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.