# is-port-636-open

> is-port-636-open is a paid API for AI agents from ip.intel.rallylive.ca, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Checks whether TCP port 636 (LDAPS) is open, closed, or filtered on a given host by attempting a connection from Cloudflare's edge network.

## Facts

- Endpoint: GET https://ip.intel.rallylive.ca/ip/port/636?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/is-port-636-open-ef8322ac
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6KImtSfPTsuD3m7ke_b1Q

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 is-port-636-open-ef8322ac
```

Example prompt: Can you check if TCP port 636 (LDAPS) is open or reachable on ldap.example.com? I want to know if it's exposed to the internet without running a local scanner.

## When to prefer this

Choose this endpoint when you need a quick, passive check of LDAPS port 636 exposure on a remote host without deploying your own network scanner. It's ideal for security audits, pre-deployment checks, and incident triage where you want an external perspective from Cloudflare's edge. Prefer this over full port scanners when you only need a single-port LDAPS exposure result at low cost ($0.01 per call).

## Known failure modes

- Cloudflare-fronted hosts return inconclusive status because Cloudflare's edge intercepts the connection
- Hosts with strict firewalls may show 'filtered' rather than 'closed', making it hard to distinguish intent
- DNS resolution failures for the given hostname will prevent a check
- Transient network issues at Cloudflare's edge may cause false negatives
- Rate limiting or payment failures result in no check being performed

## How this service works

Is TCP port 636 (LDAPS) open on a host? Attempts a connection from Cloudflare's edge and reports open/closed/filtered with the connect time; Cloudflare-fronted hosts are reported as inconclusive because their edge answers for them. Exposure checks for LDAPS without running a scanner. $0.01 per check.

## Output

Returns whether TCP port 636 is open, closed, or filtered on the target host, along with the connection time in milliseconds. If the host is behind Cloudflare's edge, the result is marked inconclusive since Cloudflare answers on behalf of the origin.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/is-port-636-open-ef8322ac/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ip.intel.rallylive.ca](https://www.zero.xyz/host/ip.intel.rallylive.ca/llms.txt)