- Server
- SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
- Host key
- ecdsa-sha2-nistp256 9a262fcf04db4a0e…
Raw response
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
Host
Tags: End-of-life software
As of our latest check on 2026-05-25, 83.136.193.210 (DDFR IT Infra & Security B.V., AS35467, Netherlands) had 2 open ports (22, 80) and 41 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-05-25.
CVEs by severity: CRITICAL 1 HIGH 8 MEDIUM 21 LOW 11
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: 80 on a distribution build — the fix may be backported (http_server 2.4.59, openssh 6.0p1). See them
Not counted: 3 fixed by the distribution (http_server 2.4.59). See them
Not counted: 2 only affect another platform (http_server 2.4.59). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
HTTP/1.1 200 OK Date: Mon, 25 May 2026 05:43:00 GMT Server: Apache/2.4.59 (Debian) Last-Modified: Wed, 26 Nov 2014 15:30:28 GMT ETag: "9e-508c4b511ad00-gzip" Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 147 Content-Type: text/html �%��!�w�������Hn1g8H8k������NM���R uIJ N[%�ƚ�z��'��U�ĥƷ�#�v������N 2l`�̉����>�%q�`8[�����}|�/�mCP$?�m�tmJ��LǞ
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 12 HIGH 44 MEDIUM 23 LOW 1
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.59 · port 80 |
| CVE-2016-1908 CRITICAL 9.8 | openssh 6.0p1 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.59 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.59 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.59 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.59 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.59 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.59 · port 80 |
| CVE-2015-5600 HIGH 8.1 | openssh 6.0p1 · port 22 |
| CVE-2016-0778 HIGH 8.1 | openssh 6.0p1 · port 22 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.59 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.59 · port 80 |
| CVE-2015-8325 HIGH 7.8 | openssh 6.0p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 6.0p1 · port 22 |
| CVE-2010-5107 HIGH 7.5 | openssh 6.0p1 · port 22 |
| CVE-2016-10708 HIGH 7.5 | openssh 6.0p1 · port 22 |
| CVE-2016-6515 HIGH 7.5 | openssh 6.0p1 · port 22 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.59 · port 80 |
| CVE-2014-1692 HIGH 7.3 | openssh 6.0p1 · port 22 |
| CVE-2016-10009 HIGH 7.3 | openssh 6.0p1 · port 22 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.59 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.59 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.59 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.59 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.59 · port 80 |
| CVE-2015-6564 HIGH 7.0 | openssh 6.0p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 6.0p1 · port 22 |
| CVE-2014-2653 MEDIUM 6.5 | openssh 6.0p1 · port 22 |
| CVE-2016-0777 MEDIUM 6.5 | openssh 6.0p1 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.59 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.59 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.59 · port 80 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 6.0p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 6.0p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 6.0p1 · port 22 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.59 · port 80 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 6.0p1 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.59 · port 80 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4.59 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.59 · port 80 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 6.0p1 · port 22 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.59 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.59 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.59 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.59 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.59 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.59 · port 80 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 6.0p1 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.59 · port 80 |
| CVE-2014-2532 MEDIUM 4.2 | openssh 6.0p1 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.59 · port 80 |
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.59 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.59 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.59 · 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.59 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.59 · 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.