- Server
- SSH-2.0-OpenSSH_8.4p1 Debian-5+deb11u7
- Host key
- ssh-ed25519 377551eed56e0bc6…
Raw response
SSH-2.0-OpenSSH_8.4p1 Debian-5+deb11u7
Host
As of our latest check on 2026-11-02, 167.71.94.0 (DigitalOcean, LLC, AS14061, United States) had 2 open ports (22, 80) and 12 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-11-02.
CVEs by severity: HIGH 4 MEDIUM 3 LOW 5
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: 60 on a distribution build — the fix may be backported (http_server 2.4.67, openssh 8.4p1). 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.4p1 Debian-5+deb11u7
HTTP/1.1 301 Moved Permanently Date: Mon, 02 Nov 2026 14:30:27 GMT Server: Apache/2.4.67 (Debian) Location: /cliente/ Content-Encoding: gzip Vary: Accept-Encoding Content-Length: 20 Content-Type: text/html; charset=UTF-8 �
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 27 MEDIUM 17 LOW 8
| CVE | Software |
|---|---|
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.4p1 · port 22 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 8.4p1 · port 22 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.67 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.67 · port 80 |
| CVE-2026-119618 HIGH 8.1 | http_server 2.4.67 · 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.67 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-59999 HIGH 7.5 | openssh 8.4p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.4p1 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.67 · 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-2026-35387 MEDIUM 6.5 | openssh 8.4p1 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.67 · 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-2026-29170 MEDIUM 6.1 | http_server 2.4.67 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.4p1 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.67 · 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-2026-58415 MEDIUM 5.3 | http_server 2.4.67 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.67 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.4p1 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.67 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 8.4p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.4p1 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.67 · port 80 |
| 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 |
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.