Expired Certificate Warning Error Block for React

No. The chain, its dates and the error code are typed in the file, and "Continue to the site, unsafe" only says that nothing connects, or asks you to tick the box first. To wire it, check the real certificate on your side, render the real chain here, and send the visitor on only if your policy allows it (many products block the page with no way on at all).

Because most people should leave, and a warning that makes continuing as easy as leaving is not a warning. Back to safety is the only colored control and first in the order; the unsafe route needs three deliberate steps: open Advanced, tick the box, press the button. The button stays focusable while the box is clear and says what is missing, instead of being disabled and silent.

From two typed dates: the certificate's last valid day (2025-12-31) and the page's typed today (AS_OF, 2026-10-14), subtracted in UTC. Nothing reads the clock, so the page says the same on the server and in every time zone, and it never goes stale. Change either date and the count and the words follow.

Because Advanced makes it taller. Most pages in this set are centred in the screen, but a centred page would move its headline whenever the panel opened or closed; starting at the top keeps everything above the disclosure where it was. The disclosure animates its height, and not at all with reduced motion.

Tab reaches Back to safety and Advanced, whose expanded state is announced; inside the panel come the Copy button, the checkbox and the unsafe button. The chain is a nested list, so a screen reader reads each link's name, role and last valid day, and the expired one says Expired. Copying says Copied through the button's own polite status; pressing the unsafe button speaks its result.

It is a code that browsers show for an expired certificate. Show the one your own client or server produces, copied exactly, so people can search for it or paste it into a ticket.