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: 5733ddf49ff49cd18553ecf70a92ecf22b6abd232206e07c97a3ba75b34555d3
Public Swagger UI/API detected at path: /swagger-ui.html - sample paths:
DELETE /api/v2/case/animal_detail/{id}
DELETE /api/v2/case/file/{id}
DELETE /api/v2/case/file_additional/{id}
DELETE /api/v2/case/personnel/{id}
DELETE /api/v2/case/{id}
DELETE /api/v2/user/{id}
GET /actuator
GET /actuator/health
GET /actuator/health/{component}
GET /actuator/health/{component}/{instance}
GET /actuator/info
GET /api/v2/address
GET /api/v2/analysis/export
GET /api/v2/animal_species
GET /api/v2/announcement
GET /api/v2/case
GET /api/v2/case/animal_detail
GET /api/v2/case/file
GET /api/v2/case/file_additional
GET /api/v2/case/note
GET /api/v2/case/note/{id}
GET /api/v2/case/personnel
GET /api/v2/case/undertaker
GET /api/v2/case/year
GET /api/v2/case/{caseNum}
GET /api/v2/case/{caseNum}/export
GET /api/v2/case_type
GET /api/v2/complaint_category
GET /api/v2/current_brief
GET /api/v2/healthcheck
GET /api/v2/me
GET /api/v2/scheduler/case_email
GET /api/v2/tag
GET /api/v2/undertaker
GET /api/v2/user
GET /error
PATCH /api/v2/animal_species/priority
PATCH /api/v2/case_type/priority
PATCH /api/v2/complaint_category/priority
PATCH /api/v2/current_brief/priority
PATCH /api/v2/tag/priority
POST /api/v2/auth
POST /api/v2/user/{id}/password
PUT /api/v2/animal_species/{id}
PUT /api/v2/case/animal_detail/{id}/animal_species
PUT /api/v2/case/animal_detail/{id}/complaint_category
PUT /api/v2/case/animal_detail/{id}/count
PUT /api/v2/case/animal_detail/{id}/current_brief
PUT /api/v2/case/personnel/{id}/{column}
PUT /api/v2/case/{caseNum}/{column}
PUT /api/v2/case_type/{id}
PUT /api/v2/complaint_category/{id}
PUT /api/v2/current_brief/{id}
PUT /api/v2/tag/{id}
PUT /api/v2/user/{id}/color/{color}
PUT /api/v2/user/{id}/is_active/{is_active}
PUT /api/v2/user/{id}/role/{role}
Severity: info
Fingerprint: 5733ddf49ff49cd1b6e67656b6e67656b6e67656b6e67656b6e67656b6e67656
Public Swagger UI/API detected at path: /swagger-ui.html
Open service 142.251.141.115:443 · api.spca.org.tw
2026-01-09 06:32
HTTP/1.1 404 Not Found
content-type: application/json;charset=UTF-8
x-cloud-trace-context: 2c0ff61eeb03ffff3b7a8e97e9aa536a;o=1
date: Fri, 09 Jan 2026 06:32:54 GMT
server: Google Frontend
Content-Length: 104
Connection: close
{"timestamp":1767940374830,"status":404,"error":"Not Found","message":"No message available","path":"/"}
Open service 142.251.141.115:443 · api.spca.org.tw
2026-01-02 02:47
HTTP/1.1 404 Not Found
content-type: application/json;charset=UTF-8
x-cloud-trace-context: b168fcf312c03e731182d0224eb0ee23
date: Fri, 02 Jan 2026 02:47:48 GMT
server: Google Frontend
Content-Length: 104
Connection: close
{"timestamp":1767322068009,"status":404,"error":"Not Found","message":"No message available","path":"/"}
Open service 142.250.186.147:443 · api.spca.org.tw
2025-12-23 05:55
HTTP/1.1 404 Not Found
content-type: application/json;charset=UTF-8
x-cloud-trace-context: 97e2a84fc76993b90cd206cdab77c065
date: Tue, 23 Dec 2025 05:55:33 GMT
server: Google Frontend
Content-Length: 104
Connection: close
{"timestamp":1766469333896,"status":404,"error":"Not Found","message":"No message available","path":"/"}
Open service 142.250.186.147:443 · api.spca.org.tw
2025-12-20 13:38
HTTP/1.1 404 Not Found
content-type: application/json;charset=UTF-8
x-cloud-trace-context: fb6932bbefc9643ce9d90c59fddd9511;o=1
date: Sat, 20 Dec 2025 13:38:49 GMT
server: Google Frontend
Content-Length: 104
Connection: close
{"timestamp":1766237929824,"status":404,"error":"Not Found","message":"No message available","path":"/"}