REDbot is available as a Slack app. Read on to find out how to install and use it.
For occasional use against public URLs, you can install REDbot by following this link:
Note that this uses the public REDbot instance, and as such the traffic will be exposed to our server, and rate limited. See the privacy and use policies below.
The Slack integration keeps logs of URLs tested, to help debug the service. Debug logs contain more information (such as Slack Team ID and/or User ID) when rate limits are exceeded.
Successful tests are saved on our system for a short period of time so that they can be accessed; this can include much of the data in the HTTP responses received, as well as REDbot's configuration for the test. This information is automatically removed on a regular basis (currently, daily).
Errors (such as an exception in REDbot, or another anomalous condition) can cause additional information to be logged, to aid debugging.
We undertake not to abuse or share this information. If you are concerned about this, you should consider running your own instance of REDbot.
Please treat the public service respectfully; if you need to run hundreds of tests a day, you should probably install your own instance (see below).
This service is rate limited, both by user ID and team ID. If you hit the rate limit, you won't be able to run more tests until the next one-hour window starts.
Please do not use this service to access content that is illegal in the United States (where it is hosted), including content that violates the copyright of others. If we are made aware of such content, we will remove it as soon as is possible.
If you want to make queries more often, or if you want to run REDbot against URLs that are
private, you can run your own instance of REDbot and configure a Slack slash command to use https://{your
site}/?slack=1
. Then, set your slack_signing_secret
in config.txt
.
Once installed, you can invoke REDbot from any channel with the /httplint
command. For example:
If you believe REDbot's output is incorrect, please tell us on Twitter, or open an issue.