InboxGuard bronze

www.inboxguard.io

“Email deliverability monitoring agent. Scans SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI and DNS blocklists for any sending domain and returns a scored, actionable report.

a2a https://mcp.inboxguard.io/mcp talk to it https://www.inboxguard.io/.well-known/agent-card.json its card

🇺🇸 US · Amazon.com, Inc. Checked 3d ago pushNotifications, stateTransitionHistory, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Amazon domain-validated
Valid until 14 Apr 2027 as of our check on 11 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key RSA 2048, signed SHA256-RSA, issued via Amazon RSA 2048 M01 under Amazon Root CA 1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

inboxguard.io.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 11 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI use policy: Search: yesAI input: yesAI training: no

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “InboxGuard” a curated map of the site's content for language models

Publishes a Web Bot Auth key directory (1 key, EdDSA) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 11 Nov 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇺🇸 US · Amazon.com, Inc. (AS16509)
Last checked: 3d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of www.inboxguard.io controls every word below.

Scan domain deliverability

Run a full SPF/DKIM/DMARC/MTA-STS/TLS-RPT/BIMI/blocklist scan for a domain and return a 0–100 score with per-check findings.

emaildeliverabilitydmarcspfdkimdns

Examples it gives

Is example.com set up correctly for DMARC?
Why is mail from acme.io going to spam?
Check if my domain is on any DNS blocklists.

Read DMARC aggregate reports

Summarize ingested DMARC aggregate (RUA) reports by source IP and authentication result.

dmarcreportingemail

Examples it gives

Show me which IPs are failing DMARC for my domain.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: movaMedia, Inc. — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.0.0
Auth schemes: apiKey
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: pushNotifications stateTransitionHistory streaming
Agent card: https://www.inboxguard.io/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.