- Status
- 200 OK
- Server
- Apache/2.4.58 (Ubuntu)
Raw response
HTTP/1.1 200 OK Date: Thu, 27 Aug 2026 01:35:15 GMT Server: Apache/2.4.58 (Ubuntu) Content-Length: 3 Content-Type: text/html; charset=UTF-8 No.
Host
104.153.31.236
As of our latest check on 2026-08-27, 104.153.31.236 (Greenlight Networks, LLC, AS31775, United States) had 1 open port (8080) and 6 known CVEs.
Known CVEs on this host
1open port
0names pointing here
6known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-08-27.
CVEs by severity: HIGH 4 MEDIUM 1 LOW 1
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: 59 on a distribution build — the fix may be backported (http_server 2.4.58). See them
Not counted: 2 only affect another platform (http_server 2.4.58). See them
- Network
- Greenlight Networks, LLC AS31775
- Open ports
- 8080 · at our latest check, 2026-08-27
- Location
- United States US
- Route
- 104.153.28.0/22 · announced by Greenlight Networks, LLC AS31775 RPKI valid
- Organisation
- Greenlight Networks, LLC · Access network (cable / DSL / ISP)
- First seen
- 2026-08-27 01:35 UTC
- Last seen alive
- 2026-08-27 01:36 UTC
- Hosted domains
- No host name points here
Reputation
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (1)
Vulnerabilities
Distribution build — the fix may be backported (59)
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 11 HIGH 34 MEDIUM 14
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.58 · port 8080 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.58 · port 8080 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.58 · port 8080 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.58 · port 8080 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.58 · port 8080 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.58 · port 8080 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.58 · port 8080 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.58 · port 8080 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.58 · port 8080 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.58 · port 8080 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.58 · port 8080 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.58 · port 8080 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.58 · port 8080 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.58 · port 8080 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.58 · port 8080 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4.58 · port 8080 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.58 · port 8080 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.58 · port 8080 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.58 · port 8080 |
Only affects another platform (2)
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.58 · port 8080 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.58 · port 8080 |
Port history
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.