- Server
- SSH-2.0-OpenSSH_8.4p1 Debian-5+deb11u1
- Host key
- ssh-ed25519 0b1c8b45b6d131ec…
Raw response
SSH-2.0-OpenSSH_8.4p1 Debian-5+deb11u1
Host
Tags: Expired certificate
As of our latest check on 2026-05-19, 45.85.217.151 (Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG, AS48314, Germany) had 3 open ports (22, 80, 443) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-05-19.
No known CVEs now
Not counted: 89 on a distribution build — the fix may be backported (http_server 2.4.54, openssh 8.4p1). See them
Not counted: 3 fixed by the distribution (http_server 2.4.54). See them
Not counted: 2 only affect another platform (http_server 2.4.54). See them
Earlier software versions of this host and the CVEs they had are kept as its history. See the history
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_8.4p1 Debian-5+deb11u1
HTTP/1.1 200 OK Date: Tue, 19 May 2026 05:39:00 GMT Server: Apache/2.4.54 (Debian) Last-Modified: Sat, 01 Apr 2023 08:34:36 GMT ETag: "1c-5f8423229bf40" Accept-Ranges: bytes Content-Length: 28 Content-Type: text/html ping test by INSTANTHOST.GG
HTTP/1.1 400 Bad Request Date: Tue, 19 May 2026 05:39:00 GMT Server: Apache/2.4.54 (Debian) Content-Length: 451 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> <hr> <address>Apache/2.4.54 (Debian) Server at ping.fra.instanthost.gg Port 80</address> </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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 14 HIGH 41 MEDIUM 27 LOW 7
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.54 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.4p1 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.54 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.54 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.54 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.54 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.54 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.54 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.54 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.54 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.4p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.4p1 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.54 · port 80 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.4p1 · port 22 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.4p1 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.54 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.54 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.54 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.54 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.54 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.54 · port 80 |
| CVE-2021-28041 HIGH 7.1 | openssh 8.4p1 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.4p1 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.4p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.4p1 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.54 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.54 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.4p1 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.54 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.4p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.4p1 · port 22 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.54 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.54 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.54 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.4p1 · port 22 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 8.4p1 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.54 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.54 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.4p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.4p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.4p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.4p1 · port 22 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.54 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.54 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.54 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.54 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.54 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.54 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.54 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.4p1 · port 22 |
| CVE-2025-32728 LOW 3.8 | openssh 8.4p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.4p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.4p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.4p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.4p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.4p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.4p1 · port 22 |
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 3
| CVE | Software |
|---|---|
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.54 · 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
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.54 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.54 · port 80 |
Software versions this host showed earlier, when we saw each, why it no longer applies, and the CVEs matched on it then. None of them is 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.
1 name · as answered by each domain's own name servers