Know what changed after a release
Watch redirects, headers, content, robots.txt, sitemap, and Core Web Vitals after deployments that affect customer-facing pages.
Security and site-health monitoring
Watch the website signals that explain trust and usability.
Dashy turns passive security headers, Core Web Vitals, sitemap, robots.txt, redirects, content checks, SSL, and domain posture into scheduled dashboard components.
Site-health board
public posture
HeadersBCSP missing
SSL76dvalid hostname
Vitalsneeds workLCP elevated
Robotsallowedsitemap found
Redirectloopcheckout path
- Passive checks
- No vulnerability scan
- Public tools
- Save to dashboard
- Reports
- Evidence included
1. Inspect passively
Run public header, SSL, redirect, robots.txt, sitemap, and vitals checks without intrusive scanning.
2. Find release risk
Catch missing headers, blocked crawl paths, redirect loops, and elevated Core Web Vitals after changes.
3. Add trust basics
Keep SSL days, hostname match, CAA, DNSSEC, domain expiry, and email DNS beside uptime.
4. Schedule evidence
Save useful findings as dashboard checks with history, recommendations, and client-safe reporting.
Dashboard components
Passive checks that help owners fix visible website risk.
- Security headers
- HTTP security header posture, missing controls, response evidence, and plain-English recommendations.
- Vitals and crawl
- Core Web Vitals, sitemap availability, robots.txt access, and crawl-blocking release mistakes.
- Routes and content
- Redirect chains, final status, expected content, content changes, and broken public pages.
- Trust basics
- SSL days left, hostname match, domain expiry, CAA, DNSSEC, and email DNS health alongside uptime.
Passive scope
Keep security monitoring useful without probing private systems.
Dashy should explain visible website risk from public evidence, then leave intrusive testing and remediation choices with the site owner.
- Public evidence
- Checks use public headers, TLS, redirects, robots.txt, sitemap, Core Web Vitals, and domain/DNS posture.
- No exploit scan
- Launch checks do not fuzz forms, brute-force routes, submit payloads, or test private admin areas.
- Owner review
- Recommendations describe the visible issue and manual fix path before any public board or client report is shared.
- Safe output
- Shared dashboards should show grades, missing controls, crawl status, and SSL/DNS posture without exposing sensitive response detail.
Explain risk without security theatre
Use passive evidence and client-safe language to show what needs fixing without implying an intrusive vulnerability scan.
Keep trust signals beside availability
Put SSL, DNS, headers, vitals, uptime, redirects, and content checks into one board instead of separate tools.
Start with passive public checks, then monitor the results.
Security headers, Core Web Vitals, sitemap, robots.txt, redirect, content, SSL, and domain tools can inspect a target before you save scheduled checks.