75trust / 100

Email Dmarc

by dmarc-record-check in Email & messaging

x402 APIPassing, checked 8 h ago

DMARC record check for a domain: fetches _dmarc TXT, parses policy (none/quarantine/reject), subdomain policy, percentage, aggregate and forensic report addresses, alignment modes, and flags a non-enforcing or missing policy. Email spoofing protection audit. $0.01 per domain.

POST
https://intel.rallylive.ca/email/dmarc
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
125 ms
642 ms slowest 5%
Last check
Passed
8 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://intel.rallylive.ca/email/dmarc

Each call costs $0.01 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.

POST https://intel.rallylive.ca/email/dmarc
content-type: application/json

{
  "domain": "github.com"
}

Example response

The provider's example. We can't check it without paying.

{
  "domain": "github.com",
  "enforcing": true,
  "parsed": {
    "adkim": "r",
    "aspf": "r",
    "pct": 100,
    "policy": "quarantine",
    "rua": [
      "mailto:[email protected]"
    ],
    "ruf": [
      "mailto:[email protected]"
    ],
    "subdomain_policy": "reject"
  },
  "present": true,
  "record": "v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:[email protected]",
  "warnings": []
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://intel.rallylive.ca/email/dmarc' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"github.com"}'

# 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 - -X POST 'https://intel.rallylive.ca/email/dmarc' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"github.com"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fintel.rallylive.ca%2Femail%2Fdmarc&method=POST
const res = await pay("https://intel.rallylive.ca/email/dmarc", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "domain": "github.com"
  }),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://intel.rallylive.ca/email/dmarc",
        json={
            "domain": "github.com",
        },
    )
    print(res.status_code, res.text)

Security scan

1 finding

  • Payment address changed recently in payment
    Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3

Recent checks

WhenResultHTTPTimePrice
8 h agoPassed402390 ms$0.01
19 h agoPassed402479 ms$0.01
30 h agoPassed40249 ms$0.01
41 h agoPassed402378 ms$0.01
2 days agoPassed40290 ms$0.01
Show 10 older checks
3 days agoPassed40250 ms$0.01
3 days agoPassed402161 ms$0.01
3 days agoPassed40283 ms$0.01
4 days agoPassed40233 ms$0.01
4 days agoPassed402125 ms$0.01
5 days agoPassed402820 ms$0.01
5 days agoPassed402207 ms$0.01
5 days agoPassed40277 ms$0.01
6 days agoPassed402159 ms$0.01
6 days agoPassed40255 ms$0.01

History

11 Oct 2026Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3