chore: add notices about WAFs and CAPTCHA

Author: azasypkin

docs/guides/web_scraping/content.md

@@ -7,6 +7,10 @@ sidebar_label: Content Trackers
 
 The web page content tracker is a utility that empowers developers to detect and monitor the content of any web page. Alongside [web page resources trackers](./resources.md), it falls under the category of [synthetic monitoring](https://en.wikipedia.org/wiki/Synthetic_monitoring) tools. However, it extends its capabilities to cover a broader set of use cases. These range from ensuring that the deployed application loads only the intended content throughout its lifecycle to tracking changes in arbitrary web content when the application lacks native tracking capabilities. In the event of a change, whether it's caused by a broken deployment or a legitimate content modification, the tracker promptly notifies the user.
 
+:::caution NOTE
+Currently, Secutils.dev doesn't support tracking content for web pages protected by application firewalls (WAF) or any form of CAPTCHA. If you require tracking content for such pages, please comment on [#secutils/34](https://github.com/secutils-dev/secutils/issues/34) to discuss your use case.
+:::
+
 On this page, you can find guides on creating and using web page content trackers.
 
 :::note
@@ -213,6 +217,10 @@ console.log(foo(5));
 ### Track API response
 You can use content tracker to track API responses as well (until dedicated [`API tracker` utility](https://github.com/secutils-dev/secutils/issues/32) is released). For instance, you can track the response of the [JSONPlaceholder](https://jsonplaceholder.typicode.com/) API:
 
+:::caution NOTE
+Ensure that the web page from which you're making a fetch request allows cross-origin requests. Otherwise, you'll get an error.
+:::
+
 ```javascript
 const { url, method, headers, body } = {
     url: 'https://jsonplaceholder.typicode.com/posts',

docs/guides/web_scraping/resources.md

@@ -9,6 +9,10 @@ The web page resources tracker is a utility that gives developers the ability to
 
 Additionally, security researchers focused on discovering potential security vulnerabilities in third-party web applications can use web page resources trackers. By being notified when the application's resources change, researchers can identify if the application has been upgraded, providing an opportunity to re-examine the application and potentially discover new vulnerabilities.
 
+:::caution NOTE
+Currently, Secutils.dev doesn't support tracking resources for web pages protected by application firewalls (WAF) or any form of CAPTCHA. If you require tracking resources for such pages, please comment on [#secutils/34](https://github.com/secutils-dev/secutils/issues/34) to discuss your use case.
+:::
+
 On this page, you can find guides on creating and using web page resources trackers.
 
 ## Create a web page resources tracker
@@ -307,7 +311,7 @@ Demo
 <td><b>URL</b></td>
 <td>
 ```
-https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/track-me.html
+https://[YOUR UNIQUE ID].webhooks.secutils.dev/track-me.html
 ```
 </td>
 </tr>
@@ -342,9 +346,9 @@ Configured tracker will fetch the resources of the `track-me.html` responder onc
 <table class="su-table">
 <tbody>
 <tr><th>Source</th><th>Diff</th><th>Type</th><th>Size</th></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/no-change.js`</td><td>-</td><td>Script</td><td>81</td></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/changed.js`</td><td>-</td><td>Script</td><td>91</td></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/removed.js`</td><td>-</td><td>Script</td><td>78</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/no-change.js`</td><td>-</td><td>Script</td><td>81</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/changed.js`</td><td>-</td><td>Script</td><td>91</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/removed.js`</td><td>-</td><td>Script</td><td>78</td></tr>
 </tbody>
 </table>
 
@@ -389,10 +393,10 @@ Normally, Secutils.dev caches web page resources for **10 minutes**. This means
 <table class="su-table">
 <tbody>
 <tr><th>Source</th><th>Diff</th><th>Type</th><th>Size</th></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/no-change.js`</td><td><b>-</b></td><td>Script</td><td>81</td></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/changed.js`</td><td><b>Changed</b></td><td>Script</td><td>91</td></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/added.js`</td><td><b>Added</b></td><td>Script</td><td>76</td></tr>
-<tr><td>`https://[YOUR UNIQUE ID].webhooks.dev.secutils.dev/removed.js`</td><td><b>Removed</b></td><td>Script</td><td>78</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/no-change.js`</td><td><b>-</b></td><td>Script</td><td>81</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/changed.js`</td><td><b>Changed</b></td><td>Script</td><td>91</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/added.js`</td><td><b>Added</b></td><td>Script</td><td>76</td></tr>
+<tr><td>`https://[YOUR UNIQUE ID].webhooks.secutils.dev/removed.js`</td><td><b>Removed</b></td><td>Script</td><td>78</td></tr>
 </tbody>
 </table>
 

docs/guides/web_security/csp.md

@@ -1,6 +1,6 @@
 ---
 sidebar_position: 1
-sidebar_label: Content Security Policy
+sidebar_label: Content Security Policies
 ---
 
 # What is a Content Security Policy?
@@ -260,7 +260,7 @@ CSP Test
 9. Once the policy is set up, it will appear in the policies grid
 10. Click the policy's **Copy policy** button and use **Policy source** dropdown to switch to **HTML meta tag** policy representation
 11. Copy `<meta>` HTML tag with the policy and navigate to [Webhooks → Responders](https://secutils.dev/ws/webhooks__responders) again
-12. Edit **Body** property of the previously created **csp-test** responder to include `<meta>` HTML tag with the policy inside `<head>` HTML tag
+12. Edit **Body** property of the previously created **CSP Test** responder to include `<meta>` HTML tag with the policy inside `<head>` HTML tag
 13. Click the **Save** button and navigate to the responder's URL again
 14. This time, when you click the **Eval** button, nothing happens and an error message is logged in the browser console meaning that you have successfully forbidden **eval()** with the Content Security Policy