HOW IT WORKS
Vulscore brings website security and diagnostics into one place. Check your configuration, understand the evidence, and prioritise improvements with transparent reports.
The scanner requests your page, follows up to five public redirects, and checks the HTTP entry point. Optional diagnostics make three GET requests at the final host’s root: a random missing .aspx page, trace.axd, and elmah.axd. It does not submit exploit payloads, authenticate, crawl, or execute page scripts.
Checks cover HTTPS, HSTS, content and framing policies, MIME sniffing, referrers, permissions, disclosure headers, and cookies. The optional classic ASP.NET checks look for recognizable diagnostic markers. ASP.NET Core does not have the same legacy configuration as ASP.NET Framework.
Only the sampled responses are tested. Bodies are limited to 64 KiB and read as UTF-8; unreadable or truncated diagnostic responses are inconclusive. A 200 response alone does not prove exposed logs. Custom diagnostic routes, authenticated pages, CSP semantics, TLS cipher suites, and application vulnerabilities need additional review. The 0–100 vulnerability score is a weighted configuration-risk heuristic: higher means more observed issues. Incomplete coverage is marked provisional; unknown checks are not passes. This is not CVSS or a guarantee of security.
Only scan websites you own or are authorised to test. Targets receive requests from this server with the VulscoreScanner user agent. Scan reports and response bodies are not stored by the application; cookie values are omitted from reports. Your browser and hosting access logs may retain request metadata. Do not enter URLs containing secrets.
Only public HTTP/HTTPS destinations on standard ports are allowed. DNS results are validated and connections use the validated IP addresses. Private and reserved networks, HTTPS downgrades, and unsafe redirect destinations are blocked. Requests have time and size limits; each instance permits four concurrent scans and twenty scan submissions per minute.
