- Banner
- 220 (vsFTPd 3.0.3)
Raw response
220 (vsFTPd 3.0.3)
Host
As of our latest check on 2026-10-23, 195.130.205.22 (JSC BALTICOM, AS24651, Latvia) had 3 open ports (21, 80, 443) and 2 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-10-23.
CVEs by severity: HIGH 2
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: 109 on a distribution build — the fix may be backported (http_server 2.4.29). See them
Not counted: 4 only affect another platform (http_server 2.4.29). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 (vsFTPd 3.0.3)
HTTP/1.1 200 OK
Date: Fri, 23 Oct 2026 01:21:51 GMT
Server: Apache/2.4.29 (Ubuntu)
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 542
Content-Type: text/html; charset=UTF-8
�}RQo�0~^~�͓�4b���I&
��D��S�*c��ؑ}-e�~N´�eyH���r�}�e'�q��(ᦺ����z6�q��b����t�˴�yy�`;�z���pH��[^-������ZR�H�"ɚ�"��ݔ�I���լ,������U�|(��N��wײ����H�$#�6�h���}k����P�1�PJ�mξt8�B�8�I�������@���zP�t�� A�\���!��j�!�|�ؓn�G/�U ��h���0�d^�����!m%�{����͙�E���0��Y�^�t�#G�7�?ū�N/�V�U(LJ-�4v�[�5�oqz�b���6�SCgb_�����
�����My���j��H��������M���w���j�'ѓ�4�`���#ٜ=�#��8K�3�>��g��=���Vρu��
K��3
������
���...<truncated>
HTTP/1.1 400 Bad Request Date: Fri, 23 Oct 2026 01:21:51 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 444 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <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> <hr> <address>Apache/2.4.29 (Ubuntu) Server at payment.avio.lv Port 443</address> </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. 3 of them are known to be exploited.
CVEs by severity: CRITICAL 23 HIGH 56 MEDIUM 29 LOW 1
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.29 · port 80 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.4.29 · port 80 |
| CVE-2019-0211 HIGH 7.8 known exploited | http_server 2.4.29 · port 80 |
| CVE-2018-1312 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.29 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.29 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.29 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.29 · port 80 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.29 · port 80 |
| CVE-2017-15715 HIGH 8.1 | http_server 2.4.29 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.29 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.29 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2017-15710 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2018-1333 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2018-17199 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2019-10081 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2019-9517 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-11993 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-9490 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.29 · port 80 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.29 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.29 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.29 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.29 · port 80 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2018-11763 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.29 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.29 · port 80 |
| CVE-2018-1283 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2018-17189 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.29 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.29 · port 80 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.29 · port 80 |
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 2
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4.29 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
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.
1 name · as answered by each domain's own name servers