- Server
- SSH-2.0-OpenSSH_8.7
- Host key
- ssh-ed25519 111b6cf064aedd93…
Raw response
SSH-2.0-OpenSSH_8.7
Host
As of our latest check on 2026-08-27, 104.248.149.2 (DigitalOcean, LLC, AS14061, Singapore) had 2 open ports (22, 80) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-08-27.
No known CVEs now
Not counted: 177 on a distribution build — the fix may be backported (http_server 2.4.53, openssl 3.0.1, openssh 8.7). See them
Not counted: 3 only affect another platform (http_server 2.4.53). 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.7
HTTP/1.1 301 Moved Permanently Date: Thu, 27 Aug 2026 20:32:18 GMT Server: Apache/2.4.53 (CentOS Stream) OpenSSL/3.0.1 Location: https://104.248.149.2/ 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://104.248.149.2/">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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 21 HIGH 86 MEDIUM 59 LOW 11
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.53 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.7 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2025-15467 CRITICAL 9.8 | openssl 3.0.1 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2026-31789 CRITICAL 9.8 | openssl 3.0.1 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.53 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.53 · port 80 |
| CVE-2024-5535 CRITICAL 9.1 | openssl 3.0.1 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.53 · port 80 |
| CVE-2026-34182 CRITICAL 9.1 | openssl 3.0.1 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.53 · port 80 |
| CVE-2026-75803 CRITICAL 9.1 | openssl 3.0.1 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.53 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.53 · port 80 |
| CVE-2026-45447 HIGH 8.8 | openssl 3.0.1 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.53 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.53 · port 80 |
| CVE-2026-84782 HIGH 8.2 | openssl 3.0.1 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.53 · port 80 |
| CVE-2024-6387 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-28387 HIGH 8.1 | openssl 3.0.1 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.53 · port 80 |
| CVE-2026-7383 HIGH 8.1 | openssl 3.0.1 · port 80 |
| CVE-2023-4807 HIGH 7.8 | openssl 3.0.1 · port 80 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.7 · port 22 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2022-0778 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2022-1473 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2022-30522 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2022-3358 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2022-3602 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2022-3786 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2022-3996 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2022-4450 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-0215 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-0216 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-0217 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-0401 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-0464 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2023-5363 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2024-4741 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2024-6119 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2025-69420 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2025-69421 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2025-9230 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-28388 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-28389 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-28390 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-31790 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-34180 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-45445 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-54874 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-63072 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-63076 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2026-9076 HIGH 7.5 | openssl 3.0.1 · port 80 |
| CVE-2023-0286 HIGH 7.4 | openssl 3.0.1 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.53 · port 80 |
| CVE-2025-69419 HIGH 7.4 | openssl 3.0.1 · port 80 |
| CVE-2022-1292 HIGH 7.3 | openssl 3.0.1 · port 80 |
| CVE-2022-2068 HIGH 7.3 | openssl 3.0.1 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.53 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.53 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.53 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.53 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.53 · port 80 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.7 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.7 · port 22 |
| CVE-2023-2650 MEDIUM 6.5 | openssl 3.0.1 · port 80 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2023-6129 MEDIUM 6.5 | openssl 3.0.1 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.53 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.53 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.53 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.53 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.53 · port 80 |
| CVE-2022-1434 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2022-4304 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2023-1255 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.53 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.7 · port 22 |
| CVE-2023-6237 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2024-2511 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2026-42766 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2026-42767 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 8.7 · port 22 |
| CVE-2026-63074 MEDIUM 5.9 | openssl 3.0.1 · port 80 |
| CVE-2024-0727 MEDIUM 5.5 | openssl 3.0.1 · port 80 |
| CVE-2026-22795 MEDIUM 5.5 | openssl 3.0.1 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.53 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.53 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.7 · port 22 |
| CVE-2022-1343 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2022-2097 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2023-0465 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2023-0466 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2023-2975 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2023-3817 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2023-5678 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2024-4603 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2026-22796 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2026-35189 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2026-75805 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2026-75806 MEDIUM 5.3 | openssl 3.0.1 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.53 · port 80 |
| CVE-2022-4203 MEDIUM 4.9 | openssl 3.0.1 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.53 · port 80 |
| CVE-2026-45446 MEDIUM 4.8 | openssl 3.0.1 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.7 · port 22 |
| CVE-2025-68160 MEDIUM 4.7 | openssl 3.0.1 · port 80 |
| CVE-2024-9143 MEDIUM 4.3 | openssl 3.0.1 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.53 · port 80 |
| CVE-2024-13176 MEDIUM 4.1 | openssl 3.0.1 · port 80 |
| CVE-2025-69418 MEDIUM 4.0 | openssl 3.0.1 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 8.7 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.7 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.53 · port 80 |
| CVE-2026-42770 LOW 3.7 | openssl 3.0.1 · port 80 |
| CVE-2026-54872 LOW 3.7 | openssl 3.0.1 · port 80 |
| CVE-2026-77696 LOW 3.7 | openssl 3.0.1 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 8.7 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.7 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.7 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.7 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.7 · port 22 |
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.53 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.53 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.53 · 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.