Raw response
SSH-2.0-OpenSSH_8.4
Host
As of our latest check on 2026-05-26, 86.110.64.20 (Trusted Network GmbH, AS21385, Germany) had 2 open ports (22, 80) and 39 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-05-26.
CVEs by severity: CRITICAL 2 HIGH 10 MEDIUM 15 LOW 12
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: 82 on a distribution build — the fix may be backported (http_server 2.4.51). See them
Not counted: 3 only affect another platform (http_server 2.4.51). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_8.4
HTTP/1.1 200 OK Date: Tue, 26 May 2026 18:02:29 GMT Server: Apache/2.4.51 (Linux/SUSE) Last-Modified: Fri, 25 May 2018 11:08:13 GMT ETag: "100-56d05c8b69316" Accept-Ranges: bytes Content-Length: 256 Content-Type: text/html Impressum <pre>Paralab Consulting UG (haftungsbeschränkt) Kohlstatt 9 82205 Gilching Telefon 08105/3795824 email: [email protected] Amtsgericht Muenchen HRB 192573 Vertretungsberechtigter Geschäftsführer: Patrick Raithofer </pre>
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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 19 HIGH 45 MEDIUM 17 LOW 1
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.51 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.51 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.51 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.51 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.51 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.51 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.51 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.51 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.51 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.51 · port 80 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.51 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.51 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.51 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.51 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.51 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.51 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.51 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.51 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.51 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.51 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.51 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.51 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.51 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.51 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.51 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.51 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.51 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.51 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.51 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.51 · port 80 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.51 · 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 2 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.51 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.51 · 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.