nginx

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Sat, 25 Jan 2025 09:06:58 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://103.153.241.10:443/

Portmap
Program	Version	Protocol	Port
portmapper	4	tcp	111
portmapper	3	tcp	111
portmapper	2	tcp	111
portmapper	4	udp	111
portmapper	3	udp	111
portmapper	2	udp	111
portmapper	4	7	111
portmapper	3	7	111
portmapper	2	7	111
mountd	1	udp	612
mountd	3	udp	612
mountd	1	tcp	612
mountd	3	tcp	612
nfs	2	tcp	2049
nfs	3	tcp	2049
status	1	udp	667
status	1	tcp	667
nlockmgr	0	udp	929
nlockmgr	0	tcp	884
nlockmgr	1	udp	929
nlockmgr	1	tcp	884
nlockmgr	3	udp	929
nlockmgr	3	tcp	884
nlockmgr	4	udp	929
nlockmgr	4	tcp	884

Portmap
Program	Version	Protocol	Port
portmapper	4	tcp	111
portmapper	3	tcp	111
portmapper	2	tcp	111
portmapper	4	udp	111
portmapper	3	udp	111
portmapper	2	udp	111
portmapper	4	7	111
portmapper	3	7	111
portmapper	2	7	111
mountd	1	udp	612
mountd	3	udp	612
mountd	1	tcp	612
mountd	3	tcp	612
nfs	2	tcp	2049
nfs	3	tcp	2049
status	1	udp	667
status	1	tcp	667
nlockmgr	0	udp	929
nlockmgr	0	tcp	884
nlockmgr	1	udp	929
nlockmgr	1	tcp	884
nlockmgr	3	udp	929
nlockmgr	3	tcp	884
nlockmgr	4	udp	929
nlockmgr	4	tcp	884

nginx

HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Thu, 20 Feb 2025 05:20:33 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: oc_sessionPassphrase=vZTyJ767WTA93WTtrDTNZMtdRd%2BxoQxLz4haTpnT7nkSLtjyefFJtiSvq%2Bn7gy8Jw0eGAY%2FZIj1DF%2Bz8UDw07ZNWp9IZPG6ahXubZetS0QBb7b10EH9JAyik3hT4UzzW; path=/; secure; HttpOnly; SameSite=Lax
Content-Security-Policy: default-src 'self'; script-src 'self' 'nonce-UlBTbDVTaGY3VjB1ZDJGZXBFU0t6VW5pWHk5TklrR20wUi85V0htekxNcz06QVp6QmwySWNsR1JiUmhzbzZDYnlwUUs2Q25zbFJRcndsU2EzY3orY0ZZYz0='; style-src 'self' 'unsafe-inline'; frame-src *; img-src * data: blob:; font-src 'self' data:; media-src *; connect-src *; object-src 'none'; base-uri 'self';
Set-Cookie: __Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax
Set-Cookie: __Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict
Set-Cookie: oc1fl4l6eoex=947dbe3dd9feaccf0c9b7219a1218907; path=/; secure; HttpOnly; SameSite=Lax
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Strict-Transport-Security: max-age=15768000; includeSubDomains;
Referrer-Policy: no-referrer
X-Content-Type-Options: nosniff
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Robots-Tag: none
X-XSS-Protection: 1; mode=block

SMB Status:
  Authentication: enabled
  SMB Version: 2
  Capabilities: raw-mode

MySQL8.0.35

MySQL:
  Protocol Version: 10
  Version: 8.0.35
  Capabilities: 65535
  Server Language: 255
  Server Status: 2
  Extended Server Capabilities: 57343
  Authentication Plugin: caching_sha2_password

HTTP/1.0 501 Unsupported method ('GET')
Server: BaseHTTP/0.6 Python/3.9.16
Date: Tue, 11 Feb 2025 00:21:01 GMT
Connection: close
Content-Type: text/html;charset=utf-8
Content-Length: 496

HTTP/1.0 400 Bad Request
Content-Type: text/plain; charset=utf-8
Content-Length: 37
Date: Sat, 08 Feb 2025 01:11:20 GMT
Server: Python/3.9 aiohttp/3.7.4.post0

Bad status line 'invalid HTTP method'

-DENIED Redis is running in protected mode because protected mode is enabled and no password is set for the default user. In this mode connections are only accepted from the loopback interface. If you want to connect from external computers to Redis you may adopt one of the following solutions: 1) Just disable protected mode sending the command 'CONFIG SET protected-mode no' from the loopback interface by connecting to Redis from the same host the server is running, however MAKE SURE Redis is not publicly accessible from internet if you do so. Use CONFIG REWRITE to make this change permanent. 2) Alternatively you can just disable the protected mode by editing the Redis configuration file, and setting the protected mode option to 'no', and then restarting the server. 3) If you started the server manually just for testing, restart it with the '--protected-mode no' option. 4) Set up an authentication password for the default user. NOTE: You only need to do one of the above things in order for the server to start accepting connections from the outside.

MySQL X Protocol

MySQL X Protocol:
  tls: False
  authentication.mechanisms:
    MYSQL41
    SHA256_MEMORY
  doc.formats: text
  client.interactive: False
  compression:
    algorithm:
      deflate_stream
      lz4_message
      zstd_stream
  node_type: mysql
  client.pwd_expire_ok: False