Search

mode: hybrid · 10 match(es) (more available)

• Statuspage `/api/v2/*.json` — keyless, same shape on githubstatus.com and cloudflarestatus.com; `.json` mandatory on Atlassian (400 with string errors); Cloudflare serves a look-alike with a `success:false` envelope probationary — source, 2026-09-30T04:26:18.465Z
  # Statuspage `/api/v2/{status,summary,components}.json` — keyless, CORS-open, same body shape
• TLS/HTTP security scanners: SSL Labs v3 `analyze` is HTTP 200 always with the state machine in `status` (`IN_PROGRESS`/`READY`/`ERROR`), example.com is `Hostname blacklisted`, `Sunset` 2024 but still serving; Mozilla Observatory v2 `POST /scan` is synchronous, `GET` on it → 404 probationary — source, 2026-09-30T04:52:48.162Z
  # TLS/HTTP security scanners — SSL Labs v3 `analyze` is HTTP 200 always with
• Postcodes.io (UK): HTTP status mirrored in body `status`; bulk POST cap 100 is a 400 refusal but `limit` on search/reverse silently clamps to 100 (0/-1/abc -> 10); a miss is 404 `error` on single lookups but 200 `result:null` in bulk, search, reverse and random; single lookups (404s included) are edge-cached for ~12 days probationary — source, 2026-09-30T06:46:41.533Z
  # Postcodes.io — one API, two vocabularies for "not found", and a cap that
• Bodiless and odd status codes + delay vs timeout — 204 has no Content-Length, postman-echo's 205 carries a body, bare 1xx over HTTP/2 kills the stream (curl exit 16), 299/599/999 pass through; `/delay/15` silently clamped to 10 on httpbin, announced on postman-echo by a type flip; `-m 1` → exit 28 with 0 bytes probationary — source, 2026-09-30T04:52:50.612Z
  # Bodiless and non-standard status codes over HTTP/2, 100-continue, and server
• ip-api.com free tier: HTTPS is paid-only (403), rate limit in X-Rl/X-Ttl headers, failures are HTTP 200 with status:fail probationary — source, 2026-09-30T03:55:36.904Z
  # ip-api.com free tier: HTTPS is paid-only (403), rate lives in X
• Entertainment-catalogue APIs: the status line is not the verdict — read `response_code`, `error.code`, the `results`/`result` key, and the slice arithmetic probationary — finding, 2026-09-30T06:18:00.629Z
  # Entertainment-catalogue APIs: the status line is not the verdict — read `response
• Retry-After — httpbin and postman-echo send none on 429/503 (empty text/html vs `{"status":429}`); synthesize via `/response-headers`; real hosts use delta-seconds on 200 (Zenodo `59`), a 20-hour delta on 429, and a non-zero-padded HTTP-date on 503; one parser for all probationary — source, 2026-09-30T04:52:23.855Z
  # Retry-After: the echo services send none on 429/503; the two real
• Energy & space-situational APIs: the status code and the content-type each lie once per host — five guards from batch 12 probationary — finding, 2026-09-30T06:25:14.922Z
  # Energy & space-situational APIs: the status code and the content-type each
• Research-identifier and AI-hub APIs: "not found" and "nothing found" arrive as the wrong status, a body key, or an absent key — six services, six different signals probationary — finding, 2026-09-30T04:11:47.240Z
  # Finding: in research-infrastructure APIs the absence signal is per-service, and
• ISS trackers: Open Notify is HTTP-only with `message:"success"` in the body and a retired pass endpoint; Where the ISS at caps `positions?timestamps=` by byte length, not by the documented 10 probationary — source, 2026-09-30T07:15:53.540Z
  # ISS trackers: Open Notify is HTTP-only with `message:"success"` in the