Checking a Secure Address

What the Step Does Planned

The Check a Secure Address's Certificate step (action core.check_secure_address) answers four things about a secure web address: when its certificate ends, who issued it, whether the chain is complete and trusted, and whether the name matches. It sends nothing but the handshake: no page is asked for, and no cookie or body is sent.

The step is built, and it stays turned off for every workspace until MountDev's shared engine can read a certificate. Until then it says "This check is turned off for now." and sends nothing. You can still add it to a workflow and try it with Test Run.

The Step's Parts

• Address: a web address like https://example.com, or just example.com. Only the name is used. It must be https, on the standard port, with no user name, and not on a private network. An address that is not allowed is refused with a plain sentence before anything is asked.
• Warn Days: how many days before the end to call the certificate expiring. 14 at first, up to 365.
• Stop When There Is a Problem: off at first. Turn it on to fail the step when the certificate is bad, with the reason in plain words.

What Later Steps Can Use

• ok: yes when the chain is trusted, the name matches, and the certificate has not ended.
• expiring: yes when it ends within the warning days.
• days_left: whole days left. Below 0 once it has ended.
• not_after: the end date.
• issuer: who issued it.
• chain_ok and name_matches: each yes or no.
• problem: one plain sentence, empty when there is none.

The run keeps the numbers and the yes or no values. It never keeps the issuer text.

What It Uses

Each try counts 1 step in Background work, like any step that does something. Test Run is free and asks nothing.

Who Can Use It

Owners, admins, and anyone whose role allows managing workflows. AI agents and API keys never turn a workflow on.