Domain Trust Check

What it runs

1. 1
   WHOIS Lookup

   Source: WHOIS protocol (ICANN-accredited registrar databases)

2. 2
   DNS Lookup

   Source: DNS protocol (authoritative nameservers)

3. 3
   SSL Certificate Check

   Source: TLS handshake (X.509 certificate from target server)

4. 4
   Domain Reputation

   Source: Threat intelligence feeds (multi-source scoring)

5. 5
   Security Header Check

   Source: HTTP response headers from target server (CSP, HSTS, X-Frame-Options)

The answer returns every step’s result, so your agent can show or check each one.

Inputs

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/domain-trust/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "domain": "example.com"
    },
    "max_price_cents": 40
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/domain-trust \
  -H 'Content-Type: application/json' \
  -d '{
    "domain": "example.com"
  }'

The bundle’s published example input.

Limitations

• Some registrars rate-limit WHOIS queries — bulk lookups may see slower response times

  From step: WHOIS Lookup

  What to do instead: Batch lookups with 1-2 second delays between requests, or use the RDAP protocol endpoint when available

• GDPR-redacted registrations (common for EU domains) show limited registrant information

  From step: WHOIS Lookup

  What to do instead: Use the abuse contact email from the WHOIS response to request registrant details through the registrar's disclosure process

• Results reflect current DNS propagation — recent changes may take up to 48 hours to appear

  From step: DNS Lookup

  What to do instead: Query the authoritative nameserver directly (returned in the NS records) to see changes before full propagation

• Checks the certificate presented on port 443 only — does not verify non-standard TLS configurations

  From step: SSL Certificate Check

  What to do instead: For services on non-standard ports, use ssl-certificate-chain with the specific hostname:port combination

• Reputation scores aggregate multiple blocklists — a single listing may not indicate actual malicious activity

  From step: Domain Reputation

  What to do instead: Check which specific blocklist flagged the domain in the response details and verify the listing reason before blocking

• Blocklist data refreshed daily — recently resolved issues may still show negative reputation for 24-48 hours

  From step: Domain Reputation

  What to do instead: If a domain was recently cleaned, re-check after 48 hours and use the trend direction to assess improvement

• Checks HTTP security headers only — does not assess server configuration, TLS settings, or application-level vulnerabilities

  From step: Security Header Check

  What to do instead: Combine with ssl-check for TLS assessment and use a full DAST scanner for application-level security testing