Check URL Status

Overview

You send a public http(s) URL and we probe it with a bounded HEAD or GET through our SSRF-safe HTTP client, then hand back the status code, the content type, and how many body bytes came back. Before every hop we resolve the host and refuse loopback, link-local, any-local, RFC 1918 private, and cloud-metadata addresses, so a redirect chain cannot walk into your internal network. Transport problems come back as ok:false with a short error code instead of an exception. We never return the page body, so pass HTML you already have to the web.extract_* skills when you need to parse a page.

You want to verify a link without opening a path into your own network, and without paying for a browser to render the page.

When to use it

Scope

Non-goals

• Does not render pages or run JavaScript
• Does not reach loopback, link-local, private, or cloud-metadata addresses
• Does not return the page body for parsing
• Does not return response-body content

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"web.check_url_status","input":{"url":"https://example.com/"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("web.check_url_status", {"url":"https://example.com/"});

Errors

Other limits

Limitations

• Does not render pages or run JavaScript
• Does not reach loopback, link-local, private, or cloud-metadata addresses
• Does not return the page body for parsing
• Does not return response-body content
• Downloading HTML for extraction — pass HTML you hold to the web.extract_* skills
• Browser-accurate rendering, or checks that depend on JavaScript
• Reaching an internal host, which we always refuse

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "web.check_url_status",
  "input": {
    "url": "https://example.com/"
  }
}

Examples

{
  "url": "https://example.com/"
}

{
  "metadata": {
    "ssrfProtected": true,
    "followedRedirects": true
  },
  "bodyTruncated": false,
  "finalUrl": "https://example.com/",
  "status": 200,
  "contentLength": 1256,
  "contentType": "text/html; charset=UTF-8",
  "ok": true
}

{
  "url": "http://127.0.0.1/admin"
}

{
  "ok": false,
  "metadata": {
    "ssrfProtected": true,
    "followedRedirects": true
  },
  "error": "BLOCKED",
  "status": 0
}

Recommended use cases

• Check that a link responds before you store or publish it
• Spot-check uptime, or learn what content type a URL serves
• Confirm a redirect chain resolves to a reachable public target

Avoid for

• Downloading HTML for extraction — pass HTML you hold to the web.extract_* skills
• Browser-accurate rendering, or checks that depend on JavaScript
• Reaching an internal host, which we always refuse

Related skills

Composable with

Safety & privacy

• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags