- Server
- SSH-2.0-OpenSSH_8.0
- Host key
- ssh-ed25519 de8320c3a6489b2d…
Raw response
SSH-2.0-OpenSSH_8.0
Host
Tags: Hosting
As of our latest check on 2026-09-23, 120.26.72.52 (Hangzhou Alibaba Advertising Co.,Ltd., AS37963, China) had 2 open ports (22, 80) and 2 known CVEs, 1 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-09-23.
CVEs by severity: HIGH 1 MEDIUM 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: 39 on a distribution build — the fix may be backported (openssh 8.0). 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 200 OK
Server: nginx/1.24.0
Date: Wed, 23 Sep 2026 14:21:31 GMT
Content-Type: text/html
Content-Length: 452
Last-Modified: Thu, 01 Jul 2021 09:21:13 GMT
Connection: keep-alive
ETag: "60dd8909-1c4"
Accept-Ranges: bytes
<!DOCTYPE html>
<html>
<head>
<title>HTTP Server Test Page</title>
<style>
body {
width: 35em;
margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif;
}
</style>
</head>
<body>
<h1>Welcome to HTTP Server Test Page!</h1>
<p>If you see this page, the httpd web server is successfully installed and
working. Further configuration is required.</p>
<p><em>Thank you for using apache httpd.</em></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.
CVEs by severity: CRITICAL 1 HIGH 7 MEDIUM 15 LOW 16
| CVE | Software |
|---|---|
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.0 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.0 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.0 · port 22 |
| CVE-2019-16905 HIGH 7.8 | openssh 8.0 · port 22 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.0 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.0 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 8.0 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.0 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.0 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.0 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 8.0 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.0 · port 22 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 8.0 · port 22 |
| 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-2026-73282 MEDIUM 4.8 | openssh 8.0 · port 22 |
| CVE-2026-106552 MEDIUM 4.2 | openssh 8.0 · port 22 |
| CVE-2025-32728 LOW 3.8 | openssh 8.0 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.0 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 8.0 · port 22 |
| 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-106587 LOW 3.3 | openssh 8.0 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 8.0 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 8.0 · port 22 |
| CVE-2026-106583 LOW 2.5 | openssh 8.0 · port 22 |
| CVE-2026-106584 LOW 2.5 | openssh 8.0 · port 22 |
| CVE-2026-106586 LOW 2.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 |
| CVE-2026-106553 LOW 2.2 | openssh 8.0 · port 22 |
| CVE-2026-106555 LOW 2.2 | openssh 8.0 · port 22 |
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.