22/tcp
SSH
OpenSSH_8.0
first 2026-09-28 · last 2026-09-28
- Server
- SSH-2.0-OpenSSH_8.0
- Host key
- ssh-ed25519 98e421bda026cf77…
Raw response
SSH-2.0-OpenSSH_8.0
Host
120.26.255.2
Tags: Hosting Expired certificate
As of our latest check on 2026-09-28, 120.26.255.2 (Hangzhou Alibaba Advertising Co.,Ltd., AS37963, China) had 3 open ports (22, 80, 443) and no known CVEs.
Known CVEs on this host
3open ports
0names pointing here
0known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-09-28.
No known CVEs now
Not counted: 39 on a distribution build — the fix may be backported (openssh 8.0). See them
- Network
- Hangzhou Alibaba Advertising Co.,Ltd. AS37963
- Open ports
- 22, 80, 443 · at our latest check, 2026-09-28
- Location
- China CN
- Route
- 120.26.0.0/16 · announced by Hangzhou Alibaba Advertising Co.,Ltd. AS37963 RPKI valid
- Organisation
- Alibaba Group · Content / hosting
- Registry network
- ALISOFT · 120.24.0.0 - 120.27.255.255 · APNIC
- Abuse contact
- [email protected] · for ALISOFT
- First seen
- 2026-09-28 09:58 UTC
- Last seen alive
- 2026-09-28 10:02 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)
80/tcp
HTTP
nginx/1.28.0
first 2026-09-28 · last 2026-09-28
- Status
- 200 OK
- Title
- Welcome to nginx!
- Server
- nginx/1.28.0
Raw response
HTTP/1.1 200 OK
Server: nginx/1.28.0
Date: Mon, 28 Sep 2026 09:59:05 GMT
Content-Type: text/html
Content-Length: 615
Last-Modified: Wed, 23 Apr 2025 13:00:03 GMT
Connection: keep-alive
ETag: "6808e453-267"
Accept-Ranges: bytes
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>
<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>
<p><em>Thank you for using nginx.</em></p>
</body>
</html>
443/tcp
TLS
first 2026-09-28 · last 2026-09-28
- TLS
- TLSv1.2
- Certificate for
- www.yunhaifan.cn, yunhaifan.cn
- Issued by
- Encryption Everywhere DV TLS CA - G2
- Valid
- 2026-04-22 → 2026-07-20
Raw response
HTTP/1.1 400 Bad Request Server: nginx/1.28.0 Date: Mon, 28 Sep 2026 09:59:05 GMT Content-Type: text/html Content-Length: 657 Connection: close Strict-Transport-Security: max-age=31536000; includeSubDomains X-Frame-Options: SAMEORIGIN X-Content-Type-Options: nosniff Referrer-Policy: strict-origin-when-cross-origin X-XSS-Protection: 1; mode=block <html> <head><title>400 The plain HTTP request was sent to HTTPS port</title></head> <body> <center><h1>400 Bad Request</h1></center> <center>The plain HTTP request was sent to HTTPS port</center> <hr><center>nginx/1.28.0</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to d
Distribution build — the fix may be backported (39)
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 10 MEDIUM 16 LOW 12
| 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-106583 HIGH 7.8 | openssh 8.0 · port 22 |
| CVE-2026-60002 HIGH 7.7 | openssh 8.0 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 8.0 · port 22 |
| CVE-2026-106555 HIGH 7.5 | 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-106552 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-106586 MEDIUM 4.3 | 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-106584 LOW 3.3 | 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-35388 LOW 2.5 | openssh 8.0 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.0 · port 22 |
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.