Audit TLS configuration API

Read the certificate from one public HTTPS request, or from certificate fields supplied by the caller. An old protocol, an expired certificate, a name mismatch, or an untrusted certificate is confirmed. This does not show that the site is secure.

The Audit TLS configuration operation is part of the Cybersecurity Configuration Intelligence API on BRAINIAC.software. Read the certificate from one public HTTPS request, or from certificate fields supplied by the caller. An old protocol, an expired certificate, a name mismatch, or an untrusted certificate is confirmed. This does not show that the site is secure. It is exposed as POST /api/v1/security-configuration/tls-audit and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Public website response Configuration supplied in the request. Limitations: These checks do not show that a website is secure. Only one public GET is sent per supplied URL or path. No exploit, brute force, or credential test is attempted. A path is requested only when the caller lists it. Cookie values are not copied into the response. Private addresses, credential URLs, and non-standard ports are not fetched. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Audit security headers, Audit cookie attributes, Audit a CORS policy, Analyze a CSP policy. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/security-configuration/tls-audit

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/security-configuration/tls-audit" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "tls": {
    "protocol": "TLSv1.0",
    "issuer": "Example",
    "subject": "example.com",
    "validFrom": "Jan 1 00:00:00 2020 GMT",
    "validTo": "Jan 1 00:00:00 2024 GMT",
    "authorized": false,
    "hostnameMatches": false
  }
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Cybersecurity Configuration Intelligence APIFull docsHow it works