Create a web service project
Add the HTTPS address as a Website, an MCP server or a Service with a URL. The panel suggests a name and an icon from the page.
Add the HTTPS address of your site, API or MCP endpoint to a web service project. Once a day the panel reads its TLS certificate and warns you 14, 7, 3 and 1 day before it expires. It works on every plan, Free included.
Each HTTPS address in the project shows when its certificate expires, who issued it and whether it covers the host name. At 14 days or less the address turns yellow; an expired certificate turns it red.
The example card is an illustration with sample values, not a live reading.
There is no public form here that tests any address. You add your own services in the panel, and the reading runs from there.
Add the HTTPS address as a Website, an MCP server or a Service with a URL. The panel suggests a name and an icon from the page.
The panel inbox is on by default. Turn on Web Push or connect Telegram in settings if you want them elsewhere.
A DNS TXT record or a file on the site starts the 30-day trial with scheduled checks and opens checks of ports on a host name.
The certificate reading is the same on every plan. Ownership and plan matter only for the checks around it.
| What is checked | Schedule | Domain ownership | Plan |
|---|---|---|---|
| Certificate of an HTTPS address in the project | Once a day; warnings at 14, 7, 3 and 1 day and on expiry | Not needed | Every plan, without a monitoring unit |
| Certificate of the server behind a proxy | Once a day, next to the edge certificate | Not needed | Every plan, when you give the origin address |
| TLS port of a service without a web page: 443, 465, 993 or 995 on a host name | Certificate once a day; a handshake check on your interval | Confirmed domain required | The scheduled check uses one monitoring unit: trial and paid plans |
| Availability of the address: status and response time | Every 5 minutes or more often, depending on the plan | Needed for the trial | Trial and paid plans, from the monitoring units of the project |
Limits per plan are listed on the pricing page. Ports outside the list above are not checked.
Each of these is a different job. Saying so here is cheaper than a surprise after you connect.
Short answers about cost, ownership and where the warnings go.
Read the monitoring documentationYes. The daily certificate reading and the expiry warnings work on every plan, Free included, and do not use a monitoring unit. Scheduled availability checks and checks of ports on a host name come with the trial and paid plans.
Not for the certificate of an HTTPS address you add. You confirm the domain with a DNS TXT record or a file on the site when you want the 30-day trial, scheduled checks, or checks of ports on a host name.
Once a day. A certificate changes rarely, so one reading a day is enough to warn you two weeks ahead. A reading older than 48 hours is shown as stale, not as healthy.
In the panel inbox. Web Push and Telegram are optional channels you turn on in settings. Each step of the 14, 7, 3 and 1 day scale sends one message, and the scale starts again when the certificate is renewed.
No. It watches the TLS certificate served at your address. Domain registration dates from WHOIS or RDAP are not read.
Create a web service project in the panel and add its address. The first certificate reading arrives within a day.