Free check · no sign-up
See when a domain and its certificate expire. Or paste a package.json, requirements.txt or go.mod to see what is deprecated, vulnerable or end of life.
We ask the registry (RDAP or WHOIS) and read the certificate your server presents.
Registration and certificate expiry dates for any domain.
Deprecated, vulnerable and end-of-life packages in a manifest.
480+ runtimes, operating systems and databases, with calendar feeds.
Reviewed API shutdowns and breaking changes, with an RSS feed.
Then let us watch it
Certificates lapse. Domains expire. Vendors retire the API you call. Runtimes reach end of life. StackClock finds those dates and sorts them by what breaks first, so you fix them on your schedule instead of during an outage.
Next 30 days
PostgreSQL 14 reaches end of life
endoflife.date · live · 2026-11-12
TLS certificate for api.acme.io
from the certificate · R11
Later
Payments API v1 is retired
vendor change · matched on payments-sdk 2.x
Monitoring license renews
entered by hand · owner: Dana
Domain acme.io expires
from the registry (WHOIS)
Example workspace · end-of-life row is live
Add a domain and we look up its registration and certificate, and find the certificates on its subdomains in public Certificate Transparency logs. Import a manifest and we find what is deprecated, vulnerable or end of life. You only type the dates nobody publishes.
Expiries and vendor sunsets share one list, sorted by what breaks first, with an owner and a status on each.
Reminders at the lead times you choose, quiet hours, and a snooze that only affects you.
Domains and certificates
Add a domain once. We read its registration and its certificate every day and remind you 60, 30, 14, 7 and 1 day ahead, so a forgotten renewal never takes your site down. We also search public Certificate Transparency logs for certificates on its subdomains, so the ones you forgot about show up too. You pick which to monitor.
Next 30 days
TLS certificate for api.acme.io expires
read from the certificate · Let's Encrypt R11 · checked 3 h ago
in 12 days
17 Nov
Later
Domain acme.io expires
from the registry · NameCheap · auto-renew not confirmed
in 264 days
27 Jul 2027
Example workspace
Vendor deprecations
We read the official changelogs of OpenAI, Anthropic, Stripe, GitHub, AWS and more, and match every shutdown and breaking change to the packages in your stack. You plan the migration instead of debugging errors in production.
npm express
vendor github ← deprecation in 11 days
npm stripe16 Nov 2026 · matched on github · Live from the vendor catalog
Package health
Every package, every day: known vulnerabilities with the version that fixes them, packages their maintainers abandoned, and runtimes past end of life. Import a package.json, requirements.txt, go.mod or Dockerfile and get the list to work through.
1
Vulnerable
2
Deprecated or end of life
1
Majors behind
lodash 4.17.20
Command injection and code injection (high) · upgrade to 4.18.1
request 2.88.2
deprecated by its maintainers · move to fetch
node 18-alpine
no security fixes since 30 Apr 2025
next 13.5.6
16.x available
react 19.3.1
latest release
Example workspace
Health score
Every workspace and product gets a score from 0 to 100, with each lost point explained, so you know what to fix next. Show it off as a badge in your README without revealing a single detail of your stack.
Checkout service · B
Example workspace
Alerts
Slack, email, a signed webhook or your calendar, at the lead times you choose, plus a Monday digest of what's coming. Acknowledge it and the reminders stop for everyone.
StackClock APP 9:00 AM
Due in 14 days: TLS certificate for api.acme.io expires
Example workspace
More features
We search public Certificate Transparency logs for every certificate under your domain, and repeat it weekly. You pick which ones to track.
Our own domain, from Cert Spotter · 20 Oct 2026
Typo and look-alike variants of your domain, checked weekly in DNS, so you see who registered one and whether it can receive mail.
3 of 281 variants of stackclock.app · 20 Oct 2026
Your pipeline sends only the files you choose, on every merge. No GitHub App and no access to your git repository.
curl -fsS https://stackclock.app/api/v1/stack/sync \ -H "Authorization: Bearer $STACKCLOCK_TOKEN" \ -F source=acme/api \ -F [email protected] -F [email protected]
From the CI sync docs
Show customers your stack is watched: a public page and a README badge with the grade and 90-day trend, never the details.
Example workspace
What it watches
A deadline's life
The default schedule. Change the lead times per workspace, or just for yourself.
Enough time to budget a renewal or plan a migration.
Pick an owner. Acknowledging stops reminders for everyone.
Most renewals and upgrades happen here.
Only deadlines nobody has acknowledged get this one.
Tomorrow it breaks.
One last reminder, then it moves to overdue on the timeline.
| Product | End of life | In |
|---|---|---|
| Node.js 22 | 30 Apr 2027 | in 176 days |
| Python 3.11 | 31 Oct 2027 | in 360 days |
| PostgreSQL 14 | 12 Nov 2026 | in 7 days |
| Ubuntu 22.04 | 1 Jun 2027 | in 208 days |
| PHP 8.2 | 31 Dec 2026 | in 56 days |
| Django 6.0 | 30 Apr 2027 | in 176 days |
What we never store
Keys, licenses and subscriptions are metadata only. Pasted secrets are rejected.
Only a keyed hash, for rate limits and the audit log.
Stripped before anything is saved.
Read in your browser. Only package names and versions are sent to us.
Pricing
For trying StackClock on a side project.
$0
For freelancers and indie developers.
$8.99/ month
For teams that share responsibility for a stack.
$11.99/ month per seat
Prices in USD. Sales tax or VAT is added at checkout where it applies.
Questions
No. For keys, licenses and subscriptions we store metadata only: a name, provider, expiry date, owner and a renewal link. Pasted secrets are detected and rejected.
We ask the registry via RDAP, or its WHOIS server for TLDs without RDAP (such as .io). If a registry publishes neither, we mark the domain as unknown, never as OK, and ask you for the date.
Yes. When you add a domain we search public Certificate Transparency logs (crt.sh, with Cert Spotter as a fallback), where every publicly trusted certificate is recorded, and list the hostnames under your domain that have a valid one. Nothing is monitored until you pick which to track, and the search repeats weekly so new subdomains show up. Wildcard certificates hide individual subdomain names, so add those by hand.
package.json, requirements.txt, pyproject.toml, go.mod, Gemfile, composer.json, Dockerfiles and docker-compose files, plus lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock, Pipfile.lock, composer.lock, go.sum) for exact versions. Import is on Pro and Team; on Free you add packages by hand.
Vulnerabilities from OSV.dev, which combines GitHub, PyPI, Go and other advisory databases. Deprecations and latest versions from the npm, PyPI and Go registries themselves. End-of-life dates from endoflife.date. Everything is checked daily and again whenever your stack changes.
Yes, on the Team plan. Add a Slack incoming webhook or any https endpoint; webhooks receive signed JSON for reminders, new vendor changes and new vulnerabilities.
Yes. Every account starts with a personal workspace. Upgrade to Pro for more assets and immediate alerts, or to Team to share a timeline.
Yes: 14 days of Pro or Team. Stripe asks for a card when the trial starts and emails you before it ends; cancel before then and you pay nothing. The Free plan needs no card at all.
Yes: no caps on assets, packages, products, members or integrations. A fair-use ceiling (20,000 assets and 20,000 packages per workspace) keeps the daily checks fast; if you need more, write to us and we will raise it.
Payments are processed by Stripe. Team plans are billed per seat and viewers are free. You can cancel any time from the billing portal.
Free for individuals. No credit card needed.
We use essential cookies to run StackClock. With your permission we would also use Google Analytics cookies to see how the website is used. Cookie Policy