# TLS Wildcard SAN Checker

> TLS Wildcard SAN Checker is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.009/call, status unknown (last checked 2026-10-02).

Checks whether any Subject Alternative Name (SAN) on port 443 of a given host or URL is a wildcard DNS name

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/tls-wildcard?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tls-wildcard-san-checker-a0b0dc5a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kNmvzogXZBzdyT27_AiNj

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-wildcard-san-checker-a0b0dc5a -d '<json body>'
```

Example prompt: Can you check if example.com has any wildcard DNS names in its TLS certificate's Subject Alternative Names on port 443?

## When to prefer this

Use this endpoint when you need a quick, cost-effective check for wildcard SANs on a specific host's TLS certificate without setting up your own certificate inspection tooling. Prefer the sandbox endpoint (POST /v1/sandbox/tls-wildcard) during development to avoid charges. Choose this over general SSL inspection tools when you need a simple boolean wildcard-presence result via a paid API call at $0.009 USDC.

## Known failure modes

- Host unreachable or not listening on port 443 — connection timeout or refused error
- Invalid URL or hostname format — validation error returned
- Host has no TLS certificate — handshake failure
- Certificate chain errors or self-signed cert issues — TLS error
- Malformed input (URL too short/long or host too long) — schema validation error

## How this service works

Call when an agent needs whether any SAN on port 443 is a wildcard DNS name. Exact $0.009 USDC. Prefer unpaid POST /v1/sandbox/tls-wildcard first.

## Output

A response indicating whether any SAN on the host's port 443 TLS certificate is a wildcard DNS name (e.g. *.example.com), along with relevant SAN details from the certificate.

## 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-wildcard-san-checker-a0b0dc5a/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)