As of our latest check on 2026-06-27, 45.151.137.174 (LLC Vpsville, AS59504, Russia) had 6 open ports (21, 22, 25, 80, 443, 8080) and 35 known CVEs, 1 known to be exploited.
Known CVEs on this host
6open ports
0names pointing here
35known CVEs
1known exploited
Open ports and CVEs as of our latest check of this host, 2026-06-27.
CVEs by severity: CRITICAL 3HIGH 9MEDIUM 14LOW 9
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: 2 fixed by the distribution (openssh 9.2p1). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (6)
21/tcpFTPfirst 2026-06-27 · last 2026-06-27
Banner
220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 21:32. Server port: 21.
220-This is a private system - No anonymous logi
Raw response
220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 21:29. Server port: 21.
220-This is a private system - No anonymous login
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
22/tcpSSHOpenSSH_9.2p135 CVEsfirst 2026-06-27 · last 2026-06-27
Server
SSH-2.0-OpenSSH_9.2p1 Debian-2
Host key
ssh-ed25519 46ac9fab7083b985…
Raw response
SSH-2.0-OpenSSH_9.2p1 Debian-2
25/tcpSMTPfirst 2026-06-27 · last 2026-06-27
Banner
220 vps257383 ESMTP Postfix (Debian/GNU)
Raw response
220 vps257383 ESMTP Postfix (Debian/GNU)
221 2.7.0 Error: I can break rules, too. Goodbye.
80/tcpHTTPApachefirst 2026-06-27 · last 2026-06-27
HTTP/1.1 400 Bad Request
Date: Sat, 27 Jun 2026 18:29:47 GMT
Server: Apache
Content-Length: 483
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>
<p>Additionally, a 400 Bad Request
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>
8080/tcpHTTPApachefirst 2026-06-27 · last 2026-06-27
Status
400 Bad Request
Server
Apache
Raw response
HTTP/1.1 400 Bad Request
Date: Sat, 27 Jun 2026 18:29:47 GMT
Server: Apache
Content-Length: 126
Connection: close
Content-Type: text/html; charset=iso-8859-1
<script>document.location.href='https://'+location.hostname+':'+location.port;</script><h1>Error 400 - trying to redirect</h1>
Vulnerabilities
Fixed by the distribution (2)
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.
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.