SSL Certificate Check.
Inspect publicly logged TLS certificate information for a domain and return structured certificate intelligence to automated systems.
Certificate data
for automation.
Check the latest publicly logged certificate information without requiring an interactive browser.
GET /v1/tools/ssl
Provide a domain name using the domain query parameter.
TLS certificate attributes
Responses can include certificate status, validity periods and publicly logged certificate details.
Security workflows
Useful for domain monitoring, security research, infrastructure analysis and automated enrichment.
Machine-payable TLS intelligence.
Discover the endpoint and payment requirements through DataBG's API specification.
View OpenAPI →API reference for AI agents and developers.
DataBG tools are designed as small, machine-readable building blocks for automated workflows. Each request uses a predictable HTTP endpoint and can be accessed with an API key or, where enabled, through x402 machine payments.
Inspect publicly logged TLS certificate information
The DataBG SSL Certificate Check API gives automated systems a way to inspect publicly logged TLS certificate information for a domain. It is intended for domain intelligence, security research, infrastructure analysis and monitoring workflows.
Request
GET https://api.databg.tech/v1/tools/ssl?domain=google.comRequired parameter: domain — the domain whose publicly logged certificate information should be inspected.
Certificate intelligence
Depending on the available certificate record, the service can expose certificate status, validity information, issuer, Subject Alternative Names and expiration-related details. The data is sourced from publicly logged certificate information and should be treated as an intelligence signal rather than a substitute for a complete live TLS handshake.
Use cases
Useful applications include automated domain inventories, certificate monitoring, security research, infrastructure mapping, technical due diligence and AI agents that need TLS context before making a decision.
Access and pricing
The current listed price is $0.005 per request in USDC on Base Mainnet. Paid clients may receive HTTP 402 Payment Required and machine-readable payment requirements before the data response.
Important implementation note
Certificate transparency data describes certificates that have been publicly logged. Agents should distinguish certificate-log intelligence from the live certificate currently served by a host when a workflow requires real-time handshake validation.
How x402 access works
DataBG paid tools can use the HTTP 402 Payment Required flow. A compatible client requests a resource, receives machine-readable payment requirements, settles the requested amount in USDC on Base Mainnet, and retries the request with payment authorization. This model is designed for autonomous software that can discover and pay for individual API calls.
Agent → DataBG endpoint
↓
402 Payment Required
↓
USDC payment on Base Mainnet
↓
Retry with payment authorization
↓
Structured JSONFor implementation details, use the live API specification and machine-readable discovery resources linked below.
Open API specification → Machine-readable discovery →