How website health checks work
HelpFixMySites.com’s quick check requests the public homepage after the visitor confirms they own the domain or are authorized to monitor it.
What the scanner checks
The public scan reports homepage availability, response timing, HTTPS, certificate details, selected security headers, and basic page signals. Member monitoring adds DNS and domain expiry, mail policies, standard public policy files, canonical URLs, accessibility basics, and a small sample of internal links. Shodan observations and reputation results depend on configured provider access.
Response timing is a single network sample. Accessibility checks cover basic HTML signals. Mobile and desktop Lighthouse lab tests run when PageSpeed Insights is configured, with assessment times and optimization priorities. Real-user Core Web Vitals and comprehensive accessibility audits remain separate, unavailable assessments. Google Web Risk checks submitted and final homepage URLs when configured. Observed exact component versions can be compared with OSV advisories; hidden and server-side dependencies are not assessed.
Read the score and the coverage together
Each assessed check contributes 100 points for pass, 50 for warning, or 0 for failure. The scanner averages checks within each category, then averages the assessed categories for the overall score. Grades are A at 90 or higher, B at 80, C at 70, D at 60, and F below 60.
Coverage shows how many displayed checks were assessed. Assessment model labels identify expanded checks; trend lines and change calculations do not bridge model changes. Blocked, unavailable, ownership-restricted, and not-applicable results stay out of the score. A high score with low coverage gives an incomplete picture; review the missing evidence before making a decision.
Evidence first, practical next steps
Open a finding or hover over a dashboard score to see the reason behind it. A site report card brings together the overall score, category results, saved trends, and remediation recommendations. Export the report as a PDF or download trend history as CSV.
Saved scans support comparisons over time. Email notifications, when enabled and configured, report score changes, IP and MX changes, and new reputation findings. Saved static text fingerprints and third-party resource hosts are compared with the previous assessed scan. Blocked scans do not replace these observations. Changed content may be intentional or dynamic; review the evidence before treating it as an incident. These comparisons are not an approved-change baseline or a complete browser-rendered content monitor.
Passive public checks only
The scanner uses ordinary public web requests, DNS lookups, TLS connection details, and configured intelligence sources. It does not submit forms, send attack payloads, guess hidden paths, brute-force, or attempt to bypass bot challenges. Passive findings do not establish that a site is free of vulnerabilities.
Respectful request limits
Requests use a five-second timeout for homepage requests, cap the response body, allow at most three redirects within the submitted domain and its www sibling, and reject private or non-public DNS destinations. Recognized verification pages, including HTTP 200 interstitials, are marked blocked rather than failed. Provider requests have separate time budgets and caching: up to five minutes for Web Risk, six hours for Lighthouse, and 24 hours for advisories. Missing keys, denied access, and rate limits are identified and left unscored.