cloudflare
tcp/443
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: 5733ddf49ff49cd12ec8532c2ec8532c2ec8532c2ec8532c2ec8532c2ec8532c
Public Swagger UI/API detected at path: /swagger/index.html
Open service 172.67.183.43:443 ยท arastur.com.tr
2026-01-23 09:03
HTTP/1.1 200 OK
Date: Fri, 23 Jan 2026 09:03:40 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Cache-Control: no-cache, no-store
pragma: no-cache
Report-To: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=IwX6rvS%2BnhM4oM470uOYsgEGj9rJR7vnSBLQ5WXgU1myvOkW%2Blb9McsiuE%2FY8gSDBT2ql%2BUab6RtC8pJNO%2FnO6ORwdWrBVoVWj0ths2H"}]}
vary: Accept-Encoding
Server: cloudflare
strict-transport-security: max-age=2592000
Set-Cookie: .AspNetCore.Antiforgery.Q_pMdWqZ_N0=CfDJ8Atd0ujh6yxDlDkYe7Fb7We2nNJtTYfSky62tMWEwz0G07KzRZdyVZ67gkRdHT6pYYybx19JU6XLDaObqWrIOjVEZmlOZ80t7RxxldkFlF9EGCQeE_dW2wJR_lVYJy6KB1NV8HsJ3myMQogCnqR-Keg; path=/; secure; samesite=none; httponly
x-powered-by: ASP.NET
x-powered-by-plesk: PleskWin
cf-cache-status: DYNAMIC
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Server-Timing: cfCacheStatus;desc="DYNAMIC"
Server-Timing: cfEdge;dur=11,cfOrigin;dur=1552
CF-RAY: 9c261e7c7fec42d8-EWR
alt-svc: h3=":443"; ma=86400