Skip to main content

CAP.L0.PINNED_HOST_UNVERIFIED — the pin could not be checked against the server

  • Category: safety
  • Level: 0
  • Stability: stable
  • Suites: audit

A host was pinned, and the server did not report an address that could be compared against it. The pin is not contradicted — it is unconfirmed, which is a third thing.

Why it is reported rather than assumed​

The alternative is a report that silently treats the pin as verified. That report is identical to one where the check actually passed, and the difference only surfaces when somebody acts on a finding about the wrong instance.

When this happens​

A server behind a pooler that does not pass the backend address through; a connection over a Unix socket, where there is no address to compare; or a managed database that withholds the setting the comparison reads.

What to do​

If the topology genuinely cannot answer, this notice is the honest end state and --strict is how you decide whether it should fail a pipeline. If it should be answerable, check whether the reading role may read the server's own settings — see settings unreadable.