MTA-STS policy parser API
Reads an MTA-STS policy file as the MTA-STS check reads a fetched one (RFC 8461 section 3.2): version, mode, mx patterns and max_age, lines that do not parse, and testing, none and short max_age. Nothing is fetched, so the _mta-sts record and MX coverage are not checked.
POST https://api.lookproof.dev/v1/mail/mta-sts-parse
Updated 2026-10-09
Examples use the Base (eip155:8453) network.
Input
A JSON body with content-type: application/json.
| Name | Type | Required | Limits | Description |
|---|---|---|---|---|
policy | string | Yes | 1–8192 characters | The MTA-STS policy file text, at most 8192 characters. Nothing is fetched. |
Example request
curl -i -X POST https://api.lookproof.dev/v1/mail/mta-sts-parse \
-H 'content-type: application/json' \
-d '{"policy": "version: STSv1\nmode: testing\nmx: mx1.example.com\nmx: *.mail.example.com\nmax_age: 604800\n"}'import asyncio
import os
from eth_account import Account
from x402 import x402Client
from x402.http.clients import x402HttpxClient
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact import register_exact_evm_client
async def main() -> None:
signer = EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"]))
client = register_exact_evm_client(x402Client(), signer, networks="eip155:8453")
async with x402HttpxClient(client) as http:
response = await http.post('https://api.lookproof.dev/v1/mail/mta-sts-parse', json={'policy': 'version: STSv1\nmode: testing\nmx: mx1.example.com\nmx: *.mail.example.com\nmax_age: 604800\n'})
response.raise_for_status()
print(response.json())
asyncio.run(main())
import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm";
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY);
const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, {
schemes: [{ network: "eip155:8453", client: new ExactEvmScheme(account) }],
});
const response = await fetchWithPayment("https://api.lookproof.dev/v1/mail/mta-sts-parse", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({"policy": "version: STSv1\nmode: testing\nmx: mx1.example.com\nmx: *.mail.example.com\nmax_age: 604800\n"}),
});
console.log(await response.json());
curl: unpaid request — returns 402 with the price (PAYMENT-REQUIRED). The Python and JavaScript clients pay it and send the request again. Only ordinary wallets (EOA) can pay; smart-contract wallets get a 402 without charge. See payments.
Example response
{
"checked_at": "2026-10-24T12:00:00Z",
"data": {
"mx_count": 2,
"notes": [
"Only the policy text is read. Whether the domain publishes an _mta-sts record, serves this file at https://mta-sts.<domain>/.well-known/mta-sts.txt and lists matching MX hosts needs the MTA-STS check."
],
"policy": {
"max_age": 604800,
"mode": "testing",
"mx": [
"mx1.example.com",
"*.mail.example.com"
],
"version": "STSv1"
},
"problems": [],
"valid": true
},
"endpoint": "mail.mta_sts_parse",
"findings": [
{
"code": "MTASTS_MODE_TESTING",
"evidence": {
"count": 1,
"items": [
{}
]
},
"explanation": "In testing mode senders report TLS failures through TLS-RPT but still deliver the mail, so the policy does not yet protect against downgrade attacks.",
"message": "The MTA-STS policy is in testing mode.",
"recommendation": "Move to mode enforce once TLS-RPT reports show that all MX hosts pass.",
"severity": "warning"
}
],
"meta": {
"cache_hit": false,
"duration_ms": 42,
"fresh_until": "2026-10-24T12:05:00Z",
"observed_at": "2026-10-24T12:00:00Z",
"resolver": null,
"source": "offline"
},
"request_id": "req_aaaaaaaaaaaaaaaaaaaaaaaaaa",
"schema_version": "1.0",
"status": "warning"
}
Response fields
| Field | Meaning |
|---|---|
request_id | Unique id of this request. Quote it when you contact support. |
endpoint | The endpoint id, for example mail.spf. |
schema_version | Version of the response format, currently 1.0. |
checked_at | When the check ran (ISO 8601, UTC). |
status | ok, info, warning or error from the worst finding, or unknown when the check was incomplete. unknown is not an error in the domain. |
data | The check's own data. Its fields are listed below. |
findings | What was found: code, severity, message, explanation and evidence. |
meta | Duration, cache use, resolver and how long the result stays fresh. |
Fields in data
| Field | Type |
|---|---|
valid | boolean |
policy | MtaStsPolicy |
mx_count | integer |
problems | array of string |
notes | array of string |
Status codes
| Status | Code | Meaning | Do you pay? |
|---|---|---|---|
| 200 | — | The result is delivered, also when it has negative findings. | Yes: charged once per payment; redelivery of the same payment is free |
| 402 | — | Payment is required, or the attached payment was refused. The body states the price. | No |
| 400 | bad_request | The request is malformed. | No |
| 409 | payment_in_progress, payment_bound_to_other_request | This payment is already being processed, or it is bound to a different request. No new payment is taken. | No |
| 413 | payload_too_large | The body is larger than 64 KB. | No |
| 422 | invalid_input | The input failed validation on a request that carries a payment; nothing is charged. Without a payment, invalid input gets a 402 whose error field names the problem. | No |
| 429 | rate_limited | Too many requests from this IP address or payer. | No |
| 502 | check_failed | The check could not be completed. | No |
| 503 | busy, unavailable, payments_unavailable | The service is busy or temporarily unavailable. | No |
| 504 | deadline_exceeded | The check ran out of time. | No |
Errors use the common error body. See errors.
Findings this endpoint can return
MTA-STS (4)
- Error
MTASTS_INVALID_POLICYThe MTA-STS policy file is not valid. - Warning
MTASTS_LOW_MAX_AGEThe MTA-STS policy has a max_age below one day. - Info
MTASTS_MODE_NONEThe MTA-STS policy is in mode none. - Warning
MTASTS_MODE_TESTINGThe MTA-STS policy is in testing mode.