Keep every client site healthy after handover
You launch the site and move on. We keep checking it: security headers, TLS and domain expiry, DNS and email authentication, privacy and cookie pages, SEO basics, speed, JavaScript errors and uptime. Between weekly summaries, you hear from us only when something changes.
Free, no sign-up. The basic check makes only the requests an ordinary browser would.
What usually breaks on client sites months after launch
- HighFree check
The TLS certificate is about to expire
Auto-renewal quietly stops after a hosting or DNS change, and nobody notices until visitors get a browser warning. We flag the certificate when fewer than 14 days are left, so there is time to renew it.
- MediumFree check
No DMARC or SPF, so the client’s email lands in spam
Without these DNS records, mailbox providers can’t tell the client’s real invoices and contact-form replies from forgeries, and treat both with suspicion. We read the domain’s DNS and say which record is missing or too permissive.
- HighFree check
Analytics running with no consent tool or privacy policy
Analytics or ad trackers on the page with no recognised consent tool, or no link to a privacy policy. Often added after launch by someone on the client’s side. A GDPR problem for the client; we point it out, it isn’t legal advice.
- MediumFree check
Security headers missing
No Content-Security-Policy, HSTS or X-Content-Type-Options: nosniff. A server move or a new CDN often drops them. We say which ones are missing and where to add them on that host.
- HighPro
The site is down, or a deploy broke the home page
Uptime is checked every five minutes on Pro and every minute on Business. Every new deploy is checked within minutes: does the page answer, render and load its scripts. If not, you get an alert.
- CriticalPro
An exposed .env or .git, Supabase tables anyone can read
These active probes run only after the client’s domain is verified with a DNS record or a meta tag. We request a short list of paths such as /.env and /.git/config and count how many rows Supabase tables return to the public key — never reading their contents.
How agencies use it
Nothing needs to be installed on the client’s site: we look at it from outside, the way a browser does. The report is a web page with a link you can share — not a PDF, and it carries our name, not yours.
Run the free check and send the client the link
Enter the client’s domain on scanyoursite.app without signing in. About a minute later you have a report, and anyone with its link can open it — the client doesn’t need an account to read it.
Put the sites you maintain under one account
Sign in with your email and add each site you look after. Business covers 10 sites, with full checks twice a day and uptime every minute. Reports for these sites stay private until you turn on “Share reports by link” on the site’s page.
Send alerts where your team already looks
Each site has its own channels: Telegram, email, or a webhook that Slack and Discord accept as is. Each channel has its own threshold — for example, critical findings to the team’s Telegram and everything else by email.
Once a month, show the client what changed
Re-check the site and go through the report with the client: what got fixed since last time and what is new. If they should have a link of their own, turn on sharing for that site and send them the report link; turn it off and the links close.
Hand the fixes to a developer or an AI tool
The report turns its findings into one prompt: what is wrong, where, and how to confirm the fix. Paste it into a ticket for the developer on the project, or into Cursor, Claude Code or Lovable if that is how the site was built.
Fix these issues on client-site.example. Find each one first; make the smallest change that fixes it. 1. No DMARC record. Add at the DNS host: _dmarc TXT "v=DMARC1; p=none; rua=mailto:dmarc@client-site.example" 2. No Strict-Transport-Security header. Add max-age=31536000 on the web server or CDN. When done, re-check: https://scanyoursite.app/en?check=client-site.example
One plan for all your client sites
Business: $99 / €99 a month for up to 10 sites, checks twice a day, uptime every minute, alerts by email, Telegram or webhook, every finding explained with a fix. Pilot for agencies: three months free for the first ten agencies that give us feedback — write to support@scanyoursite.app.
See plansQuestions
Do my clients need accounts?
No. A free check run without signing in gives a report anyone with the link can open — send it to the client. For a monitored site, turn on “Share reports by link” on its page and send that link. Monitoring and alerts stay under your account.
Can I add more than 10 sites?
Write to support@scanyoursite.app. Today Business covers 10 sites; beyond that we set it up by agreement.
Do you touch the client’s site?
Only the way a browser does: the page, its scripts, robots.txt, the sitemap, DNS and the certificate. We never log in or submit forms. Active probes, such as a request for /.env, run only after whoever controls the domain verifies it with a DNS record or a meta tag.
Who sees the alerts?
Only the channels you connect, set per site: one client’s site can go to your team chat, another’s to the developer who maintains it. An email address gets alerts only after its owner confirms it, so a client hears from us only if you add them and they agree.
Can the client pay directly?
Yes. Any plan can be bought by the client under their own account, with their own alerts. The agency pilot is for sites under your account.
Paste your URL. Get the list in about a minute.
Every finding comes with what it means for you and how to fix it — or a prompt your AI coding tool can apply.
Free, no sign-up. The basic check makes only the requests an ordinary browser would.