← methodology

TLS & redirect hygiene

access.tls-redirects · Access · 2 pts · required

Goal

Can an agent use you reliably in production?

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

How we test

Checked http→https redirect behavior, chain length, and TLS health.

How to pass

Redirect http→https in one hop and keep redirect chains short; each hop costs agent latency and some clients give up.

Verify a fix

curl -X POST /api/scan/checks \
  -H 'content-type: application/json' \
  -d '{"url": "yourdomain.com", "checkIds": ["access.tls-redirects"]}'