---
title: "List all web security data of a company."
method: GET
path: "/api/v2/companies/{id}/findings/websitesecurity"
tags: ["Findings"]
---

# List all web security data of a company.

`GET /api/v2/companies/{id}/findings/websitesecurity`

This is a special analysis of the company’s main website. The findings are collected from the SSL/TLS Strength, Patch Management, Application Security, Web Ranking and Brand Monitoring sub-categories.
 This category has 6% effect on total scan score.<br/><br/> For storage optimization, the system <b>permanently</b> deletes all findings that haven't been detected by the Black Kite scanner for over a year. Findings with manually changed statuses or associated tickets are excluded.

## Path parameters

- `id` integer, required

## Query parameters

- `page_number` integer
- `page_size` 10 | 20 | 30 | 50 | 100 | 250

## Response `200`

Success

- WebsiteSecurityFinding[]
  - `Domain` string — The domain which this finding is related.
  - `Performance` number, nullable — Score representing the performance of the web site. Individual findings can be fetched by accessing WebRanking endpoint's GooglePageSpeedInsightsPerformanceFindings property.
  - `SecurityHeaders` number, nullable — Score representing the security HTTP headers of the web site. Individual findings can be fetched by accessing the SecurityHeaderRelatedControlIds list.
  - `SecurityHeaderRelatedControlIds` string[] — ApplicationSecurity security control ids related to Security Headers.
  - `PossibleVulnerabilitiesRelatedControlIds` string[] — ApplicationSecurity security control ids related to Possible Vulnerabilities.
  - `PatchLevel` number, nullable — Score representing the patch level of the web site. Individual findings can be fetched by accessing PatchManagement endpoint.
  - `CodeQuality` number, nullable — Score representing the code quality of the web site. Individual findings can be fetched by accessing CodeQualityFindings list.
  - `SslTlsStrength` number, nullable — Score representing the SSL/TLS strength of the web site. Individual findings can be fetched by accessing SSL/TLS Strength endpoint.
  - `LatestScreenshotUrl` string — The latest screenshot of the website.
  - `CodeQualityControlId` string — The unique identifier of the control that this finding relates to.
  - `CodeQualityFindings` object[], nullable — The core reason to run your HTML documents through a conformance checker is simple: To catch unintended mistakes—mistakes you might have otherwise missed—so that you can fix them. Beyond that, some document-conformance requirements (validity rules) in the HTML spec are there to help you and the users of your documents avoid certain kinds of potential problems. This validator checks the markup validity of Web documents in HTML, XHTML, SMIL, MathML, etc. This category (Website Security) may contain domains that is not be listed in WebRanking category. Hence a separate code quality finding list. Max 1000 findings will be returned.
    - `Title` string — The title of the finding. It's always a good idea to whitelist HTML sanitize this value before rendering it as HTML.
    - `Location` string — The location of the finding in the code.
    - `Code` string — The code block that triggers the finding. It's always a good idea to whitelist HTML sanitize this value before rendering it as HTML.

## Other responses

- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `default` — Failure

---

[API](https://skmtc.net/blackkitetech/apis/black-kite-api.md) · [All operations](https://skmtc.net/blackkitetech/apis/black-kite-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/blackkitetech/black-kite-api/revisions/616dfa9b3b1f/schema)