User Agent¶
HTTP checks that are carried out by Argus always contain a User-Agent header. This header is being used for HTTP requests to identify the nature and kind of the browser (or bot) that is making a request to a website. Usually, this user agent string contains information about the browser's version and some websites may deliver different content to requesting instances, depending on this user agent.
While that's generally a bad idea, because the User-Agent header can just be set to any value and therefore neither offers any form of security nor certainty, please take note of the structure of the User-Agent header, Argus is always adding to monitoring HTTP requests.
This user agent string follows the conventions of RFC 9110. The value XXX equals the version of the rescaled Argus monitoring agent which is a proprietary piece of software running on our monitoring servers to send the actual monitoring requests out to the monitoring targets and the value YYY is a unique identifier of a certain monitor so we can trace back which request was made for which monitor for debugging and abuse processing purposes.
Reporting Abuse¶
If you're seeing requests in your web server log that contain the User-Agent header described above and don't have configured Argus to carry out these checks and don't want these checks to continuously make requests to your infrastructure, please reach out to us.
Please provide the full User-Agent header content for us to investigate.