New and resolved findings
A finding that appears or disappears between two scans becomes a change event. A failed or partial scan is never treated as a fix.
Weekly · Monthly
Save your sites, verify that you control them and let RedSentinel scan again every week or month. You see what is new, what is fixed and when a certificate is about to expire.
Each scheduled scan is compared with the previous complete one.
A finding that appears or disappears between two scans becomes a change event. A failed or partial scan is never treated as a fix.
Security or SEO scores that move by a meaningful number of points are flagged, in both directions.
You are warned as a certificate crosses the 30, 14 and 7 day thresholds, and again if it has expired.
A sharp SEO score fall, or a new critical indexing, robots, canonical or redirect issue, is raised as a regression.
Three steps, no installation.
Register the URL, then prove control with a DNS TXT record or a meta tag. Recurring scans require verification by default.
Choose weekly or monthly. Nothing runs more often than every seven days, and the first scan sets the baseline.
Events appear on the site page. A signed webhook is available, and email notifications depend on how the service is configured.
Monitoring is useful only if the alerts stay worth reading.
The first scan of a site creates a reference and does not raise events, apart from certificate expiry.
The same event is not repeated within your cooldown window, so a flapping finding does not flood you.
Switch individual event types on or off in your notification settings.
Scheduled re-scans are not uptime monitoring or a real-time alerting system.
The same checks as the public scanner, run weekly or monthly on saved sites with change detection.
Change digests can be posted to an HTTPS endpoint with an HMAC signature.
Delivery depends on the email provider being configured for the service. If it is not, deliveries are recorded as skipped.
The shortest interval is seven days. Outages, response times and live traffic are not monitored.
Search positions and mentions in AI answers are not tracked.
No. Scans run on a weekly or monthly schedule. It is built to catch configuration drift and regressions, not outages.
Yes. Saved sites, schedules and notifications belong to an account. The public scanner needs no account.
Add a DNS TXT record named _redsentinel-verify on your domain, or place a redsentinel-verify meta tag on the page, then ask RedSentinel to check.
New findings, resolved findings, severity changes, score improvements and regressions, SEO regressions and certificate expiry tiers.
No. Recurring scans require a verified site by default, and you should only scan sites you are authorised to assess.
Create an account, verify a site and choose a schedule.