- Banner
- 220 (vsFTPd 2.3.5)
Raw response
220 (vsFTPd 2.3.5)
Host
212.28.34.89
Tags: Expired certificate End-of-life software
As of our latest check on 2026-06-07, 212.28.34.89 (Transkom GmbH, AS12292, Germany) had 5 open ports (21, 80, 110, 143, 443) and 2 known CVEs.
Known CVEs on this host
5open ports
0names pointing here
2known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-06-07.
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: 55 on a distribution build — the fix may be backported (http_server 2.2.22). See them
Not counted: 2 only affect another platform (http_server 2.2.22). See them
- Network
- Transkom GmbH AS12292
- Open ports
- 21, 80, 110, 143, 443 · at our latest check, 2026-06-07
- Location
- Germany DE
- Hostname
- ouranos.ibs.de · reverse DNS, checked 2026-10-05
- Route
- 212.28.32.0/19 · announced by Transkom GmbH AS12292 no RPKI authorisation
- Organisation
- Transkom GmbH
- Registry network
- IBS-LAN1 · 212.28.34.0 - 212.28.34.255 · RIPE
- Abuse contact
- [email protected] · for IBS-LAN1
- First seen
- 2026-06-07 07:41 UTC
- Last seen alive
- 2026-06-07 07:55 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 (5)
80/tcp
HTTP
Apache/2.2.22 (Ubuntu)
first 2026-06-07 · last 2026-06-07
- Status
- 200 OK
- Title
- Transkom
- Server
- Apache/2.2.22 (Ubuntu)
Raw response
HTTP/1.1 200 OK
Date: Sun, 07 Jun 2026 07:54:21 GMT
Server: Apache/2.2.22 (Ubuntu)
Last-Modified: Mon, 20 Oct 2003 13:24:17 GMT
ETag: "73a53-127-3ca1e434bc240"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 216
Content-Type: text/html
�m���0E�|ES�H�jk��
�&���Z���R�ϗ���8�ɜ{f2ć(�:$b0C>��e�}p�xk�5�-61�(V�\$��ٳH�,��!��ٲI@!��᪼��x}��U1�%�gY
�6ժie��2h��������*}P#/���Ob4A��h��=����};�J�V��W9d�Y��*t�
ŃUW�N:������@'
110/tcp
POP3
first 2026-06-07 · last 2026-06-07
- Banner
- +OK Dovecot ready.
Raw response
+OK Dovecot ready.
143/tcp
IMAP
first 2026-06-07 · last 2026-06-07
- Banner
- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED] Dovecot ready.
Raw response
* OK Waiting for authentication process to respond..
443/tcp
TLS
first 2026-06-07 · last 2026-06-07
- TLS
- TLSv1.2
- Certificate for
- ecash.transkom.net, www.ecash.transkom.net
- Issued by
- UTN-USERFirst-Hardware
- Valid
- 2010-12-28 → 2013-12-28
Raw response
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> Reason: You're speaking plain HTTP to an SSL-enabled server port.<br /> Instead use the HTTPS scheme to access this URL, please.<br /> <blockquote>Hint: <a href="https://ecash.transkom.net/"><b>https://ecash.transkom.net/</b></a></blockquote></p> <hr> <address>Apache/2.2.22 (Ubuntu) Server at ecash.transkom.net Port 443</address> </body></html>
Vulnerabilities
Distribution build — the fix may be backported (55)
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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 13 HIGH 17 MEDIUM 24 LOW 1
| CVE | Software |
|---|---|
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.2.22 · port 80 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.2.22 · port 80 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.2.22 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.2.22 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.2.22 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.2.22 · port 80 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.2.22 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.2.22 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.2.22 · port 80 |
| CVE-2012-0883 MEDIUM 6.9 | http_server 2.2.22 · port 80 |
| CVE-2014-0226 MEDIUM 6.8 | http_server 2.2.22 · port 80 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.2.22 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.2.22 · port 80 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.2.22 · port 80 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.2.22 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.2.22 · port 80 |
| CVE-2013-1862 MEDIUM 5.1 | http_server 2.2.22 · port 80 |
| CVE-2013-5704 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2013-6438 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2014-0098 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2014-0231 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2015-0228 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2015-3183 MEDIUM 5.0 | http_server 2.2.22 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.2.22 · port 80 |
| CVE-2008-0455 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2012-3499 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2012-4558 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2013-1896 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2014-0118 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.2.22 · port 80 |
| CVE-2012-2687 LOW 2.6 | http_server 2.2.22 · port 80 |
Only affects another platform (2)
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: HIGH 1 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.2.22 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.2.22 · 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.