Uptime monitoring that tells you your site is down before your customers do
A reliable website stays up for visitors and keeps working after each change to its code.
17:38 GET / 200 312 ms17:43 GET / 50317:44 GET / 50317:49 GET / 200 298 msUncaught TypeError: items.map is not a functionPage code runs into errors while loadingSiteCMD watches your home page and emails you when it goes down or comes back up. The free SiteCMD CLI checks your code for what could stop your site working after your next change.
Explore what keeps a website up and working
Find out why your site is down and when your domain expires
3 guides
Get an email when your site goes down and another when it's back up.
Read the guide: Uptime monitoringTell your own connection apart from a real outage, then trace the error to its cause.
How to fix
- See whether other websites loadIf other websites fail too, investigate your internet connection first.
- Try Chrome's Incognito modeOpen the page in Chrome's Incognito mode. If it loads, exit Incognito mode and turn off extensions or clear browsing data. If turning off extensions fixes the problem, turn them back on one at a time to find the cause.
- Try mobile data instead of Wi-FiOpen the same address over a different connection. If the site loads there, it isn't down for everyone, so look at the first network, such as its DNS or its internet provider.
- Save the exact error and timeNote the address, the exact error message and the time it failed. The error points to a likely cause below, and the time helps you find the failure in your host's logs.
Review the registration date and renewal settings before your domain runs out.
How to fix
- Review the renewal paymentConfirm auto-renewal is enabled if you want it, and replace an expired or canceled payment card in the registrar account.
- Keep renewal notices reachableUpdate an old contact email and check the registrar's renewal reminders before the registration ends.
Reliability
Your domain name expires soon or has expired
Your domain's registration is approaching or past its expiration date, which risks losing the domain and everything on it.
Fix with your agent
# SiteCMD Fix Brief: Your domain name expires soon or has expired Site: https://yoursite.com ## What is wrong Your domain's registration is approaching or past its expiration date, which risks losing the domain and everything on it. ## How to fix Read the reported RDAP expiration date and urgency tier first; a date within 90 days is a planning warning, not proof that auto-renew failed, and even a past date needs confirmation because renewal publication can lag. Confirm status and renewal intent in the authoritative registrar account, renew immediately if needed, verify auto-renew and the payment path, and keep registrar access recoverable independently of the domain being protected. ## Acceptance criteria After you finish, SiteCMD will re-run the check against https://yoursite.com. The fix is only accepted if that check passes. Make the smallest change that satisfies it.
Keep your database in sync with its migrations and your agent instructions clear
2 guides
Keep your local database in step with the migrations in your repository.
How to fix
- Run
npx prisma migrate devto detect the drift and generate a corrective migration, then confirm withnpx prisma migrate status. If Prisma reports a history conflict, inspect the exact database changes before usingprisma migrate resolve; marking a migration applied is a bookkeeping assertion, appropriate only when the database already has that migration's intended effect.
Reliability
Local database may be behind on changes (SQLite, Prisma)
The Prisma schema and the actual local database no longer agree with each other, which can cause confusing errors.
Fix with your agent
# SiteCMD Fix Brief: Local database may be behind on changes (SQLite, Prisma) Site: https://yoursite.com ## What is wrong The Prisma schema and the actual local database no longer agree with each other, which can cause confusing errors. ## How to fix Run `npx prisma migrate dev` to detect the drift and generate a corrective migration, then confirm with `npx prisma migrate status`. If Prisma reports a history conflict, inspect the exact database changes before using `prisma migrate resolve`; marking a migration applied is a bookkeeping assertion, appropriate only when the database already has that migration's intended effect. ## Acceptance criteria SiteCMD accepts the fix when an authenticated code submission bound to this attempt, from your CI or the SiteCMD CLI, no longer reports the finding. SiteCMD records the result as self-attested. Make the smallest change that fixes the reported risk.
Keep one clear, secret-free set of instructions for coding agents.
How to fix
- Expand the instruction file so an agent is useful immediately: describe the stack and where the important code lives, explain how to run the app locally, list the exact build, test, lint, and typecheck commands an agent should use to verify its own work, and write down the hard rules, such as conventions to follow and files that must never be touched.
Reliability
An AI instructions file is almost empty
The file meant to guide AI coding agents is too thin to be useful, missing the real commands and rules they need.
Fix with your agent
# SiteCMD Fix Brief: An AI instructions file is almost empty Site: https://yoursite.com ## What is wrong The file meant to guide AI coding agents is too thin to be useful, missing the real commands and rules they need. ## How to fix Expand the instruction file so an agent is useful immediately: describe the stack and where the important code lives, explain how to run the app locally, list the exact build, test, lint, and typecheck commands an agent should use to verify its own work, and write down the hard rules, such as conventions to follow and files that must never be touched. ## Acceptance criteria SiteCMD accepts the fix when an authenticated code submission bound to this attempt, from your CI or the SiteCMD CLI, no longer reports the finding. SiteCMD records the result as self-attested. Make the smallest change that fixes the reported risk.
Frequently asked questions
Can a website reliability checker tell me if a site is trustworthy?
No. Judging whether a site or its information can be trusted is a different job. SiteCMD checks your own site: whether it stays up, and whether its code is ready for the next change.
Does uptime monitoring need access to my code?
No. Uptime monitoring needs only your site's address. To check your code, run the free SiteCMD CLI in your project.
What does SiteCMD check in my code for reliability?
The gaps that let a change break your site or slow your recovery from an outage, such as tests that never run in CI, errors that are caught and ignored, migrations out of step with your database and no plan for restoring a backup.