- Server
- SSH-2.0-Go
- Host key
- ssh-ed25519 cc865b28479b5131…
Raw response
SSH-2.0-Go
Host
As of our latest check on 2026-05-26, 85.158.153.20 (Merula Limited, AS16353, United Kingdom) had 2 open ports (22, 80) and 60 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-05-26.
CVEs by severity: CRITICAL 4 HIGH 28 MEDIUM 21 LOW 6 UNRATED 1
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: 55 on a distribution build — the fix may be backported (http_server 2.4.62). See them
Not counted: 1 only affects another platform (http_server 2.4.62). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-Go
HTTP/1.1 301 Moved Permanently Date: Tue, 26 May 2026 08:16:30 GMT Server: Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1 Location: https://85.158.153.20/ Content-Length: 230 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="https://85.158.153.20/">here</a>.</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.
CVEs by severity: CRITICAL 8 HIGH 33 MEDIUM 13 LOW 1
| CVE | Software |
|---|---|
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.62 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.62 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.62 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.62 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.62 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.62 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.62 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.62 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.62 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.62 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.62 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.62 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.62 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.62 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.62 · port 80 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.62 · 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 1
| CVE | Software |
|---|---|
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.62 · 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.