@httpstatusbotFree
79 / 100
Score
Checking a domain, an address or a link before you trust it - answers that arrive as a message you can forward.
| # | Bot | Price | Languages | Inline | Groups | Score |
|---|---|---|---|---|---|---|
| 1 | @httpstatusbot | Free | EN | no | no | 79 |
| 2 | @whois_bot | Free | EN | no | no | 75 |
| 3 | @ipinfo_bot | Free | EN | no | no | 74 |
| 4 | @JsonBot | Free | EN | no | no | 73 |
| 5 | @DNSCheckerBot | Free | EN | no | no | 68 |
We did not run these bots by hand; the ranking rests on what can be checked in the open. For each bot we confirmed on its t.me page that it is a live bot and read what it says it returns, then looked for a source on the owner's side, such as the service that supplies the data linking back to the bot. We noted what each answer contains, whether it needs a signup, who runs the bot and what it cannot tell you, such as a hidden domain owner or an approximate city.
Every one of these bots replaces a browser tab you would otherwise open in the middle of something else: a page behaves oddly, a link looks suspicious, a name might be free, a log line has an unfamiliar address. The answer is two lines of text, and in a chat it can be forwarded to the person who asked.
A status code tells you whether a page exists; the headers tell you why it behaves the way it does. A whois record rarely names an owner any more, but the registration date is a genuine signal - a domain created last week and a domain created in 2011 are different risks. An IP resolves to a network and a provider, not to a person, and a city is an approximation.
These tools describe infrastructure, not intent. A clean status code says nothing about whether a site is honest, and a domain with a long history can still be running a scam this month. Pair a lookup with a link-checking bot when the question is safety rather than configuration, and treat anything you forward into a bot as leaving your device.
Look at the domain's registration date and the page's status and headers; then run it through a dedicated link-checking bot for a malware verdict.
Rarely. Privacy protection hides the registrant on most domains; what you reliably get is dates, the registrar and the hosting network.
Treat it as public. Forward a test message when you only need identifiers, and keep private conversations out of any third-party bot.
