4 ms·

It is on every system, kinda (well curl usually is): ~ $ curl -v telnet://1.1.1.1:443 * Trying 1.1.1.1:443... * Connected to 1.1.1.1 (1.1.1.1) port 443 --

It is on every system, kinda (well curl usually is): ~ $ curl -v telnet://1.1.1.1:443 * Trying 1.1.1.1:443... * Connected to 1.1.1.1 (1.1.1.1) port 443 -- ~ $ curl -v telnet://1.1.1.1:22 * Trying 1.1.1.1:22... ^C ~ $

abalashov 1y ago
I didn't know curl could do that. Something new every day... thanks! Having said that, in the world of my customers' systems, neither telnet nor curl can be presumed, it seems.
- indigodaddy 1y ago
  Me either until a few years ago. My mind was well blown!
- indigodaddy 1y ago
  Introduces more ambiguity in terms of replies, but you could also just use curl straight up: ~ $ curl -v 1.1.1.1:53 * Trying 1.1.1.1:53... * Connected to 1.1.1.1 (1.1.1.1) port 53 * using HTTP/1.x > GET / HTTP/1.1 > Host: 1.1.1.1:53 > User-Agent: curl/8.13.0 > Accept: / > * Request completely sent off * Empty reply from server * shutting down connection #0 curl: (52) Empty reply from server -- ~ $ curl -v 1.1.1.1:22 * Trying 1.1.1.1:22... ^C
em500 1y ago
Curl is not installed by default on Debian or Ubuntu. And if you need to apt install you might as well just apt telnet.
- indigodaddy 1y ago
  Your secops team might disagree