- Banner
- 220 Welcome! Please note that all activity is logged.
Raw response
220 Welcome! Please note that all activity is logged.
Host
As of our latest check on 2026-09-10, 115.42.220.28 (SingNet, AS3758, Singapore) had 6 open ports (21, 22, 80, 443, 8080, 8443) and 38 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-09-10.
CVEs by severity: CRITICAL 3 HIGH 10 MEDIUM 14 LOW 11
A match is an indication, not proof: it is based on the software version a service reported, and fixes are often backported without changing the version. See the list
Not counted: 122 on a distribution build — the fix may be backported (openssl 3.0.2, http_server 2.4.66). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 Welcome! Please note that all activity is logged.
SSH-2.0-OpenSSH_8.9p1
HTTP/1.1 200 OK
Server: nginx
Date: Thu, 10 Sep 2026 15:09:56 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 1062
Connection: keep-alive
Last-Modified: Mon, 21 Apr 2025 04:34:34 GMT
ETag: "9d8-63342628e4b27-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
��Vߏ�6~��sT'�RL0�E8��ݩUO��C�>����582N�lu�{m0�=�2�g��=������rd��B<�Il�����J���$�IM?I
� М����w��<�]U%)��;sV��PYjVӚ�:ߦ��)C�d
����*J��Α�Z��݉RVUo�Y;��J_��d/��cG�=�O%Oe��R��C����F]u�%��C���uv��>�,3���\\�F0A�xU�J�b
/� �5�_���;H~�����K-��7&�LsJ�;1����.��S��1�)+��L�*�xf`�j�Ɇ��o�
��"�]������nK�g������!8>vM���p�������O�P�@M�j����w���7�V�C�/���e��!�1�����.�...<truncated>
HTTP/1.1 400 Bad Request Server: nginx Date: Thu, 10 Sep 2026 15:09:56 GMT Content-Type: text/html; charset=utf-8 Content-Length: 650 Connection: close <html> <head><title>400 The plain HTTP request was sent to HTTPS port</title></head> <body> <center><h1>400 Bad Request</h1></center> <center>The plain HTTP request was sent to HTTPS port</center> <hr><center>nginx</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
HTTP/1.1 200 OK
Date: Thu, 10 Sep 2026 15:09:56 GMT
Server: Apache/2.4.66 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/3.0.2
Last-Modified: Mon, 21 Apr 2025 04:34:34 GMT
ETag: "9d8-63342628e4b27-gzip"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 1062
Connection: close
Content-Type: text/html
��Vߏ�6~��sT'�RL0�E8��ݩUO��C�>����582N�lu�{m0�=�2�g��=������rd��B<�Il�����J���$�IM?I
� М����w��<�]U%)��;sV��PYjVӚ�:ߦ��)C�d
����*J��Α�Z��݉RVUo�Y;��J_��d/��cG�=�O%Oe��R��C����F]u�%��C���uv��>�,3���\\�F0A�xU�J�b
/� �5�_���;H~�����K-��7&�LsJ�;1����.��S��1�)+��L�*�xf`�j�Ɇ��o�
��"�]������nK�g������!8>vM���p�������O�P�@M�j����w���7�V�C�/���e�...<truncated>
HTTP/1.1 400 Bad Request Date: Thu, 10 Sep 2026 15:09:56 GMT Server: Apache/2.4.66 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/3.0.2 Content-Length: 402 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> Reason: You're speaking plain HTTP to an SSL-enabled server port.<br /> Instead use the HTTPS scheme to access this URL, please.<br /> </p> </body></html>
These CVEs were matched on software built by an operating-system distribution whose package revision the service does not show. Distributions often fix a flaw without changing the upstream version number, so whether this build is affected cannot be told from its version. They are not counted.
CVEs by severity: CRITICAL 16 HIGH 60 MEDIUM 42 LOW 4
| CVE | Software |
|---|---|
| CVE-2022-1292 CRITICAL 10.0 | openssl 3.0.2 · port 8080 |
| CVE-2022-2068 CRITICAL 10.0 | openssl 3.0.2 · port 8080 |
| CVE-2024-4741 CRITICAL 9.8 | openssl 3.0.2 · port 8080 |
| CVE-2025-15467 CRITICAL 9.8 | openssl 3.0.2 · port 8080 |
| CVE-2025-9230 CRITICAL 9.8 | openssl 3.0.2 · port 8080 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-31789 CRITICAL 9.8 | openssl 3.0.2 · port 8080 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.66 · port 8080 |
| CVE-2024-5535 CRITICAL 9.1 | openssl 3.0.2 · port 8080 |
| CVE-2026-34182 CRITICAL 9.1 | openssl 3.0.2 · port 8080 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.66 · port 8080 |
| CVE-2026-75803 CRITICAL 9.1 | openssl 3.0.2 · port 8080 |
| CVE-2024-9143 HIGH 8.8 | openssl 3.0.2 · port 8080 |
| CVE-2026-23918 HIGH 8.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-45447 HIGH 8.8 | openssl 3.0.2 · port 8080 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-84782 HIGH 8.2 | openssl 3.0.2 · port 8080 |
| CVE-2026-119618 HIGH 8.1 | http_server 2.4.66 · port 8080 |
| CVE-2026-28387 HIGH 8.1 | openssl 3.0.2 · port 8080 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.66 · port 8080 |
| CVE-2026-7383 HIGH 8.1 | openssl 3.0.2 · port 8080 |
| CVE-2023-4807 HIGH 7.8 | openssl 3.0.2 · port 8080 |
| CVE-2026-107493 HIGH 7.7 | openssl 3.0.2 · port 8080 |
| CVE-2022-1473 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2022-3358 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2022-3602 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2022-3786 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2022-3996 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2022-4450 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-0215 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-0216 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-0217 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-0401 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-0464 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-5363 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2024-6119 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2025-69420 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2025-69421 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-28388 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-28389 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-28390 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-31790 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-34180 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-45445 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-54874 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-63072 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-63076 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-9076 HIGH 7.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-0286 HIGH 7.4 | openssl 3.0.2 · port 8080 |
| CVE-2025-69419 HIGH 7.4 | openssl 3.0.2 · port 8080 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.66 · port 8080 |
| CVE-2023-2650 MEDIUM 6.5 | openssl 3.0.2 · port 8080 |
| CVE-2023-6129 MEDIUM 6.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.66 · port 8080 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.66 · port 8080 |
| CVE-2022-1434 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2022-4304 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2023-1255 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2023-6237 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2024-2511 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2025-9231 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2025-9232 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2026-42766 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2026-42767 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2026-63074 MEDIUM 5.9 | openssl 3.0.2 · port 8080 |
| CVE-2024-0727 MEDIUM 5.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-22795 MEDIUM 5.5 | openssl 3.0.2 · port 8080 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.66 · port 8080 |
| CVE-2022-1343 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2022-2097 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2023-0465 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2023-0466 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2023-2975 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2023-3817 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2023-5678 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2024-4603 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2026-22796 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-35189 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.66 · port 8080 |
| CVE-2026-75805 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2026-75806 MEDIUM 5.3 | openssl 3.0.2 · port 8080 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.66 · port 8080 |
| CVE-2022-4203 MEDIUM 4.9 | openssl 3.0.2 · port 8080 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.66 · port 8080 |
| CVE-2026-45446 MEDIUM 4.8 | openssl 3.0.2 · port 8080 |
| CVE-2025-68160 MEDIUM 4.7 | openssl 3.0.2 · port 8080 |
| CVE-2024-13176 MEDIUM 4.6 | openssl 3.0.2 · port 8080 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.66 · port 8080 |
| CVE-2025-69418 MEDIUM 4.0 | openssl 3.0.2 · port 8080 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.66 · port 8080 |
| CVE-2026-42770 LOW 3.7 | openssl 3.0.2 · port 8080 |
| CVE-2026-54872 LOW 3.7 | openssl 3.0.2 · port 8080 |
| CVE-2026-77696 LOW 3.7 | openssl 3.0.2 · port 8080 |
Every port that has answered a connection on this address, and when. A port is listed as open above only when a service was identified on it. Times are UTC.
12 names · as answered by each domain's own name servers