Documentation
Agent ToolsPOST

Agent Ssl Checker

Check the SSL/TLS certificate for a domain and port. Returns validity, expiry date, days remaining, issuer, issued-to, and Subject Alternative Names (SANs). `valid: false` means the certificate is expired or verification failed — do not trust email from this domain without further review. `error` is non-null only when a connection or verification failure occurred; parse it to determine the root cause. Results are cached for 1 hour. Example request: {"domain": "acme.com", "port": 443} Signals agents should act on: - valid == false → certificate invalid or expired - days_remaining < 14 → certificate expiring soon - error != null → connection or verification failure Use POST /v1/agent/tools/ssl-checker when you need this capability from your application or backend. It accepts a JSON request body. There are no query parameters for this operation.

Endpoint

Use this full URL directly in server-side integrations, scripts, or internal tooling.

POST request
https://api.dropfakes.com/api/v1/agent/tools/ssl-checker
Full endpoint URL
POST https://api.dropfakes.com/api/v1/agent/tools/ssl-checker

Authorization

This section explains how this endpoint should be called in the current API version.

No authorization required
This endpoint is documented as public in this version of the API reference. No bearer token is required.
Authorization
Authorization: dk_live_*****

Code examples

Start with curl, then use the language sample that matches your backend.

curl
curl -X POST "https://api.dropfakes.com/api/v1/agent/tools/ssl-checker" \
  -H "Content-Type: application/json" \
  -d '{
  "domain": "example.com",
  "port": 443
}'

Parameters

Query string parameters and request body fields are listed together for faster scanning.

NameLocationTypeRequiredDescriptionDefault
domainbodystringYesBody field for `domain`.-
portbodyintegerNoBody field for `port`.443

Success response

The primary success status for this operation is 200.

Status 200
Successful Response
200 application/json
{
  "domain": "example.com",
  "port": 1,
  "valid": "id_123",
  "expired": false,
  "days_remaining": 1,
  "issued_to": "string",
  "issuer": "string",
  "issued_at": "string",
  "expires_at": "string",
  "sans": [],
  "error": "string",
  "cached": false
}

Error response

Use this example to handle validation and request errors safely on the client or backend.

Status 422
Validation Error
422 application/json
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}