Microsoft-IIS 10.0
tcp/443 tcp/80
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: 5733ddf49ff49cd1aad03549dbdfbb7014bf82528068a87aa030f99552c3bb26
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/Activity/detail
GET /api/Activity/list
GET /api/Advert/brandList
GET /api/Advert/brandModelList
GET /api/Conversation/list
GET /api/Google/searchPlace
GET /api/Location/cities/{countryId}
GET /api/Location/countries
GET /api/Media/view
GET /api/Notification/list
GET /api/Place/activityList
GET /api/Place/propertyList
GET /api/Post/hashtagList
GET /api/Profile/favoritePlace
GET /api/Profile/followList
GET /api/Profile/socialProfile
GET /api/Profile/timeline
GET /api/Type/translation
POST /api/Account/checkValue
POST /api/Account/forgotPassword
POST /api/Account/login
POST /api/Account/register
POST /api/Account/saveDevice
POST /api/Account/sendValidateCode
POST /api/Account/validationAccount
POST /api/Advert/delete
POST /api/Advert/detail
POST /api/Advert/detailByCode
POST /api/Advert/save
POST /api/Advert/search
POST /api/Campaign/detail
POST /api/Company/addMedia
POST /api/Company/changeMeta
POST /api/Company/deleteMedia
POST /api/Company/detail
POST /api/Company/detailInfo
POST /api/Company/list
POST /api/Company/register
POST /api/Company/save
POST /api/CompanyComment/add
POST /api/CompanyComment/delete
POST /api/CompanyComment/list
POST /api/CompanyComment/setLike
POST /api/Conversation/detail
POST /api/Conversation/sendMessage
POST /api/Google/newPlace
POST /api/Google/validatePlace
POST /api/Media/upload
POST /api/Notification/push
POST /api/Notification/send
POST /api/Notification/sendV2
POST /api/Place/addMedia
POST /api/Place/changeMeta
POST /api/Place/deleteMedia
POST /api/Place/detail
POST /api/Place/detailByCode
POST /api/Place/nearBy
POST /api/Place/notifPlace
POST /api/Place/setFavorite
POST /api/Place/suggestPlace
POST /api/PlaceComment/add
POST /api/PlaceComment/askQuestion
POST /api/PlaceComment/delete
POST /api/PlaceComment/list
POST /api/PlaceComment/setLike
POST /api/Post/add
POST /api/Post/adminLike
POST /api/Post/block
POST /api/Post/delete
POST /api/Post/search
POST /api/Post/searchByTag
POST /api/Post/setLike
POST /api/Post/timeline
POST /api/PostComment/add
POST /api/PostComment/delete
POST /api/PostComment/list
POST /api/PostComment/setLike
POST /api/PostComment/update
POST /api/Profile/changePassword
POST /api/Profile/changeProfile
POST /api/Profile/changeProfilePhoto
POST /api/Profile/delete
POST /api/Profile/follow
POST /api/Type/list
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: 5733ddf49ff49cd1aad03549dbdfbb7014bf82528068a87aa030f99552c3bb26
Public Swagger UI/API detected at path: /swagger/index.html - sample paths:
GET /api/Activity/detail
GET /api/Activity/list
GET /api/Advert/brandList
GET /api/Advert/brandModelList
GET /api/Conversation/list
GET /api/Google/searchPlace
GET /api/Location/cities/{countryId}
GET /api/Location/countries
GET /api/Media/view
GET /api/Notification/list
GET /api/Place/activityList
GET /api/Place/propertyList
GET /api/Post/hashtagList
GET /api/Profile/favoritePlace
GET /api/Profile/followList
GET /api/Profile/socialProfile
GET /api/Profile/timeline
GET /api/Type/translation
POST /api/Account/checkValue
POST /api/Account/forgotPassword
POST /api/Account/login
POST /api/Account/register
POST /api/Account/saveDevice
POST /api/Account/sendValidateCode
POST /api/Account/validationAccount
POST /api/Advert/delete
POST /api/Advert/detail
POST /api/Advert/detailByCode
POST /api/Advert/save
POST /api/Advert/search
POST /api/Campaign/detail
POST /api/Company/addMedia
POST /api/Company/changeMeta
POST /api/Company/deleteMedia
POST /api/Company/detail
POST /api/Company/detailInfo
POST /api/Company/list
POST /api/Company/register
POST /api/Company/save
POST /api/CompanyComment/add
POST /api/CompanyComment/delete
POST /api/CompanyComment/list
POST /api/CompanyComment/setLike
POST /api/Conversation/detail
POST /api/Conversation/sendMessage
POST /api/Google/newPlace
POST /api/Google/validatePlace
POST /api/Media/upload
POST /api/Notification/push
POST /api/Notification/send
POST /api/Notification/sendV2
POST /api/Place/addMedia
POST /api/Place/changeMeta
POST /api/Place/deleteMedia
POST /api/Place/detail
POST /api/Place/detailByCode
POST /api/Place/nearBy
POST /api/Place/notifPlace
POST /api/Place/setFavorite
POST /api/Place/suggestPlace
POST /api/PlaceComment/add
POST /api/PlaceComment/askQuestion
POST /api/PlaceComment/delete
POST /api/PlaceComment/list
POST /api/PlaceComment/setLike
POST /api/Post/add
POST /api/Post/adminLike
POST /api/Post/block
POST /api/Post/delete
POST /api/Post/search
POST /api/Post/searchByTag
POST /api/Post/setLike
POST /api/Post/timeline
POST /api/PostComment/add
POST /api/PostComment/delete
POST /api/PostComment/list
POST /api/PostComment/setLike
POST /api/PostComment/update
POST /api/Profile/changePassword
POST /api/Profile/changeProfile
POST /api/Profile/changeProfilePhoto
POST /api/Profile/delete
POST /api/Profile/follow
POST /api/Type/list
Open service 195.142.1.194:80 · api.vanliferoad.com
2026-01-23 09:54
HTTP/1.1 307 Temporary Redirect Transfer-Encoding: chunked Location: https://api.vanliferoad.com/ Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 09:54:26 GMT Connection: close
Open service 195.142.1.194:443 · api.vanliferoad.com
2026-01-23 09:54
HTTP/1.1 404 Not Found Transfer-Encoding: chunked Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 09:54:26 GMT Connection: close
Open service 195.142.1.194:80 · api.vanliferoad.com
2026-01-23 00:48
HTTP/1.1 307 Temporary Redirect Transfer-Encoding: chunked Location: https://api.vanliferoad.com/ Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 23 Jan 2026 00:48:58 GMT Connection: close
Open service 195.142.1.194:443 · api.vanliferoad.com
2026-01-22 20:55
HTTP/1.1 404 Not Found Transfer-Encoding: chunked Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Thu, 22 Jan 2026 20:55:15 GMT Connection: close
Open service 195.142.1.194:443 · api.vanliferoad.com
2026-01-09 01:40
HTTP/1.1 404 Not Found Transfer-Encoding: chunked Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 09 Jan 2026 01:40:44 GMT Connection: close
Open service 195.142.1.194:80 · api.vanliferoad.com
2026-01-08 23:44
HTTP/1.1 307 Temporary Redirect Transfer-Encoding: chunked Location: https://api.vanliferoad.com/ Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Thu, 08 Jan 2026 23:44:13 GMT Connection: close
Open service 195.142.1.194:80 · api.vanliferoad.com
2026-01-02 02:04
HTTP/1.1 307 Temporary Redirect Transfer-Encoding: chunked Location: https://api.vanliferoad.com/ Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Fri, 02 Jan 2026 02:04:26 GMT Connection: close
Open service 195.142.1.194:80 · api.vanliferoad.com
2025-12-23 05:59
HTTP/1.1 307 Temporary Redirect Transfer-Encoding: chunked Location: https://api.vanliferoad.com/ Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Tue, 23 Dec 2025 05:59:42 GMT Connection: close
Open service 195.142.1.194:443 · api.vanliferoad.com
2025-12-22 13:49
HTTP/1.1 404 Not Found Transfer-Encoding: chunked Server: Microsoft-IIS/10.0 X-Powered-By: ASP.NET Date: Mon, 22 Dec 2025 13:49:09 GMT Connection: close