- Banner
- 220 FTP Server ready.
Raw response
220 FTP Server ready.
Host
Tags: Database Expired certificate
As of our latest check on 2026-06-27, 45.89.67.237 (IHOR HOSTING LTD, AS209641, Russia) had 6 open ports (21, 22, 25, 3306, 8080, 8443) and 79 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-06-27.
CVEs by severity: CRITICAL 15 HIGH 26 MEDIUM 21 LOW 17
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: 135 on a distribution build — the fix may be backported (http_server 2.4.38, openssl 1.1.1n, openssh 7.9p1, mariadb 10.3.38). See them
Not counted: 4 fixed by the distribution (http_server 2.4.38, openssl 1.1.1n). See them
Not counted: 4 only affect another platform (http_server 2.4.38). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 FTP Server ready.
SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2
554 SMTP synchronization error
c 5.5.5-10.3.38-MariaDB-0+deb10u1��3&ATakt'c����>I6pR*w;`Takmysql_native_password
HTTP/1.1 403 Forbidden
Date: Sat, 27 Jun 2026 11:28:13 GMT
Server: Apache/2.4.38 (Debian) mod_fcgid/2.3.9 OpenSSL/1.1.1n
Last-Modified: Fri, 30 Oct 2020 10:00:30 GMT
ETag: "4da-5b2e077730b80"
Accept-Ranges: bytes
Content-Length: 1242
Connection: close
Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>
<title>403 — Forbidden</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="description" content="You do not have permission to view this"/>
<style type="text/css">
body {font-size:14px; color:#777777; font-family:arial; text-align:center;}
h1 {font-size:180px; color:#99A7AF; margin: 70px 0 0 0;}
h2 {color: #DE6C5D; font-family: arial; font-size: 20px; font-weight: bold; letter-spacing: -1px; margin: -3px 0 39px;}
HTTP/1.1 400 Bad Request Date: Sat, 27 Jun 2026 11:28:13 GMT Server: Apache/2.4.38 (Debian) mod_fcgid/2.3.9 OpenSSL/1.1.1n Content-Length: 362 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> </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 25 HIGH 65 MEDIUM 43 LOW 2
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.38 · port 8080 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.4.38 · port 8080 |
| CVE-2019-0211 HIGH 7.8 known exploited | http_server 2.4.38 · port 8080 |
| CVE-2020-11984 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 7.9p1 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.38 · port 8080 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4.38 · port 8080 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.38 · port 8080 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.38 · port 8080 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.38 · port 8080 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.38 · port 8080 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.38 · port 8080 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.38 · port 8080 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.38 · port 8080 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.38 · port 8080 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.38 · port 8080 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.38 · port 8080 |
| CVE-2019-16905 HIGH 7.8 | openssh 7.9p1 · port 22 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2019-0215 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2019-10081 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2019-9517 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2020-11993 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2020-9490 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2021-36160 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2022-4450 HIGH 7.5 | openssl 1.1.1n · port 8080 |
| CVE-2023-0215 HIGH 7.5 | openssl 1.1.1n · port 8080 |
| CVE-2023-0464 HIGH 7.5 | openssl 1.1.1n · port 8080 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-4741 HIGH 7.5 | openssl 1.1.1n · port 8080 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2020-15778 HIGH 7.4 | openssh 7.9p1 · port 22 |
| CVE-2023-0286 HIGH 7.4 | openssl 1.1.1n · port 8080 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.38 · port 8080 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4.38 · port 8080 |
| CVE-2022-1292 HIGH 7.3 | openssl 1.1.1n · port 8080 |
| CVE-2022-2068 HIGH 7.3 | openssl 1.1.1n · port 8080 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.38 · port 8080 |
| CVE-2019-10097 HIGH 7.2 | http_server 2.4.38 · port 8080 |
| CVE-2021-41617 HIGH 7.0 | openssh 7.9p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 7.9p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 7.9p1 · port 22 |
| CVE-2022-47015 MEDIUM 6.5 | mariadb 10.3.38 · port 3306 |
| CVE-2023-2650 MEDIUM 6.5 | openssl 1.1.1n · port 8080 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 7.9p1 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.38 · port 8080 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.38 · port 8080 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4.38 · port 8080 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4.38 · port 8080 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4.38 · port 8080 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.38 · port 8080 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 7.9p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 7.9p1 · port 22 |
| CVE-2022-4304 MEDIUM 5.9 | openssl 1.1.1n · port 8080 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.38 · port 8080 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 7.9p1 · port 22 |
| CVE-2024-2511 MEDIUM 5.9 | openssl 1.1.1n · port 8080 |
| CVE-2024-0727 MEDIUM 5.5 | openssl 1.1.1n · port 8080 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.38 · port 8080 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.38 · port 8080 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 7.9p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 7.9p1 · port 22 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2022-2097 MEDIUM 5.3 | openssl 1.1.1n · port 8080 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2023-0465 MEDIUM 5.3 | openssl 1.1.1n · port 8080 |
| CVE-2023-0466 MEDIUM 5.3 | openssl 1.1.1n · port 8080 |
| CVE-2023-3817 MEDIUM 5.3 | openssl 1.1.1n · port 8080 |
| CVE-2023-5678 MEDIUM 5.3 | openssl 1.1.1n · port 8080 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.38 · port 8080 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.38 · port 8080 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.38 · port 8080 |
| CVE-2019-0197 MEDIUM 4.2 | http_server 2.4.38 · port 8080 |
| CVE-2021-36368 LOW 3.7 | openssh 7.9p1 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.38 · port 8080 |
The distribution's security data says the package revision this service shows already has the fix for these CVEs, or that its build is not affected. They are not counted.
CVEs by severity: HIGH 4
| CVE | Software |
|---|---|
| CVE-2023-4807 HIGH 7.8 | openssl 1.1.1n · port 8080 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.38 · port 8080 |
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.38 · port 8080 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.38 · port 8080 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4.38 · port 8080 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.38 · 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.