Why do a domain's emails go to spam? Checks SPF, DKIM, DMARC, MX and blocklists. Free, no login.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Check why emails from a domain might land in spam. Looks up the domain's public DNS: SPF, DKIM (common selectors), DMARC, MX, and whether its mail servers are on major blocklists. Returns a 0-100 score and plain-English issues, worst first. Read-only: it changes nothing and sends no email. DKIM keys on custom selectors can't be found from outside, so "DKIM not found" is only a hint. Free email providers (gmail.com etc.) aren't checked. Args: domain: The domain that sends the email, e.g. "joesplumbing.com". A website URL or an email address also works; the domain is taken from it.
Check why emails from a domain might land in spam. Looks up the domain's public DNS: SPF, DKIM (common selectors), DMARC, MX, and whether its mail servers are on major blocklists. Returns a 0-100 score and plain-English issues, worst first. Read-only: it changes nothing and sends no email. DKIM keys on custom selectors can't be found from outside, so "DKIM not found" is only a hint. Free email providers (gmail.com etc.) aren't checked. Args: domain: The domain that sends the email, e.g. "joesplumbing.com". A website URL or an email address also works; the domain is taken from it.
| Argument |
|---|
| Type |
|---|
| Description |
|---|
| domain* | string |
{
"type": "object",
"title": "check_email_deliverabilityArguments",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"title": "Domain"
}
}
}