Dmarc Parse
by Sift Web Tools in Documents & files
DMARC aggregate report parser with real alignment checks (JSON or CSV). Reads a DMARC aggregate report URL (XML, .gz, .zip or the whole email). Computes SPF and DKIM alignment itself using the Public Suffix List, reports the receiver's verdict separately, flags disagreements, explains each failure in plain words, and rolls up pass rate, dispositions, failure modes and worst sources.
https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse- Price
- $0.02
- per call in USDC
- Uptime
- 96.2%
- last 30 days
- Response time
- 149 ms
- 223 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse
Each call costs $0.02 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fdmarc-example.xmlParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
format | string | No | json or csv (default json) |
url | string | Yes | Report URL (xml, gz, zip or eml) |
Example response
The provider's example. We can't check it without paying.
{
"rollup": {
"failure_modes": {
"SPF passed but for a domain not aligned with the From domain (third-party sender); no passing DKIM signature": 3
},
"messages": 12,
"pass_rate": 0.75
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fdmarc-example.xml'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fdmarc-example.xml' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fv1%2Fdmarc%2Fparse
const res = await pay("https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fdmarc-example.xml");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://sift.srv1996466.hstgr.cloud/v1/dmarc/parse?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Fdmarc-example.xml")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 172 ms | $0.02 |
| 7 h ago | Passed | 402 | 144 ms | $0.02 |
| 12 h ago | Passed | 402 | 49 ms | $0.02 |
| 16 h ago | Passed | 402 | 144 ms | $0.02 |
| 21 h ago | Passed | 402 | 159 ms | $0.02 |
Show 10 older checks
| 25 h ago | Passed | 402 | 144 ms | $0.02 |
| 29 h ago | Passed | 402 | 194 ms | $0.02 |
| 33 h ago | Passed | 402 | 223 ms | $0.02 |
| 37 h ago | Passed | 402 | 47 ms | $0.02 |
| 41 h ago | Passed | 402 | 45 ms | $0.02 |
| 45 h ago | Passed | 402 | 140 ms | $0.02 |
| 2 days ago | Passed | 402 | 140 ms | $0.02 |
| 2 days ago | Expected HTTP 402, got 404 | 404 | 148 ms | - |
| 2 days ago | Passed | 402 | 192 ms | $0.02 |
| 3 days ago | Passed | 402 | 142 ms | $0.02 |