Tell me, please, is it possible to somehow make it so that port 80 seems to be closed during checks, but can it accept http requests?

Closed due to the fact that the question is too general for the participants cheops , dirkgntly , Vartlok , user207618, Grundy Aug 12 '16 at 11:00 .

Please correct the question so that it describes the specific problem with sufficient detail to determine the appropriate answer. Do not ask a few questions at once. See “How to ask a good question?” For clarification. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • It seems to be closed if, when connecting to it, a connection is denied or the host is simply not located. To serve HTTP requests, connections need to be accepted. I have the impression that you are solving some related problem with very strange means. - D-side
  • @ D-side Yes, I do not decide anything. A friend created a website on VPS in reg.ru, and asked me to look for possible holes in it. I scanned the ports and noticed that port 80 is closed. But this is if you get access to the port by IP. If the domain, then everything is fine. - JamesJGoodwin
  • @JamesJGoodwin, how did you scan port 80? - aleksandr barakin 6:55 pm
  • @ D-side with nmap. - JamesJGoodwin
  • @ D-side detailed report nmap showed that port 80 has filtered status. - JamesJGoodwin 7:42 pm

1 answer 1

You can make at the level of IPtables (linux firewall) pass packets through port 80 only with a specific User-Agent. Next, change the User-Agent from your browser to the specified one.

  • But then it will work only for me. But what about the other users? They will have another UserAgent. - JamesJGoodwin
  • The question was not correctly posed. Should a restriction be set to a specific site that is located on the server? - Sequent