You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have looked into related issue, where a proposal was mentioned. However, this proposal only allows for closing connection passive. It controls the closing of connections through timeouts or max connections, whereas the 444 status code in nginx can be controlled by the upstream.
The text was updated successfully, but these errors were encountered:
I think what they are trying to achieve is closing the connection without a response
the use case (at least for me) would not return any response if a scanner tries to connect to subdomain "random.domain.tld", like when you connect to https://paudg.box/ (random domain i just typed that doesn't exist)
with logging etc this would allow banning anyone trying to find which services are present (like when using wildcard certificates I think)
useful to preemptively ban generic subdomain scanning
Welcome!
What did you expect to see?
I have looked into related issue, where a proposal was mentioned. However, this proposal only allows for closing connection passive. It controls the closing of connections through timeouts or max connections, whereas the 444 status code in nginx can be controlled by the upstream.
The text was updated successfully, but these errors were encountered: