- Banner
- 220 (vsFTPd 3.0.5)
Raw response
220 (vsFTPd 3.0.5)
Host
Tags: Hosting Database Expired certificate
As of our latest check on 2026-07-24, 69.161.221.211 (LEASEWEB SINGAPORE PTE. LTD., AS59253, Singapore) had 4 open ports (21, 22, 443, 3306) and 105 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-07-24.
CVEs by severity: CRITICAL 1 HIGH 3 MEDIUM 94 LOW 7
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: 106 on a distribution build — the fix may be backported (mysql 8.0.36, openssh 8.2p1). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 (vsFTPd 3.0.5)
SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
HTTP/1.1 400 Bad Request Server: nginx/1.18.0 (Ubuntu) Date: Fri, 24 Jul 2026 07:29:45 GMT Content-Type: text/html Content-Length: 666 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/1.18.0 (Ubuntu)</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 -->
[ 8.0.36-0ubuntu0.20.04.1lPD2mXK�����EcA`n6"Zc:acaching_sha2_password
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: HIGH 9 MEDIUM 78 LOW 19
| CVE | Software |
|---|---|
| CVE-2026-35385 HIGH 8.1 | openssh 8.2p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.2p1 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 8.2p1 · port 22 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.2p1 · port 22 |
| CVE-2020-12062 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.2p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 8.2p1 · port 22 |
| CVE-2025-50076 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2025-50078 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2025-50082 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2025-50083 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-21968 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-22009 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-22017 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-34270 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-34271 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-34276 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-34303 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-34308 MEDIUM 6.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.2p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 8.2p1 · port 22 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 8.2p1 · port 22 |
| CVE-2026-34318 MEDIUM 5.8 | mysql 8.0.36 · port 3306 |
| CVE-2025-50085 MEDIUM 5.5 | mysql 8.0.36 · port 3306 |
| CVE-2025-53053 MEDIUM 5.5 | mysql 8.0.36 · port 3306 |
| CVE-2025-53054 MEDIUM 5.5 | mysql 8.0.36 · port 3306 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.2p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.2p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.2p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.2p1 · port 22 |
| CVE-2024-21176 MEDIUM 5.3 | mysql 8.0.36 · port 3306 |
| CVE-2024-21238 MEDIUM 5.3 | mysql 8.0.36 · port 3306 |
| CVE-2026-34317 MEDIUM 5.0 | mysql 8.0.36 · port 3306 |
| CVE-2026-34319 MEDIUM 5.0 | mysql 8.0.36 · port 3306 |
| CVE-2024-21203 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2024-21218 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-21531 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-21543 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50077 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50079 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50080 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50084 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50086 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50087 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50088 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50091 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50092 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50093 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50097 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50099 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50101 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-50102 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53023 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53040 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53042 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53044 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53045 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53062 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2025-53069 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-21936 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-21937 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-21941 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-21948 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-21964 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-21998 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-22002 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-22004 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-22005 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-34267 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-34278 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-34293 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-34304 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-35236 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-35237 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-35238 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-35239 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-35240 MEDIUM 4.9 | mysql 8.0.36 · port 3306 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.2p1 · port 22 |
| CVE-2025-50096 MEDIUM 4.4 | mysql 8.0.36 · port 3306 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 8.2p1 · port 22 |
| CVE-2026-22015 MEDIUM 4.3 | mysql 8.0.36 · port 3306 |
| CVE-2024-21247 LOW 3.8 | mysql 8.0.36 · port 3306 |
| CVE-2021-36368 LOW 3.7 | openssh 8.2p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 8.2p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.2p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.2p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.2p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 8.2p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 8.2p1 · port 22 |
| CVE-2025-50081 LOW 3.1 | mysql 8.0.36 · port 3306 |
| CVE-2026-106588 LOW 3.1 | openssh 8.2p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 8.2p1 · port 22 |
| CVE-2025-50098 LOW 2.7 | mysql 8.0.36 · port 3306 |
| CVE-2025-50104 LOW 2.7 | mysql 8.0.36 · port 3306 |
| CVE-2026-22001 LOW 2.7 | mysql 8.0.36 · port 3306 |
| CVE-2026-35388 LOW 2.5 | openssh 8.2p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.2p1 · port 22 |
| CVE-2024-21101 LOW 2.2 | mysql 8.0.36 · port 3306 |
| CVE-2025-50100 LOW 2.2 | mysql 8.0.36 · port 3306 |
| CVE-2025-21520 LOW 1.8 | mysql 8.0.36 · port 3306 |
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.