Cian Endpoint Audit

With a single tool there is no possibility of misselection; the purpose (audit one public HTTP endpoint) is stated explicitly and its scope is clear. No other tool overlaps or competes with it.

The lone name endpoint_audit is a clean snake_case noun_action pattern that matches the described operation. There is no second tool to deviate from the convention.

One tool is a thin surface, though it is deliberately scoped as a paid single-purpose audit micro-service. The bundled capabilities (status/redirects, TLS, headers, DNS) could plausibly have been split, but consolidation is defensible.

The audit covers the core dimensions of endpoint health: HTTP status and redirect chain, TLS, security headers, and underlying DNS records. Minor gaps exist—no batch/multi-endpoint auditing, no history or diffing against previous runs—but nothing blocks a single-endpoint audit workflow.