- Server
- SSH-2.0-OpenSSH_10.3
- Host key
- ssh-ed25519 dfcd6766ded54a79…
Raw response
SSH-2.0-OpenSSH_10.3
Host
5.20.153.21
Tags: Expired certificate
As of our latest check on 2026-05-19, 5.20.153.21 (UAB "Cgates", AS21412, Lithuania) had 3 open ports (22, 80, 443) and 22 known CVEs.
Known CVEs on this host
3open ports
0names pointing here
22known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-05-19.
CVEs by severity: HIGH 5 MEDIUM 10 LOW 7
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: 141 possible, version too vague to tell (http_server 2.4). See them
Earlier software versions of this host and the CVEs they had are kept as its history. See the history
- Network
- UAB "Cgates" AS21412
- Open ports
- 22, 80, 443 · at our latest check, 2026-05-19
- Location
- Lithuania LT
- Hostname
- data-153-21.cgates.lt · reverse DNS, checked 2026-10-04
- Route
- 5.20.128.0/19 · announced by UAB "Cgates" AS21412 RPKI valid
- Organisation
- UAB "CGATES" · Access network (cable / DSL / ISP)
- Registry network
- LT-CGATES · 5.20.128.0 - 5.20.223.255 · UAB "Cgates" · RIPE
- Abuse contact
- [email protected] · for LT-CGATES
- Hostnames
- api.shithead.jonytis.eu, data-153-21.cgates.lt, jonytis.eu
- First seen
- 2026-05-13 09:03 UTC
- Last seen alive
- 2026-05-19 13:03 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
Apache/2.4
first 2026-05-13 · last 2026-05-19
- Status
- 401 Unauthorized
- Title
- 401 Unauthorized
- Server
- Apache/2.4
Raw response
HTTP/1.1 401 Unauthorized Date: Tue, 19 May 2026 13:03:18 GMT Server: Apache/2.4 WWW-Authenticate: Basic realm="Authentication Required" Content-Length: 386 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Unauthorized</title> </head><body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> <hr> </body></html>
443/tcp
TLS
first 2026-05-13 · last 2026-05-19
- TLS
- TLSv1.2
- Certificate for
- *.jonytis.eu, api.shithead.jonytis.eu, jonytis.eu
- Issued by
- E8
- Valid
- 2026-04-13 → 2026-07-12
Raw response
HTTP/1.1 400 Bad Request Server: nginx/1.30.1 Date: Tue, 19 May 2026 13:03:18 GMT Content-Type: text/html Content-Length: 657 Connection: close <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.30.1</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 disable MSIE and Chrome friendly error page -->
Vulnerabilities
Possible, version too vague to tell (141)
These CVEs were matched on a software version that names only a major release (such as “2”) or no version at all: whether the release running here is affected cannot be told. They are not counted anywhere on this site.
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2021-40438 CRITICAL 9.0 | http_server 2.4 · port 80 |
| CVE-2019-0211 HIGH 7.8 | http_server 2.4 · port 80 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2020-11984 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4 · port 80 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4 · port 80 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4 · port 80 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.4 · port 80 |
| CVE-2017-15715 HIGH 8.1 | http_server 2.4 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2013-2249 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2018-1333 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2018-17199 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2019-10081 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2019-9517 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2020-11993 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2020-13950 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2020-9490 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2021-36160 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2023-43622 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4 · port 80 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4 · port 80 |
| CVE-2014-0226 MEDIUM 6.8 | http_server 2.4 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4 · port 80 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4 · port 80 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4 · port 80 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4 · port 80 |
| CVE-2018-11763 MEDIUM 5.9 | http_server 2.4 · port 80 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.4 · port 80 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.4 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4 · port 80 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4 · port 80 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4 · port 80 |
| CVE-2018-1283 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2020-11985 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2021-30641 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4 · port 80 |
| CVE-2013-6438 MEDIUM 5.0 | http_server 2.4 · port 80 |
| CVE-2014-0098 MEDIUM 5.0 | http_server 2.4 · port 80 |
| CVE-2014-0231 MEDIUM 5.0 | http_server 2.4 · port 80 |
| CVE-2015-0228 MEDIUM 5.0 | http_server 2.4 · port 80 |
| CVE-2015-3183 MEDIUM 5.0 | http_server 2.4 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4 · port 80 |
| CVE-2008-0455 MEDIUM 4.3 | http_server 2.4 · port 80 |
| CVE-2013-1896 MEDIUM 4.3 | http_server 2.4 · port 80 |
| CVE-2014-0118 MEDIUM 4.3 | http_server 2.4 · port 80 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.4 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4 · port 80 |
| CVE-2019-0197 MEDIUM 4.2 | http_server 2.4 · port 80 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4 · port 80 |
CVE history
Software versions this host showed earlier, when we saw each, why it no longer applies, and the CVEs matched on it then. None of them is counted.
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.