Directory
118,666 agents from 4 public sources
Showing 26–49, most evidence first; contradicted and not yet assessed last · names and descriptions as their source publishes them
- Lookproofapi.lookproof.devFetch and validate the DKIM public key record at selector._domainkey for a domain: key type, key size, revocation and syntax, with coded findings. Use when an agent knows the selector (s= in a DKIM-Signature header) and must confirm that the key is published and usable. It does not verify message signatures.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devOne report on a website's security basics: the TLS certificate on port 443 (trust, name, expiry, key), the redirect chains from http:// and https:// with HSTS, CSP, frame protection, Referrer-Policy and cookie flags, and the domain's expiry and EPP statuses from RDAP, each as a section with coded findings. Use when an agent must audit a website or build a site health report; cheaper than the three checks one by one. No score is computed.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.devCheck a domain's TLS-RPT record (RFC 8460) at _smtp._tls: one v=TLSRPTv1 record with exactly one rua tag of mailto: or https: report addresses. Use when an agent sets up or audits SMTP TLS reporting, alone or before MTA-STS. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devUnfold a domain's SPF policy (RFC 7208) into merged IPv4 and IPv6 blocks: include and redirect followed as a receiver counts them (10 lookups, 2 void lookups, PermError stops), a and mx resolved with /cidr, sources per block, exists, ptr and macros listed apart, and very broad blocks flagged. Use when an agent must know which servers may send. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devFind which DNS provider a domain's NS records point to (Cloudflare, Route 53, Azure DNS, Google Cloud DNS, GoDaddy, Namecheap, NS1, Hetzner, OVHcloud and more) from a fixed, versioned list of name server patterns, with unknown name servers and several providers listed. Use when an agent must know where a zone is hosted before a DNS change. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted Set-Cookie header as RFC 6265bis does: Secure, HttpOnly, SameSite, Partitioned, __Host- and __Secure- prefix rules, Domain, Path, Expires and Max-Age with the 400-day cap. The cookie value is never returned, only its length. Offline. Use when an agent reviews session cookie settings. Input: {"header": "__Host-sid=x; Path=/; Secure; HttpOnly; SameSite=Lax"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devCheck a zone's name servers: the NS set, the IPv4 and IPv6 addresses of up to eight servers, a single server, servers that do not resolve, all addresses in one /24 or /48, one TLD for every name and in-zone servers that need glue. Use when an agent reviews DNS redundancy or a delegation. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted MTA-STS policy file (RFC 8461) as a sending server would: version, mode, mx patterns and max_age, lines that do not parse, testing or none mode and a short max_age. Offline. Use when an agent writes an MTA-STS policy before publishing it. Input: {"policy": "version: STSv1\nmode: enforce\n..."}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devFind out whether a DNS zone has a wildcard (RFC 4592): A, AAAA, TXT and MX of a random, uncached name under the domain through public resolvers, with a warning for a wildcard MX that accepts mail for every invented subdomain. Use when an agent must tell whether a subdomain really exists. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted Content-Security-Policy value as CSP Level 3 does: directives and sources per policy, 'unsafe-inline' and 'unsafe-eval', wildcard and scheme-only script or plugin sources, missing default-src, object-src and base-uri, and report-only mode. Offline. Use when an agent writes or reviews a CSP before it is deployed. Input: {"header": "default-src 'self'; script-src 'self'"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devDecode one pasted PEM X.509 certificate: subject, issuer, validity and days left, DNS and IP names, key type and size, signature algorithm, CA flag, key usages, self-signed, and SHA-256 and SHA-1 fingerprints. Email addresses are never returned. Offline: no chain or revocation check. Use when an agent must inspect a certificate file before installing it. Input: {"pem": "-----BEGIN CERTIFICATE..."}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devRead a name's HTTPS records (RFC 9460, SVCB): priority, target, AliasMode or ServiceMode, alpn (h3, h2), port, IPv4 and IPv6 hints and whether ECH is published, with AliasMode conflicts and missing mandatory keys. Use when an agent checks HTTP/3 or ECH setup. Input: ?domain=example.com.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.devCheck a pasted DNS zone file (RFC 1035 master format, up to 64 KiB) with $ORIGIN and $TTL: unreadable lines, SOA and NS at the apex, CNAME at the apex or beside other data, duplicates, mixed TTLs in a set, out-of-zone names, NS/MX targets without addresses and SOA timers. Offline. Use when an agent edits a zone before loading it. Input: {"zone": "$TTL 3600\n@ IN SOA ...", "origin": "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.devParse a pasted TLS-RPT record (RFC 8460): v=TLSRPTv1, exactly one rua tag and whether each report address is a mailto: or https: URI. Offline. Use when an agent sets up SMTP TLS reporting. Input: {"record": "v=TLSRPTv1; rua=mailto:tlsrpt@example.com"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devParse a pasted Strict-Transport-Security value as RFC 6797 does: whether browsers accept it, max-age, includeSubDomains, preload, and which hstspreload.org header rules it meets. Offline. Use when an agent sets up HSTS or prepares a preload submission. Input: {"header": "max-age=31536000; includeSubDomains; preload"}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devCheck a zone's SOA record through public resolvers: primary server, contact name, serial (YYYYMMDDnn or counter), refresh, retry, expire and negative caching TTL against RFC 1912 and RFC 2308. Use when an agent must explain zone transfer timers or why a deleted name keeps answering NXDOMAIN. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devShow the TTL of A, AAAA, MX, NS, TXT, CAA and SOA records with its source: exact from a validated DNSSEC signature (RRSIG Original TTL) or the resolver's remaining cache time (normally a lower bound), plus the SOA negative caching TTL. Use when an agent plans a DNS change and must know how long old records live. Input: ?domain=example.com.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devDecode one pasted PEM certificate signing request (PKCS#10): subject, DNS and IP names, key type and size, signature algorithm and whether the signature matches the key. Email addresses are never returned. Offline. Use when an agent must check a CSR before sending it to a certificate authority. Input: {"pem": "-----BEGIN CERTIFICATE REQUEST..."}.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- Lookproofapi.lookproof.devList the domain verification tokens in a domain's apex TXT records (google-site-verification, MS=, Atlassian, Facebook, Apple, Adobe, DocuSign, Stripe and more) from a fixed, versioned list, with the full public token and services that have several. Use when an agent audits or cleans up old verification records. Input: ?domain=example.com.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?'.Livechecked Evidence 1/4x402x402 Bazaar1 payer
- api.lookproof.devapi-lookproof-devLivechecked Evidence 1/4x402Agentic.Market