Domain api.latido.com.np
India
Software information
nginx 1.24.0
tcp/443
-
Swagger API description is publicly available
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.
First seen 2025-11-20 09:38
Last seen 2026-02-02 10:57
Open for 74 days-
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354922638863f153e4072198726a5fbe666ddc5d7bdcPublic Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /admins/ GET /admins/{id}/ GET /cart-items/ GET /cart-items/{id}/ GET /cart/ GET /cart/items/ GET /cart/items/{id}/ GET /carts/ GET /carts/{id}/ GET /categories/ GET /categories/{id}/ GET /categories/{id}/products/ GET /classifications/{id}/ GET /customers/ GET /customers/{id}/ GET /homepage/ GET /homepage/{id}/ GET /inventory-items/ GET /inventory-items/{id}/ GET /orders/ GET /orders/epg/validation/ GET /orders/payment/ GET /orders/shippingcost/ GET /orders/user/ GET /orders/{id}/ GET /presets/{id}/ GET /products/ GET /products/{id}/ GET /reviews/ GET /reviews/{id} GET /send-otp/ GET /subcategories/ GET /subcategories/{id}/ GET /subcategories/{id}/products/ GET /users/current/ GET /verify-otp/ POST /forgot-password/ POST /forgot-password/confirm/ POST /images POST /token/ POST /token/blacklist/ POST /token/refresh/ POST /wishlist/ PUT /wishlist/{id}/Found on 2026-02-02 10:57 -
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354922638863f153e4072198726a5fbe666dc0fb8f21Public Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /admins/ GET /admins/{id}/ GET /cart-items/ GET /cart-items/{id}/ GET /cart/ GET /cart/items/ GET /cart/items/{id}/ GET /carts/ GET /carts/{id}/ GET /categories/ GET /categories/{id}/ GET /categories/{id}/products/ GET /customers/ GET /customers/{id}/ GET /homepage/ GET /homepage/{id}/ GET /inventory-items/ GET /inventory-items/{id}/ GET /orders/ GET /orders/epg/validation/ GET /orders/payment/ GET /orders/shippingcost/ GET /orders/user/ GET /orders/{id}/ GET /presets/{id}/ GET /products/ GET /products/{id}/ GET /reviews/ GET /reviews/{id} GET /send-otp/ GET /subcategories/ GET /subcategories/{id}/ GET /subcategories/{id}/products/ GET /users/current/ GET /verify-otp/ POST /forgot-password/ POST /forgot-password/confirm/ POST /images POST /token/ POST /token/blacklist/ POST /token/refresh/ POST /wishlist/ PUT /wishlist/{id}/Found on 2026-01-16 19:51
-
-
Swagger API description is publicly available
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.
First seen 2025-12-22 22:15
Last seen 2026-02-01 23:02
Open for 41 days-
Severity: info
Fingerprint: 5733ddf49ff49cd1aad0354922638863f153e4072198726a5fbe666ddc5d7bdcPublic Swagger UI/API detected at path: /swagger/index.html - sample paths: GET /admins/ GET /admins/{id}/ GET /cart-items/ GET /cart-items/{id}/ GET /cart/ GET /cart/items/ GET /cart/items/{id}/ GET /carts/ GET /carts/{id}/ GET /categories/ GET /categories/{id}/ GET /categories/{id}/products/ GET /classifications/{id}/ GET /customers/ GET /customers/{id}/ GET /homepage/ GET /homepage/{id}/ GET /inventory-items/ GET /inventory-items/{id}/ GET /orders/ GET /orders/epg/validation/ GET /orders/payment/ GET /orders/shippingcost/ GET /orders/user/ GET /orders/{id}/ GET /presets/{id}/ GET /products/ GET /products/{id}/ GET /reviews/ GET /reviews/{id} GET /send-otp/ GET /subcategories/ GET /subcategories/{id}/ GET /subcategories/{id}/products/ GET /users/current/ GET /verify-otp/ POST /forgot-password/ POST /forgot-password/confirm/ POST /images POST /token/ POST /token/blacklist/ POST /token/refresh/ POST /wishlist/ PUT /wishlist/{id}/Found on 2026-02-01 23:02
-
-
Open service 43.205.63.184:443 · api.latido.com.np
2026-01-23 13:34
HTTP/1.1 404 Not Found Server: nginx/1.24.0 (Ubuntu) Date: Fri, 23 Jan 2026 13:34:18 GMT Content-Type: text/html; charset=utf-8 Content-Length: 3830 Connection: close X-Frame-Options: DENY X-Content-Type-Options: nosniff Referrer-Policy: same-origin Cross-Origin-Opener-Policy: same-origin Vary: origin Page title: Page not found at / <!DOCTYPE html> <html lang="en"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <title>Page not found at /</title> <meta name="robots" content="NONE,NOARCHIVE"> <style> html * { padding:0; margin:0; } body * { padding:10px 20px; } body * * { padding:0; } body { font-family: sans-serif; background:#eee; color:#000; } body > :where(header, main, footer) { border-bottom:1px solid #ddd; } h1 { font-weight:normal; margin-bottom:.4em; } h1 small { font-size:60%; color:#666; font-weight:normal; } table { border:none; border-collapse: collapse; width:100%; } td, th { vertical-align:top; padding:2px 3px; } th { width:12em; text-align:right; color:#666; padding-right:.5em; } #info { background:#f6f6f6; } #info ol { margin: 0.5em 4em; } #info ol li { font-family: monospace; } #summary { background: #ffc; } #explanation { background:#eee; border-bottom: 0px none; } pre.exception_value { font-family: sans-serif; color: #575757; font-size: 1.5em; margin: 10px 0 10px 0; } </style> </head> <body> <header id="summary"> <h1>Page not found <small>(404)</small></h1> <table class="meta"> <tr> <th scope="row">Request Method:</th> <td>GET</td> </tr> <tr> <th scope="row">Request URL:</th> <td>http://api.latido.com.np/</td> </tr> </table> </header> <main id="info"> <p> Using the URLconf defined in <code>config.urls</code>, Django tried these URL patterns, in this order: </p> <ol> <li> <code> admin/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> swagger/ [name='schema-swagger-ui'] </code> </li> <li> <code> redoc/ [name='schema-redoc'] </code> </li> </ol> <p> The empty path didn’t match any of these. </p> </main> <footer id="explanation"> <p> You’re seeing this error because you have <code>DEBUG = True</code> in your Django settings file. Change that to <code>False</code>, and Django will display a standard 404 page. </p> </footer> </body> </html>Found 2026-01-23 by HttpPluginCreate report
-
Open service 13.203.124.122:443 · uat.api.latido.com.np
2026-01-22 20:41
HTTP/1.1 404 Not Found Server: nginx/1.24.0 (Ubuntu) Date: Thu, 22 Jan 2026 20:41:25 GMT Content-Type: text/html; charset=utf-8 Content-Length: 3834 Connection: close X-Frame-Options: DENY X-Content-Type-Options: nosniff Referrer-Policy: same-origin Cross-Origin-Opener-Policy: same-origin Vary: origin Page title: Page not found at / <!DOCTYPE html> <html lang="en"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <title>Page not found at /</title> <meta name="robots" content="NONE,NOARCHIVE"> <style> html * { padding:0; margin:0; } body * { padding:10px 20px; } body * * { padding:0; } body { font-family: sans-serif; background:#eee; color:#000; } body > :where(header, main, footer) { border-bottom:1px solid #ddd; } h1 { font-weight:normal; margin-bottom:.4em; } h1 small { font-size:60%; color:#666; font-weight:normal; } table { border:none; border-collapse: collapse; width:100%; } td, th { vertical-align:top; padding:2px 3px; } th { width:12em; text-align:right; color:#666; padding-right:.5em; } #info { background:#f6f6f6; } #info ol { margin: 0.5em 4em; } #info ol li { font-family: monospace; } #summary { background: #ffc; } #explanation { background:#eee; border-bottom: 0px none; } pre.exception_value { font-family: sans-serif; color: #575757; font-size: 1.5em; margin: 10px 0 10px 0; } </style> </head> <body> <header id="summary"> <h1>Page not found <small>(404)</small></h1> <table class="meta"> <tr> <th scope="row">Request Method:</th> <td>GET</td> </tr> <tr> <th scope="row">Request URL:</th> <td>http://uat.api.latido.com.np/</td> </tr> </table> </header> <main id="info"> <p> Using the URLconf defined in <code>config.urls</code>, Django tried these URL patterns, in this order: </p> <ol> <li> <code> admin/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> api/ </code> </li> <li> <code> swagger/ [name='schema-swagger-ui'] </code> </li> <li> <code> redoc/ [name='schema-redoc'] </code> </li> </ol> <p> The empty path didn’t match any of these. </p> </main> <footer id="explanation"> <p> You’re seeing this error because you have <code>DEBUG = True</code> in your Django settings file. Change that to <code>False</code>, and Django will display a standard 404 page. </p> </footer> </body> </html>Found 2026-01-22 by HttpPluginCreate report
-
Open service 43.205.63.184:443 · api.latido.com.np
2026-01-10 01:39
HTTP/1.1 404 Not Found Server: nginx/1.24.0 (Ubuntu) Date: Sat, 10 Jan 2026 01:39:15 GMT Content-Type: text/html; charset=utf-8 Content-Length: 179 Connection: close X-Frame-Options: DENY X-Content-Type-Options: nosniff Referrer-Policy: same-origin Cross-Origin-Opener-Policy: same-origin Vary: origin Page title: Not Found <!doctype html> <html lang="en"> <head> <title>Not Found</title> </head> <body> <h1>Not Found</h1><p>The requested resource was not found on this server.</p> </body> </html>
Found 2026-01-10 by HttpPluginCreate report