Raw response
SSH-2.0-OpenSSH_8.0
Host
2.27.136.174
As of our latest check on 2026-05-16, 2.27.136.174 (Ace Data Centers II, L.L.C., AS401152, United Kingdom) had 2 open ports (22, 80) and 54 known CVEs.
Known CVEs on this host
2open ports
0names pointing here
54known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-05-16.
CVEs by severity: CRITICAL 4 HIGH 15 MEDIUM 19 LOW 16
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: 111 on a distribution build — the fix may be backported (http_server 2.4.37). See them
Not counted: 5 only affect another platform (http_server 2.4.37, php 5.6.40). See them
- Network
- Ace Data Centers II, L.L.C. AS401152
- Open ports
- 22, 80 · at our latest check, 2026-05-16
- Location
- Warsaw, PL-MZ · Poland PL
- Route
- 2.27.136.0/24 · announced by FZCO AS219337 RPKI valid
- Organisation
- PLAY2GO - FZCO · Enterprise
- Registry network
- PLAY2GO-CUSTOMERS-NETWORK · 2.27.136.0 - 2.27.136.255 · RIPE
- Abuse contact
- [email protected] · for PLAY2GO-CUSTOMERS-NETWORK
- First seen
- 2026-05-15 12:21 UTC
- Last seen alive
- 2026-05-16 18:15 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 (2)
- Status
- 200 OK
- Server
- Apache/2.4.37 (Rocky Linux)
- Powered by
- PHP/5.6.40
Raw response
TTP/1.1 200 OK Date: Sat, 16 May 2026 18:14:52 GMT Server: Apache/2.4.37 (Rocky Linux) X-Powered-By: PHP/5.6.40 Content-Length: 0 Content-Type: text/html; charset=UTF-8
Vulnerabilities
Distribution build — the fix may be backported (111)
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 24 HIGH 60 MEDIUM 26 LOW 1
| 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-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-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-73636 HIGH 8.1 | http_server 2.4.37 · port 80 |
| 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-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-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-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-46729 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-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-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-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-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-43951 MEDIUM 6.5 | http_server 2.4.37 · port 80 |
| 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-2023-45802 MEDIUM 5.9 | http_server 2.4.37 · 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-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-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-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-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-2026-42356 LOW 3.7 | http_server 2.4.37 · port 80 |
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.
CVEs by severity: CRITICAL 1 HIGH 2 MEDIUM 2
| CVE | Software |
|---|---|
| CVE-2024-3566 CRITICAL 9.8 | php 5.6.40 · port 80 |
| 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 |
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.