# is-port-135-open

> is-port-135-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-13).

Checks whether TCP port 135 (MS-RPC) 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/135?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/is-port-135-open-a563bad5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d2HlKcYpyy2OOESF2arV8

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-135-open-a563bad5
```

Example prompt: Can you check whether TCP port 135 (MS-RPC) is open or closed on the host 203.0.113.45? I want to know if it's exposed to the internet without running a local scanner.

## When to prefer this

Use this endpoint when you need a quick, agentless check on whether port 135 (MS-RPC) is publicly reachable on a host, without deploying a local port scanner. It is ideal for security audits, firewall validation, and incident triage where you want an external perspective from Cloudflare's edge network. Prefer this over generic network scanners when you specifically need MS-RPC exposure data at low cost ($0.01/check) and don't want to manage scanner infrastructure.

## Known failure modes

- Cloudflare-fronted hosts return inconclusive status because Cloudflare's edge answers the TCP connection before the origin
- Filtered ports may time out, leading to slower responses
- Invalid or unresolvable hostnames will fail to produce a result
- Firewalls that silently drop packets may be misreported as filtered vs closed

## How this service works

Is TCP port 135 (MS-RPC) 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 MS-RPC without running a scanner. $0.01 per check.

## Output

Returns whether TCP port 135 is open, closed, or filtered on the target host, along with the connection time in milliseconds. If the host is behind Cloudflare's edge (which answers connections on behalf of the origin), the result is flagged as inconclusive.

## 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-135-open-a563bad5/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)