Consistency Findings

A hostname often resolves to several addresses: load-balanced servers, or the nodes of a CDN. The check connects to each one, and these findings say when they don't all serve the same certificate.

To confirm any fix on this page, click Check Now on the monitor's page. On the Certificate Report, click the Addresses count to see each address and the certificate it served.

CERT_CON01: Addresses serve different certificates

Key: CERT_CON01 · Label: Certs Did Not Match · Severity: Error · Can be dismissed: No

What it means: the addresses behind this hostname served different certificates on the same check, so visitors get one or the other.

Why it matters: the certificates usually differ for a reason: one node missed a renewal or a replacement, and it will fail on its own when its certificate expires.

How to fix it: install the same certificate on every server, load balancer and CDN node behind this hostname.

CERT_CON02: Certificate keeps changing between checks

Key: CERT_CON02 · Label: Certificate Flapping · Severity: Warning · Can be dismissed: No

What it means: the certificate served for this hostname has changed back and forth over the last few checks (three or more changes across the last five checks). This finding comes from the monitor's state rather than a single check: on the Findings page it shows how many times the certificate changed in the last week, and how long ago it last did. It's over once the last three checks have all read the same certificate.

Why it matters: it usually means different CDN or load-balancer nodes serve different certificates, which causes repeated change alerts and can hide a node whose certificate is about to expire.

How to fix it: install the same certificate on every server, load balancer and CDN node behind this hostname, and remove the old certificate from any node still serving it.