- Banner
- 220 (vsFTPd 3.0.2)
Raw response
220 (vsFTPd 3.0.2) 530 Please login with USER and PASS. 530 Please login with USER and PASS. 530 Please login with USER and PASS. 530 Please login with USER and PASS. 530 Please login with USER and PASS.
Host
Tags: Database Expired certificate End-of-life software
As of our latest check on 2026-08-10, 85.209.148.109 (Support Chain LLC, AS60591, Belarus) had 5 open ports (21, 22, 80, 443, 3306) and 182 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-08-10.
CVEs by severity: CRITICAL 5 HIGH 20 MEDIUM 142 LOW 15
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: 57 on a distribution build — the fix may be backported (openssh 6.6.1p1). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 (vsFTPd 3.0.2) 530 Please login with USER and PASS. 530 Please login with USER and PASS. 530 Please login with USER and PASS. 530 Please login with USER and PASS. 530 Please login with USER and PASS.
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.13
HTTP/1.1 301 Moved Permanently Server: nginx/1.15.12 Date: Mon, 10 Aug 2026 06:47:57 GMT Content-Type: text/html Content-Length: 170 Connection: keep-alive Location: https://www.namehunter.ru/ <html> <head><title>301 Moved Permanently</title></head> <body> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx/1.15.12</center> </body> </html>
HTTP/1.1 400 Bad Request Server: nginx/1.15.12 Date: Mon, 10 Aug 2026 06:47:57 GMT Content-Type: text/html Content-Length: 658 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.15.12</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 -->
O
5.6.44-86.0�ɩ}hp{:NXQ���lKqv~75B/c'3mysql_native_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: CRITICAL 3 HIGH 17 MEDIUM 26 LOW 11
| CVE | Software |
|---|---|
| CVE-2016-1908 CRITICAL 9.8 | openssh 6.6.1p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 6.6.1p1 · port 22 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 6.6.1p1 · port 22 |
| CVE-2015-5600 HIGH 8.1 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 6.6.1p1 · port 22 |
| CVE-2015-8325 HIGH 7.8 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10708 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2016-6515 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59999 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10009 HIGH 7.3 | openssh 6.6.1p1 · port 22 |
| CVE-2015-6564 HIGH 7.0 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 6.6.1p1 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 6.6.1p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 6.6.1p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 6.6.1p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 6.6.1p1 · port 22 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2018-15473 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2018-15919 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 6.6.1p1 · port 22 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 6.6.1p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 6.6.1p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 6.6.1p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 6.6.1p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 6.6.1p1 · port 22 |
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