Directory
118,577 agents from 4 public sources
Showing 1–13, most evidence first; contradicted and not yet assessed last · names and descriptions as their source publishes them
- Lookproof DNS, mail and TLS security checksio.github.lookproof/lookproof-mcp · api.lookproof.devSPF, DKIM, DMARC, MTA-STS, DNSSEC, TLS and DNS checks. Free API key or pay-per-call (x402).Livechecked Evidence 2/4MCPWebsiteMCP Registry
- Lookproofapi.lookproof.devOne report on a domain's mail and DNS security: MX, SPF, DMARC, common DKIM selectors, MTA-STS with TLS-RPT, DNSSEC, reverse DNS of the mail servers, BIMI and CAA in one call, each as its own section with coded findings and evidence. Use when an agent must audit a domain's email security or build a domain health report; cheaper than calling the nine checks one by one. No score is computed.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devRun the mail configuration check (MX, SPF, DMARC) on up to 20 domains in one request, each with its spoofing protection category. Results keep the input order, and items that fail for a technical reason come with a token for a free retry. Use when an agent must audit many domains at once, for example a customer list or a portfolio of brands.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devOne report on a domain's mail setup: MX, SPF and DMARC, plus DKIM for the selectors you give, with coded findings, an overall status and a spoofing protection category (protected, partial, monitoring, unprotected or broken) with its reasons. Use when an agent needs a complete overview of a domain's email authentication in one call instead of four, or must judge how well the domain is protected against spoofing.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devLook up a domain's registration at its registry over RDAP (RFC 9083, servers from the IANA bootstrap file): registrar and IANA id, creation, change and expiry dates, EPP statuses such as hold or pending delete, nameservers and DNSSEC delegation. Contact data is never returned. Use when an agent must tell when a domain expires, whether it is locked against transfer or why it suddenly stopped resolving.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devLook up the DMARC record of a domain or its organisational domain and explain policy, subdomain policy, alignment and reporting addresses, with coded findings. Use when an agent must read which policy a domain asks receivers to apply to mail that fails DMARC, how strict it is, or why DMARC reports do not arrive.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted SPF record without DNS (RFC 7208): mechanisms with qualifiers and values, modifiers, syntax errors, the all policy and the number of terms that need DNS lookups, with coded findings such as +all, ptr and over ten lookups. Use when an agent must check an SPF record before publishing it. Input: {"record": "v=spf1 mx include:_spf.example.com ~all"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse and evaluate a domain's SPF record: the include and redirect tree, qualifiers and the RFC 7208 limit of ten DNS lookups, with coded findings. Use when an agent must tell whether SPF is valid, why mail from a service fails SPF, or whether one more include would exceed the lookup limit.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted DMARC record without DNS (RFC 9989): p, sp, np, psd, t, adkim, aspf, rua and ruf, historic and unknown tags, with the same coded findings as the DMARC check, such as p=none or a missing report address. Use when an agent must check a DMARC record before publishing it. Input: {"record": "v=DMARC1; p=none; rua=mailto:dmarc@example.com"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devCheck a domain's BIMI record (<selector>._bimi, default selector, with fallback to the organisational domain): v=BIMI1 syntax, HTTPS logo and certificate URLs, an SVG logo path and whether DMARC is enforced at quarantine or reject with pct=100. Use when an agent must tell why a brand logo does not show in mail clients. The logo and certificate are not downloaded.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devRead how strong a domain's DMARC policy (RFC 9989) is: protected (reject), partial (quarantine), monitoring (none), unprotected or broken, plus whether it has gaps (none, partial or full), the effective policy after test mode (t=y), the subdomain policy, pct and the SPF all qualifier. Use when an agent must explain whether a domain asks receivers to stop forged mail. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted BIMI record: v=BIMI1, the l= logo and a= certificate tags, repeated or missing tags, HTTPS URLs, the .svg logo path and a missing mark certificate. Offline: the logo and DMARC are not fetched. Use when an agent writes or reviews a BIMI record. Input: {"record": "v=BIMI1; l=https://example.com/logo.svg"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devUse when the user pastes email headers and asks why a message failed SPF, DKIM or DMARC, went to spam or arrived late. Returns the Received hops with delays, the verdicts, domains and alignment. Offline; addresses masked. Ex: 'Why did this email fail DMARC?'.Not checked yetlisted Evidence 0/4x402x402 Bazaar1 payer