Vulnerabilities

Check IP/Domain Vulnerabilities

The given response in the JSON format provides details about the vulnerabilities associated with the queried IP address or domain. It includes information such as open ports (e.g., 80, 443, 2052), associated tags (e.g., "cdn"), and sections for potential vulnerabilities (vulns) and common platform enumerations (cpes), both of which are shown as empty. Additionally, it lists hostnames related to the domain, which is also empty in this case.

Request

GET https://ismalicious.com/api/check/vulnerabilities?query=qouv.fr

Try this endpoint in your browser 🔗

Request

Query Parameters

Parameter	Type	Description
query	string	The IP address / Domain name to check.

Response

Response

{
    "vulnerabilities": {
        "cpes": [],
        "hostnames": [],
        "ip": "172.64.154.211",
        "ports": [
            80,
            443,
            2052,
            2082,
            2083,
            2086,
            2087,
            8080,
            8443,
            8880
        ],
        "tags": [
            "cdn"
        ],
        "vulns": []
    }
}

Description

This feature allows users to check for vulnerabilities by querying specific IP addresses or domain names. The response details any open ports, associated tags, and provides the IP address being inspected. This function is essential for enhancing cybersecurity by identifying potential weaknesses, ensuring safe browsing, and protecting sensitive information from cyber threats. It aids businesses in maintaining network security, thereby safeguarding their reputation and minimizing operational disruptions.

Why is this useful?

• Identify open ports that could pose security risks.

• Determine associated tags to understand the context of vulnerabilities.

• Verify the queried IP address or domain for security assessments.

• Enhance cybersecurity by flagging potential weaknesses.

• Protect sensitive information and ensure safe browsing experiences.

• Maintain network security, safeguard reputation, and minimize business disruptions.

• Use separate endpoints for optimized performance and specific vulnerability checks.

More:

More:

For performance reasons, you'll find other separate endpoints for each sub-check you want to look after:

Reputation

Geolocation

Whois