Get notified whenever something on your site breaks.
Upcheck checks every site you own for uptime, SSL/TLS certificate expiry, DNS changes and domain renewal — and, when you ask, a page’s text, a price, a TCP port or an API endpoint — and warns your team by Email, Slack, Discord, Teams, or Webhook before your customers notice.
Cancel anytime. No agent, no DNS change, no code on your side.
- $10
- base, per month
- $1
- per site, per month
- 4
- ways every site is watched
Upcheck reads the certificate every twelve hours and stays silent in between. You decide which of the 30, 14 and 7-day thresholds you want, per site or across all of them.
Issued
Issuer, SANs, serial and chain recorded the moment it appears.
30 days
The first heads-up, while renewal is still a routine Tuesday task.
14 days
A second word, to whoever actually owns this site.
7 days
Last call, to every channel you chose — and no more than that.
Renewed
Back to green, with the change written into the activity feed.
Everything your website needs to run properly.
The server, the certificate, the DNS, the domain name, and the pages, ports and APIs behind it. The first four are watched from the moment you add a site; the rest, the moment you point at something.
- Every 5 minutes
Uptime
A real HTTPS request, confirmed twice before anyone is paged, with the response time kept on every probe.
How it works - Every 5 minutes
API endpoints
The same probe aimed at an endpoint, with a path, request headers, the status it should return, text its body must hold and a latency limit.
How it works - Twice a day
SSL certificate
A real TLS handshake: validity, chain, hostname coverage and expiry, with warnings at the thresholds you set.
How it works - Every 6 hours
DNS
The record set fingerprinted against the last, so a moved A, AAAA, NS or MX record is an alert and rotation is not.
How it works - Daily
Domain registration
Expiry and registry holds over RDAP, weeks before a missed invoice takes the name down.
How it works - Every 5 minutes
Keyword
A phrase that should be on a page, or should not: a login button present, “Out of stock” absent.
How it works - Every 5 minutes
Page change
A page, an element or the first number in it compared with the previous probe, with before and after in the alert.
How it works - Every 5 minutes
Ports
A TCP connect to SSH, a database, mail or a game server, on the site itself or the origin behind it.
How it works
Wherever your team already is.
Five places to send a warning, and reusable recipient lists so a rule points at a group of people rather than a column of addresses.
- Slack
- Discord
- Microsoft Teams
- Webhook
You get an alert when something you asked about changes.
- 01
One dashboard
Uptime every five minutes — with a path, headers and an expected status when it's an API — the certificate twice a day, DNS four times, the registration daily, a keyword on any page you name, a page watched for change, and the TCP ports that must stay open.
- 02
Outages, confirmed first
A site is only called down after two failed probes in a row. When it comes back, you hear that too.
- 03
Clear DNS visibility
We check your DNS records every 6 hours and tell you if they change or stop working.
- 04
Alerts that fit your team
Email, Slack, Discord, Microsoft Teams, or your own webhook endpoint. Pick per rule.
- 05
Thresholds you choose
30, 14 or 7 days out. Several per rule, scoped to a single site or all of them at once.
- 06
The whole certificate
Issuer, subject alternative names, serial, signature algorithm, key type and size, fingerprint, chain.
- 07
A record of every check
Every check result kept per site, beside a feed of what changed and who changed it.
- 08
Reusable recipient lists
Group the people who should hear about a site once, then point any rule at the group.
Eight sites come to $18 a month, every check included. No tiers to outgrow.
Monitor my sitesSleep through the next surprise.
Add your sites, choose who hears about them and where, then let Upcheck keep the calendar.