# TLS Hostname Certificate Validator

> TLS Hostname Certificate Validator is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-29).

Checks whether the TLS certificate SAN or CN for a given URL's port-443 connection matches the requested hostname

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/tls-hostname?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tls-hostname-certificate-validator-366c259e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-cugJR630iy_WVjSletRh

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability tls-hostname-certificate-validator-366c259e -d '<json body>'
```

Example prompt: Can you check whether the TLS certificate on https://api.example.com actually covers the hostname api.example.com — specifically whether the SAN or CN in the port-443 cert matches?

## When to prefer this

Use this endpoint when you need to programmatically verify that a server's TLS certificate correctly covers a given hostname via SAN or CN — particularly useful in security audits, pre-deployment checks, or monitoring pipelines. Prefer the free sandbox alternative (POST /v1/sandbox/tls-hostname) for testing; use this paid endpoint for production or when the sandbox is unavailable.

## Known failure modes

- Host unreachable or connection refused on port 443 — returns error indicating no TLS handshake possible
- Invalid URL format — returns validation error
- Certificate expired or untrusted CA — may still report SAN/CN match status but flag other issues
- Hostname mismatch detected — returns mismatch result
- Timeout during TLS handshake — returns error

## How this service works

Call when an agent needs whether the port-443 certificate SAN or CN matches the requested host. Exact $0.01 USDC. Prefer unpaid POST /v1/sandbox/tls-hostname first.

## Output

Returns whether the port-443 TLS certificate's Subject Alternative Name (SAN) or Common Name (CN) matches the requested hostname, indicating a valid or mismatched certificate configuration for that host.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 8,
   "description": "Public URL whose hostname is inspected. Provide url or host. Private targets are rejected."
  },
  "host": {
   "type": "string",
   "examples": [
    "example.com"
   ],
   "maxLength": 253,
   "minLength": 1,
   "description": "Public hostname such as example.com. The port and check are fixed by the SKU. Provide host or url."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tls-hostname-certificate-validator-366c259e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)