[ Thanks to Mike
Golvach for this link. ]
“We’ve elected to have our port scan start at 80 (The
traditional http server port) and grab every other (higher)
listening port on the localhost and query all of them, as if they
were http servers, by sending a simple HTTP/1.0 GET request. As a
blanket request to any number of known, and unknown, ports, it’s
not always the best way to interrogate, but it does get lots of
useful information from any sort of web server and a few other
sorts of servers as well. The only thing you have to settle down
and be comfortable with is the fact that, a lot of the time, you
can find out just as much about what’s running on a particular port
by reading the error message you receive from a bogus query as you
can from reading the result of a successful one.”
Web Webster has more than 20 years of writing and editorial experience in the tech sector. He’s written and edited news, demand generation, user-focused, and thought leadership content for business software solutions, consumer tech, and Linux Today, he edits and writes for a portfolio of tech industry news and analysis websites including webopedia.com, and DatabaseJournal.com.
LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.
Property of TechnologyAdvice. © 2025 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.