- Banner
- 220 ProFTPD Server (Debian) [::ffff:65.49.60.183]
Raw response
220 ProFTPD Server (Debian) [::ffff:65.49.60.183]
Host
As of our latest check on 2026-07-17, 65.49.60.183 (ServerOptima, AS401742, United States) had 3 open ports (21, 25, 8080) and 19 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-07-17.
CVEs by severity: CRITICAL 3 HIGH 12 MEDIUM 3 LOW 1
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: 83 on a distribution build — the fix may be backported (http_server 2.4.52, exim 4.95). See them
Not counted: 3 only affect another platform (http_server 2.4.52). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 ProFTPD Server (Debian) [::ffff:65.49.60.183]
220 peaprojetos.local ESMTP Exim 4.95 Ubuntu Fri, 17 Jul 2026 14:34:49 -0300 500 unrecognized command 500 unrecognized command 500 unrecognized command 500 Too many unrecognized commands
HTTP/1.1 200 OK Date: Fri, 17 Jul 2026 17:34:49 GMT Server: Apache/2.4.52 (Ubuntu) Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 334 Content-Type: text/html;charset=UTF-8 ���]K�0���+^s���7��l'��/�6]�mR�l��ެ��.���s99�"\���7�����i��� �����y]x��爓a-��"g-������Zis��*��S@�͉c��H'Gm�綵�j��4��<�;��K¨,vP��'(c�*�r��L ����e,_�6;������.��K?$l�A����3&l�+�Nd*Er^7�Z~�7&Uldi�V�(��?��:�J��\����rc��'�U��%�3�]�� �p������`-�A���� �^gԃ�6Fm��9�u�~꪿bYe6*
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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 22 HIGH 39 MEDIUM 20 LOW 2
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.52 · port 8080 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2022-3620 CRITICAL 9.8 | exim 4.95 · port 25 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2023-42115 CRITICAL 9.8 | exim 4.95 · port 25 |
| CVE-2023-42116 CRITICAL 9.8 | exim 4.95 · port 25 |
| CVE-2023-42117 CRITICAL 9.8 | exim 4.95 · port 25 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2025-67896 CRITICAL 9.8 | exim 4.95 · port 25 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2026-40685 CRITICAL 9.8 | exim 4.95 · port 25 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.52 · port 8080 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.52 · port 8080 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.52 · port 8080 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.52 · port 8080 |
| CVE-2026-40687 CRITICAL 9.1 | exim 4.95 · port 25 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.52 · port 8080 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.52 · port 8080 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.52 · port 8080 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.52 · port 8080 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.52 · port 8080 |
| CVE-2026-66140 HIGH 7.8 | exim 4.95 · port 25 |
| CVE-2026-66141 HIGH 7.8 | exim 4.95 · port 25 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2022-3559 HIGH 7.5 | exim 4.95 · port 25 |
| CVE-2022-37451 HIGH 7.5 | exim 4.95 · port 25 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-40684 HIGH 7.5 | exim 4.95 · port 25 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-94056 HIGH 7.5 | exim 4.95 · port 25 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.52 · port 8080 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-94054 HIGH 7.0 | exim 4.95 · port 25 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.52 · port 8080 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.52 · port 8080 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.52 · port 8080 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-39929 MEDIUM 5.4 | exim 4.95 · port 25 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.52 · port 8080 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.52 · port 8080 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.52 · port 8080 |
| CVE-2023-42114 MEDIUM 5.3 | exim 4.95 · port 25 |
| CVE-2023-51766 MEDIUM 5.3 | exim 4.95 · port 25 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.52 · port 8080 |
| CVE-2026-40686 MEDIUM 5.3 | exim 4.95 · port 25 |
| CVE-2026-48840 MEDIUM 5.3 | exim 4.95 · port 25 |
| CVE-2026-94057 MEDIUM 5.3 | exim 4.95 · port 25 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.52 · port 8080 |
| CVE-2026-94055 LOW 3.7 | exim 4.95 · port 25 |
| CVE-2023-42119 LOW 3.1 | exim 4.95 · port 25 |
These CVEs need a platform this host visibly does not run (for example a flaw of the Windows build on a Linux host). They are not counted.
CVEs by severity: HIGH 2 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.52 · port 8080 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.52 · 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.
2 names · as answered by each domain's own name servers