- Server
- SSH-2.0-OpenSSH_8.0
- Host key
- ssh-ed25519 2d5b67dcb08d947f…
Raw response
SSH-2.0-OpenSSH_8.0
Host
Tags: Hosting
As of our latest check on 2026-08-28, 104.250.152.2 (GorillaServers, Inc., AS53850, United States) had 2 open ports (22, 80) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-08-28.
No known CVEs now
Not counted: 159 on a distribution build — the fix may be backported (http_server 2.4.37, openssh 8.0, openssl 1.1.1k). See them
Not counted: 4 only affect another platform (http_server 2.4.37). 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.0
HTTP/1.1 302 Found Date: Fri, 28 Aug 2026 02:01:05 GMT Server: Apache/2.4.37 (AlmaLinux) OpenSSL/1.1.1k mod_fcgid/2.3.9 Location: https://104.250.152.2/ Content-Length: 206 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="https://104.250.152.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. 3 of them are known to be exploited.
CVEs by severity: CRITICAL 26 HIGH 76 MEDIUM 49 LOW 8
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.37 · port 80 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.4.37 · port 80 |
| CVE-2019-0211 HIGH 7.8 known exploited | http_server 2.4.37 · port 80 |
| CVE-2020-11984 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2021-3711 CRITICAL 9.8 | openssl 1.1.1k · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.0 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.37 · port 80 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4.37 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.37 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.37 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.37 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.37 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.37 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.37 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.37 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.37 · port 80 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.37 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.37 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.0 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.0 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.37 · port 80 |
| CVE-2019-16905 HIGH 7.8 | openssh 8.0 · port 22 |
| CVE-2023-4807 HIGH 7.8 | openssl 1.1.1k · port 80 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.0 · port 22 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2018-17199 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2019-0190 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2019-0215 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2019-10081 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2019-9517 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2020-11993 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2020-9490 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2021-36160 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2022-0778 HIGH 7.5 | openssl 1.1.1k · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2022-4450 HIGH 7.5 | openssl 1.1.1k · port 80 |
| CVE-2023-0215 HIGH 7.5 | openssl 1.1.1k · port 80 |
| CVE-2023-0464 HIGH 7.5 | openssl 1.1.1k · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-4741 HIGH 7.5 | openssl 1.1.1k · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.0 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2020-15778 HIGH 7.4 | openssh 8.0 · port 22 |
| CVE-2021-3712 HIGH 7.4 | openssl 1.1.1k · port 80 |
| CVE-2023-0286 HIGH 7.4 | openssl 1.1.1k · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.37 · port 80 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4.37 · port 80 |
| CVE-2022-1292 HIGH 7.3 | openssl 1.1.1k · port 80 |
| CVE-2022-2068 HIGH 7.3 | openssl 1.1.1k · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.37 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.37 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.37 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.37 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.37 · port 80 |
| CVE-2019-10097 HIGH 7.2 | http_server 2.4.37 · port 80 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.0 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.0 · port 22 |
| CVE-2023-2650 MEDIUM 6.5 | openssl 1.1.1k · port 80 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.37 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.37 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.37 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.37 · port 80 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4.37 · port 80 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4.37 · port 80 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4.37 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.37 · port 80 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 8.0 · port 22 |
| CVE-2021-4160 MEDIUM 5.9 | openssl 1.1.1k · port 80 |
| CVE-2022-4304 MEDIUM 5.9 | openssl 1.1.1k · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.37 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.0 · port 22 |
| CVE-2024-2511 MEDIUM 5.9 | openssl 1.1.1k · port 80 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 8.0 · port 22 |
| CVE-2024-0727 MEDIUM 5.5 | openssl 1.1.1k · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.37 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.37 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.0 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.0 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.0 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.0 · port 22 |
| CVE-2018-17189 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2022-2097 MEDIUM 5.3 | openssl 1.1.1k · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2023-0465 MEDIUM 5.3 | openssl 1.1.1k · port 80 |
| CVE-2023-0466 MEDIUM 5.3 | openssl 1.1.1k · port 80 |
| CVE-2023-3817 MEDIUM 5.3 | openssl 1.1.1k · port 80 |
| CVE-2023-5678 MEDIUM 5.3 | openssl 1.1.1k · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.37 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.37 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.0 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.37 · port 80 |
| CVE-2019-0197 MEDIUM 4.2 | http_server 2.4.37 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 8.0 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.0 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.37 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 8.0 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.0 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.0 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.0 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.0 · 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 2
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.37 · port 80 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4.37 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.37 · 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.