Exposing Swagger/OpenAPI documentation is primarily a risk if your API has underlying security flaws, as it gives attackers a precise roadmap to find them.
Those detail every endpoint, parameter, and data model, making it easier to discover and exploit vulnerabilities like broken access control or injection points.
While a perfectly secure API mitigates the danger, protecting your documentation is a critical layer of defense that forces attackers to work without a map.
Severity: info
Fingerprint: 5733ddf49ff49cd1f3d88d6029a0f31b4f10edf354c8617dedb86afa5dbef3e2
Public Swagger UI/API detected at path: /swagger/v1/swagger.json - sample paths:
GET /cases/inspection-requests/{inspectionRequestId}
GET /cases/inspection-requests/{inspectionRequestId}/attachment/{attachmentFilename}
GET /cases/{caseId}
GET /cases/{caseId}/history
GET /cases/{caseId}/notes
GET /configuration/{configurationId}
GET /container-inspection-companies/{id}
GET /email-templates
GET /email-templates/{id}
GET /incidents/{incidentId}
GET /locations/{locode}
GET /users
GET /users/{userId}
GET /verified-shippers/search-global
GET /verified-shippers/{rawShipperId}
GET /version
GET /views/team
GET /views/team/{id}
GET /views/user
GET /views/user/{id}
POST /cases
POST /cases/assignment
POST /cases/export
POST /cases/ids
POST /cases/inspection-requests
POST /cases/inspection-requests/list
POST /cases/inspection-requests/{inspectionRequestId}/attachments
POST /cases/inspection-requests/{inspectionRequestId}/list-attachments
POST /cases/{caseId}/assignment
POST /cases/{caseId}/emails
POST /cases/{caseId}/emails/download
POST /cases/{caseId}/emails/preview
POST /cases/{caseId}/resendemail
POST /container-inspection-companies
POST /container-inspection-companies/list
POST /emails
POST /incidents
POST /incidents/customers/list
POST /incidents/list
POST /inspection-requests
POST /inspection-requests/response
POST /locations/list
POST /screening
POST /screening/{screeningId}/risksummary
POST /verified-shippers/create
PUT /cases/status
PUT /cases/status/reason
PUT /cases/statuses
PUT /cases/statuses/reason
PUT /cases/{caseId}/dueDate
PUT /cases/{caseId}/status
PUT /cases/{caseId}/status/reason
PUT /incidents/customers/{customerId}
Open service 2620:1ec:46::44:80 · api.case.qa.detect.hazcheck.com
2026-02-05 10:47
HTTP/1.1 307 Temporary Redirect Date: Thu, 05 Feb 2026 10:47:40 GMT Content-Type: text/html Content-Length: 0 Connection: close Location: https://api.case.qa.detect.hazcheck.com/ x-azure-ref: 20260205T104740Z-1788cd67658dxnzkhC1ATL9728000000042g000000006skq X-Cache: CONFIG_NOCACHE
Open service 13.107.246.44:443 · api.case.qa.detect.hazcheck.com
2026-01-23 07:58
HTTP/1.1 200 OK
Date: Fri, 23 Jan 2026 07:58:33 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 110
Connection: close
Request-Context: appId=
Strict-Transport-Security: max-age=15724800; includeSubDomains
X-Trace-Id: c94c3e30-7bd2-4cd3-a7aa-5587fac8ed33
x-azure-ref: 20260123T075833Z-15c4449dbb8t9594hC1YTO1t300000000e5g000000001wyf
X-Cache: CONFIG_NOCACHE
Accept-Ranges: bytes
{"name":"Hazcheck Detect Case Management API","message":"Welcome to the Hazcheck Detect Case Management API!"}
Open service 13.107.246.44:443 · api.case.qa.detect.hazcheck.com
2026-01-09 16:20
HTTP/1.1 200 OK
Date: Fri, 09 Jan 2026 16:20:51 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 110
Connection: close
Request-Context: appId=cid-v1:26c57984-58cd-400b-b24e-44e56f10a6da
Strict-Transport-Security: max-age=15724800; includeSubDomains
X-Trace-Id: 85936033-ce6f-4ce3-8f77-3ac66f50074d
x-azure-ref: 20260109T162051Z-169bcb8b8b864n4jhC1ATL6fd40000001p9g00000000ndwg
X-Cache: CONFIG_NOCACHE
Accept-Ranges: bytes
{"name":"Hazcheck Detect Case Management API","message":"Welcome to the Hazcheck Detect Case Management API!"}
Open service 13.107.246.44:443 · api.case.qa.detect.hazcheck.com
2026-01-02 21:49
HTTP/1.1 200 OK
Date: Fri, 02 Jan 2026 21:49:42 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 110
Connection: close
Request-Context: appId=cid-v1:26c57984-58cd-400b-b24e-44e56f10a6da
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Security-Policy: self
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
Feature-Policy: self
x-azure-ref: 20260102T214942Z-r1ff49d4475rhbjkhC1AMSr0zn00000010mg00000000hzya
X-Cache: CONFIG_NOCACHE
Accept-Ranges: bytes
{"name":"Hazcheck Detect Case Management API","message":"Welcome to the Hazcheck Detect Case Management API!"}
Open service 13.107.246.44:443 · api.case.qa.detect.hazcheck.com
2025-12-22 22:27
HTTP/1.1 200 OK
Date: Mon, 22 Dec 2025 22:27:19 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 110
Connection: close
Request-Context: appId=cid-v1:26c57984-58cd-400b-b24e-44e56f10a6da
Strict-Transport-Security: max-age=15724800; includeSubDomains
Content-Security-Policy: self
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: no-referrer
Feature-Policy: self
x-azure-ref: 20251222T222719Z-r1b65f586b974xg6hC1YTOg4580000000f7g00000000b2qz
X-Cache: CONFIG_NOCACHE
Accept-Ranges: bytes
{"name":"Hazcheck Detect Case Management API","message":"Welcome to the Hazcheck Detect Case Management API!"}