Search and browse Common Vulnerabilities and Exposures entries with severity scores and affected products.
Look up a known CVE identifier or search CVE records to identify vulnerabilities associated with a product. The tool presents the record description, available severity score, and affected-product information so you can decide which advisory needs closer review. A CVE match does not prove that a particular installation is vulnerable. Product naming, version ranges, configuration, platform, and installed fixes still have to be compared with the system in question.
Use a complete identifier such as CVE-2021-44228 when you already have a CVE number. A broader search helps browse possible records when you begin with a product or vulnerability term. Results are CVE entries, not detections from the user's computer. The lookup does not inspect installed software, running services, configuration, or network exposure.
A result associates the CVE description with any displayed severity score and affected-product data. Read product names and version statements literally because similar editions, forks, operating systems, or package builds may not share the same status. A CVSS score describes technical severity using defined metrics. It is not a probability that exploitation will occur.
No. A CVSS score summarizes technical severity from defined metric values. It does not measure your asset's importance, how widely the vulnerable feature is deployed, whether attackers are currently exploiting it, or whether controls reduce exposure. Combine the record with vendor guidance, deployment context, and current threat information when prioritizing work.
No. It returns published vulnerability information rather than examining the device. Confirmation requires identifying the installed product and version, checking platform and configuration conditions, and determining whether the relevant fix or mitigation is present. Vendor advisories are often needed because package revisions and backported fixes may not align neatly with upstream version numbers.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.