- Server
- SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.16
- Host key
- ssh-ed25519 b29cc092be119542…
Raw response
SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.16
Host
104.239.136.58
Tags: Hosting
As of our latest check on 2026-08-27, 104.239.136.58 (Rackspace Hosting, AS33070, United States) had 3 open ports (22, 80, 443) and 21 known CVEs.
Known CVEs on this host
3open ports
0names pointing here
21known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-08-27.
CVEs by severity: CRITICAL 3 HIGH 11 MEDIUM 4 LOW 3
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: 66 on a distribution build — the fix may be backported (http_server 2.4.52, php 8.1.2). See them
Not counted: 57 fixed by the distribution (php 8.1.2, openssh 8.9p1). See them
Not counted: 5 only affect another platform (http_server 2.4.52, php 8.1.2). See them
- Network
- Rackspace Hosting AS33070
- Open ports
- 22, 80, 443 · at our latest check, 2026-08-27
- Location
- United States US
- Route
- 104.239.128.0/19 · announced by Rackspace Hosting AS33070 no RPKI authorisation
- Organisation
- Rackspace Hosting
- Registry network
- RACKS-8-NET-16 · 104.239.128.0 - 104.239.255.255 · Rackspace Hosting · ARIN
- Abuse contact
- [email protected] · for RACKS-8-NET-16
- First seen
- 2026-08-27 23:25 UTC
- Last seen alive
- 2026-08-27 23:28 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 (3)
- Status
- 200 OK
- Title
- Welcome to 3D Cellular - 3d-cellular.com
- Server
- Apache/2.4.52 (Ubuntu)
- Powered by
- PHP/8.1.2-1ubuntu2.25
Raw response
HTTP/1.1 200 OK Date: Thu, 27 Aug 2026 23:26:10 GMT Server: Apache/2.4.52 (Ubuntu) X-Powered-By: PHP/8.1.2-1ubuntu2.25 Cache-Control: no-cache, private Set-Cookie: XSRF-TOKEN=eyJpdiI6Ik9Ic0FRWGpXMStuZlIzR3M3Vks0Unc9PSIsInZhbHVlIjoiT052Q1VCSU40NG1NQkpkMlIzcFRWd0p4M0FJVnpNSmdzMEl4VCs4dkMwYUROVVVoL0hHYVVjZWVMVUt6NUVsUFNiUEtOSlp4Q1ZNZnNWb2plNGduZTJ4STRzcFI4SzFmZm5BMWI5bEd4V2VENjBrdWxyV3BWcTAxL3cyTm1vMWEiLCJtYWMiOiI2NWNhMzBkMGFkNzVjYzcxYmFlNDcwNzdlYWRhMzRlZWFjMjkwMDEzOTg5M2VmMDYxZmI1NzljODZkYmYwNzRkIiwidGFnIjoiIn0%3D; expires=Fri, 28 Aug 2026 01:26:10 GMT; Max-Age=7200; path=/; samesite=lax Set-Cookie: 3d_cellular_session=eyJpdiI6ImFOVHBoLzFhd1JKQThGdEdKczFENWc9PSIsInZhbHVlIjoicjg0UDQweHk0cndqV1oweURyYzNUSVprWmNsYUFXS2RjdWtPN2pRRlhaWEhXOEUxY2FvNmp1RFR2MFZiZ0dLT3A1RzV4TEFoM1pJcnZyenVRL2hHeEEwbCtqdktNb0oxaVhTOHZvUXJKUDhTaDk4UVE2VEIzSitnL0FJMFAycGIiLCJtYWMiOiJmZTU4MWY1YzZjMjQyNGI3YWYwYTgzZGI1YjYyZTdlMmU2YTVhNTFlM2Y1NmM5YjVkMTA5Mjg1ZWNmZWRiZjg4IiwidGFnIjoiIn0
443/tcp
TLS
first 2026-08-27 · last 2026-08-27
- TLS
- TLSv1.2
- Certificate for
- 3d-cellular.com
- Issued by
- YR1
- Valid
- 2026-08-19 → 2026-11-17
Raw response
HTTP/1.1 400 Bad Request Date: Thu, 27 Aug 2026 23:26:10 GMT Server: Apache/2.4.52 (Ubuntu) Content-Length: 443 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> Reason: You're speaking plain HTTP to an SSL-enabled server port.<br /> Instead use the HTTPS scheme to access this URL, please.<br /> </p> <hr> <address>Apache/2.4.52 (Ubuntu) Server at 3d-cellular.com Port 80</address> </body></html>
Vulnerabilities
Distribution build — the fix may be backported (66)
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 16 HIGH 34 MEDIUM 16
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.52 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2024-1874 CRITICAL 9.4 | php 8.1.2 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.52 · port 80 |
| CVE-2024-5585 HIGH 8.8 | php 8.1.2 · port 80 |
| CVE-2024-8926 HIGH 8.8 | php 8.1.2 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.52 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.52 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.52 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.52 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.52 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.52 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.52 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.52 · port 80 |
| CVE-2025-14177 MEDIUM 6.3 | php 8.1.2 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.52 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.52 · port 80 |
| CVE-2024-2408 MEDIUM 5.9 | php 8.1.2 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.52 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.52 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.52 · port 80 |
Fixed by the distribution (57)
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: CRITICAL 9 HIGH 17 MEDIUM 26 LOW 5
| CVE | Software |
|---|---|
| CVE-2021-21708 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2022-31627 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2022-37454 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2023-28531 CRITICAL 9.8 | openssh 8.9p1 · port 22 |
| CVE-2023-3824 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.9p1 · port 22 |
| CVE-2024-11236 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2024-8932 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2022-31631 CRITICAL 9.1 | php 8.1.2 · port 80 |
| CVE-2022-31626 HIGH 8.8 | php 8.1.2 · port 80 |
| CVE-2024-11233 HIGH 8.2 | php 8.1.2 · port 80 |
| CVE-2025-14178 HIGH 8.2 | php 8.1.2 · port 80 |
| CVE-2025-14180 HIGH 8.2 | php 8.1.2 · port 80 |
| CVE-2022-31625 HIGH 8.1 | php 8.1.2 · port 80 |
| CVE-2023-0568 HIGH 8.1 | php 8.1.2 · port 80 |
| CVE-2024-6387 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.9p1 · port 22 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.9p1 · port 22 |
| CVE-2023-0662 HIGH 7.5 | php 8.1.2 · port 80 |
| CVE-2023-3823 HIGH 7.5 | php 8.1.2 · port 80 |
| CVE-2024-8927 HIGH 7.5 | php 8.1.2 · port 80 |
| CVE-2025-1735 HIGH 7.5 | php 8.1.2 · port 80 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.9p1 · port 22 |
| CVE-2024-11234 HIGH 7.2 | php 8.1.2 · port 80 |
| CVE-2022-31630 HIGH 7.1 | php 8.1.2 · port 80 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.9p1 · port 22 |
| CVE-2022-31629 MEDIUM 6.5 | php 8.1.2 · port 80 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2024-3096 MEDIUM 6.5 | php 8.1.2 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.9p1 · port 22 |
| CVE-2025-1217 MEDIUM 6.3 | php 8.1.2 · port 80 |
| CVE-2025-1219 MEDIUM 6.3 | php 8.1.2 · port 80 |
| CVE-2025-1734 MEDIUM 6.3 | php 8.1.2 · port 80 |
| CVE-2025-1736 MEDIUM 6.3 | php 8.1.2 · port 80 |
| CVE-2025-1861 MEDIUM 6.3 | php 8.1.2 · port 80 |
| CVE-2023-0567 MEDIUM 6.2 | php 8.1.2 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.9p1 · port 22 |
| CVE-2025-6491 MEDIUM 5.9 | php 8.1.2 · port 80 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 8.9p1 · port 22 |
| CVE-2024-8929 MEDIUM 5.8 | php 8.1.2 · port 80 |
| CVE-2022-31628 MEDIUM 5.5 | php 8.1.2 · port 80 |
| CVE-2023-51384 MEDIUM 5.5 | openssh 8.9p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.9p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.9p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.9p1 · port 22 |
| CVE-2024-5458 MEDIUM 5.3 | php 8.1.2 · port 80 |
| CVE-2024-8925 MEDIUM 5.3 | php 8.1.2 · port 80 |
| CVE-2025-1220 MEDIUM 5.3 | php 8.1.2 · port 80 |
| CVE-2023-3247 MEDIUM 4.3 | php 8.1.2 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 8.9p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.9p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.9p1 · port 22 |
| CVE-2024-9026 LOW 3.3 | php 8.1.2 · port 80 |
| CVE-2026-35388 LOW 2.5 | openssh 8.9p1 · port 22 |
Only affects another platform (5)
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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 2 HIGH 2 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-4577 CRITICAL 9.8 known exploited | php 8.1.2 · port 80 |
| CVE-2024-3566 CRITICAL 9.8 | php 8.1.2 · port 80 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
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.