Email Deliverability Audit

What it runs

1. 1
   Email Deliverability Check

   Source: DNS protocol (SPF, DKIM, DMARC record verification) + blacklist check

2. 2
   DNS Lookup

   Source: DNS protocol (authoritative nameservers)

3. 3
   SSL Certificate Check

   Source: TLS handshake (X.509 certificate from target server)

The answer returns every step’s result, so your agent can show or check each one.

Inputs

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/email-audit/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "domain": "google.com"
    },
    "max_price_cents": 25
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/email-audit \
  -H 'Content-Type: application/json' \
  -d '{
    "domain": "google.com"
  }'

The bundle’s published example input.

Limitations

• SMTP verification may be blocked by some mail servers — a 'deliverable' result is not guaranteed delivery

  From step: Email Deliverability Check

  What to do instead: Treat SMTP-verified results as 'likely deliverable' and implement bounce handling in your email pipeline for definitive status

• Results reflect current DNS propagation — recent changes may take up to 48 hours to appear

  From step: DNS Lookup

  What to do instead: Query the authoritative nameserver directly (returned in the NS records) to see changes before full propagation

• Checks the certificate presented on port 443 only — does not verify non-standard TLS configurations

  From step: SSL Certificate Check

  What to do instead: For services on non-standard ports, use ssl-certificate-chain with the specific hostname:port combination