Host
Tags: Hosting End-of-life software
As of our latest check on 2026-09-23, 120.27.63.36 (Hangzhou Alibaba Advertising Co.,Ltd., AS37963, China) had 2 open ports (22, 80) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-09-23.
No known CVEs now
Not counted: 72 on a distribution build — the fix may be backported (openssh 6.6.1p1, nginx 1.4.6). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
HTTP/1.1 200 OK
Server: nginx/1.4.6 (Ubuntu)
Date: Wed, 23 Sep 2026 14:19:32 GMT
Content-Type: text/html
Last-Modified: Thu, 06 Jun 2024 11:14:09 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Content-Encoding: gzip
135
�U�MO�0��H�&��H�^�8��1mǐ�&U�uۿ���Sl'~^�Nqm�N��I��W�p�U�.:���Aeƈ��ݨ1��}��=��[K��R��N����U5����ck4?K!{J�s��}�;�rOOx�|H�бLjJ�=i����Q"e�����.���%J�
��6{,�T<���ui��fo�ł����A��T��FI��1[�����u�EQrBT��{L'��A���������j��:2rض�]w�����ZC=�)���A��j1���_q���?���[�
0
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 5 HIGH 26 MEDIUM 30 LOW 11
| CVE | Software |
|---|---|
| CVE-2016-0746 CRITICAL 9.8 | nginx 1.4.6 · port 80 |
| CVE-2016-1908 CRITICAL 9.8 | openssh 6.6.1p1 · port 22 |
| CVE-2017-20005 CRITICAL 9.8 | nginx 1.4.6 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 6.6.1p1 · port 22 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 6.6.1p1 · port 22 |
| CVE-2015-5600 HIGH 8.1 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 6.6.1p1 · port 22 |
| CVE-2015-8325 HIGH 7.8 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 6.6.1p1 · port 22 |
| CVE-2016-1247 HIGH 7.8 | nginx 1.4.6 · port 80 |
| CVE-2022-41741 HIGH 7.8 | nginx 1.4.6 · port 80 |
| CVE-2026-106583 HIGH 7.8 | openssh 6.6.1p1 · port 22 |
| CVE-2021-23017 HIGH 7.7 | nginx 1.4.6 · port 80 |
| CVE-2014-0133 HIGH 7.5 | nginx 1.4.6 · port 80 |
| CVE-2016-0742 HIGH 7.5 | nginx 1.4.6 · port 80 |
| CVE-2016-10708 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2016-4450 HIGH 7.5 | nginx 1.4.6 · port 80 |
| CVE-2016-6515 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2017-7529 HIGH 7.5 | nginx 1.4.6 · port 80 |
| CVE-2026-106553 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59999 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 6.6.1p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 6.6.1p1 · port 22 |
| CVE-2021-3618 HIGH 7.4 | nginx 1.4.6 · port 80 |
| CVE-2016-10009 HIGH 7.3 | openssh 6.6.1p1 · port 22 |
| CVE-2022-41742 HIGH 7.1 | nginx 1.4.6 · port 80 |
| CVE-2015-6564 HIGH 7.0 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 6.6.1p1 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 6.6.1p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 6.6.1p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 6.6.1p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 6.6.1p1 · port 22 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 6.6.1p1 · port 22 |
| CVE-2018-16845 MEDIUM 6.1 | nginx 1.4.6 · port 80 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 6.6.1p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 6.6.1p1 · port 22 |
| CVE-2016-0747 MEDIUM 5.3 | nginx 1.4.6 · port 80 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2018-15473 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2018-15919 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 6.6.1p1 · port 22 |
| CVE-2019-20372 MEDIUM 5.3 | nginx 1.4.6 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 6.6.1p1 · port 22 |
| CVE-2014-3616 MEDIUM 4.3 | nginx 1.4.6 · port 80 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 6.6.1p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 6.6.1p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 6.6.1p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 6.6.1p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 6.6.1p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 6.6.1p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 6.6.1p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 6.6.1p1 · 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.