Avoid being blacklisted.
We ask the main mail and domain blacklists about your servers and tell you the moment one lists you. Your SPF, DKIM and DMARC records are watched too, so your mail keeps reaching inboxes.
Know before your customers do.
RMySitesUp watches your websites, domains, mail records and blacklists around the clock. When something breaks you hear about it first, by email, Telegram, Discord, Slack or webhook.
No passwords: you sign in with a link sent to your email.
shop.example.comresolved in 4 min 11 s
0:00checkGET https://shop.example.com: 503 in 1.8 s
1:00checkChecked again: 503. Confirmed, not a blip
1:01incidentOpened: shop.example.com is down
1:02alertSent to Telegram @ops and sam@example.com
5:12check200 OK in 212 ms
5:12resolvedClosed after 4 min 11 s. Saved to history and your status page
02:00pingDue now. Grace period: 15 min
02:15checkNo ping received
02:15incidentOpened: nightly-backup missed its heartbeat
02:15alertSent to Slack #ops
02:41pingPing received. The backup ran late
02:41resolvedClosed after 26 min
0:00checkAsked the mail blacklists about 203.0.113.9
0:02Spamhaus ZEN says listed (127.0.0.2)
0:02incidentOpened: mail.example.com is on a blacklist
0:02alertSent to sam@example.com
+1 hcheckAsked again: still listed
+9 hresolvedNot listed any more. Closed and saved to history
30 dcheckCertificate is valid, 30 days left
14 dcheckCertificate expires in 14 days
14 dalertSent to sam@example.com and Telegram @ops
12 dcheckNew certificate found, valid for 90 days
12 dresolvedClosed. Your visitors never saw a warning
An example. Your dashboard shows this for every incident.
Eight small apps in one account.
Each one does a single job well. Turn on the ones you need.
Show customers your availability, from an independent source.
A public status page that does not go down with your site, on your own address on paid plans. People trust numbers that are not published by the company itself.
Prove your uptime years from now.
Incidents and uptime history are never deleted, on any plan. When a client asks what happened last spring, you have the answer.
No false alarms.
Independent probes check your site as often as every minute and confirm a failure before they wake you. HTTP, keyword, API, port and ping. Alerts by email, Telegram, Discord, Slack, webhook or text message.
Know when a silent job stops.
Cron jobs and workers ping a URL when they run. If a ping goes missing, you hear about it.
Never lose a domain by accident.
Domain and certificate expiry and DNS changes are tracked, so a renewal never catches you off guard.
Let your tools do the setup.
A REST API, an OpenAPI file and an MCP endpoint let your scripts and AI assistants add checks and read incidents.
One account for every client.
Workspaces with roles, so a team or an agency can look after many clients at once.
One line in your cron job.
Or ask your AI assistant to do it. A documented REST API, an OpenAPI file and an MCP endpoint let scripts and agents create checks, add heartbeats and read incidents.
Open the API reference llms.txt for agentsAsk your assistantAdd a heartbeat to my nightly backup and alert me on Telegram if it doesn't run.
# crontab: the ping runs only if the backup succeeded
0 2 * * * /usr/local/bin/backup.sh && curl -fsS https://api.rmysitesup.com/hb/YOUR_TOKENSet up your first check in a minute.
Add a site, pick where alerts go, and you're covered.