How Duke42 checks security information
Official sources, explicit affected versions and practical repair guidance.
Where our vulnerability information comes from
We use vendor security advisories and published records in the official CVE List. Vendor guidance determines affected versions and remediation; CVE identifiers let readers cross-reference the same issue. Our current advisory window is 24 July–24 October 2026.
What the free website check can tell you
It fetches the public homepage and reads visible technology signals such as response headers, generator tags and asset paths. It does not log in, execute exploit payloads, scan ports or change the website. Hidden components and patched vendor builds may not be identifiable externally.
What a finding means
A possible match needs verification against installed versions and configuration. Unknown is not safe; a matching product name is not a confirmed vulnerability. We do not invent findings when a scan has insufficient evidence.
How repairs are checked
The intended repair workflow is to inventory the affected component, preserve a recovery copy, apply a supported fix and check key functions afterwards. The site accepts repair requests; submitting a form does not itself deploy an automated fix.
Editorial responsibility
These explanations and comparisons are published by Duke42. Comparisons link to vendors and disclose that Duke42 is a participant. This snapshot was checked on 24 October 2026; it is not a continuously refreshed threat feed.