Host
As of our latest check on 2026-08-13, 95.78.124.81 (JSC "ER-Telecom Holding", AS42116, Russia) had 2 open ports (25, 8080) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-08-13.
No known CVEs now
Not counted: 116 on a distribution build — the fix may be backported (http_server 2.4.18). See them
Not counted: 4 only affect another platform (http_server 2.4.18). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 sndr.foteks.ru ESMTP Postfix (Ubuntu) 221 2.7.0 Error: I can break rules, too. Goodbye.
HTTP/1.1 200 OK
Date: Thu, 13 Aug 2026 19:51:19 GMT
Server: Apache/2.4.18 (Ubuntu)
Set-Cookie: PHPSESSID=r9t254roh7fgvc3ebphmhh1k67; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Access-Control-Allow-Origin: http://95.78.124.81
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 1381
Content-Type: text/html; charset=UTF-8
��V�n�8}�����SDR�{j�E���H�����P-1�H���Ev��/�+�a����R�,�Nv[����܇�[�'��o�^�����<?z3B��_�p|�~}=~{�z�>+"43L
��1F83�x��ܟ���J�����b��p��LK�OL�Ѱ3p7^�\�pN����ǖ� '"
1�v S!�Fa�FI���,�G?�l�B�4'�R*L���bg�`��Ҽp+�7������StF8K�i�����
M[���'��tJ�D������ˈ�ռ{���T����逤�+O\��Yi2�Z7�eq�(G��d9Uym�"+8�Əe�
�H���\����БIV...<truncated>
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. 3 of them are known to be exploited.
CVEs by severity: CRITICAL 27 HIGH 55 MEDIUM 33 LOW 1
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.18 · port 8080 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.4.18 · port 8080 |
| CVE-2019-0211 HIGH 7.8 known exploited | http_server 2.4.18 · port 8080 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2018-1312 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.18 · port 8080 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.4.18 · port 8080 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4.18 · port 8080 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.18 · port 8080 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.18 · port 8080 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.18 · port 8080 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.18 · port 8080 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.18 · port 8080 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.18 · port 8080 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.18 · port 8080 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.18 · port 8080 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.4.18 · port 8080 |
| CVE-2017-15715 HIGH 8.1 | http_server 2.4.18 · port 8080 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.18 · port 8080 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.18 · port 8080 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2016-4979 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2016-8740 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2017-15710 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2018-1333 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2018-17199 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.18 · port 8080 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4.18 · port 8080 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.18 · port 8080 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.18 · port 8080 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.18 · port 8080 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.4.18 · port 8080 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4.18 · port 8080 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4.18 · port 8080 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4.18 · port 8080 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.18 · port 8080 |
| CVE-2016-1546 MEDIUM 5.9 | http_server 2.4.18 · port 8080 |
| CVE-2018-11763 MEDIUM 5.9 | http_server 2.4.18 · port 8080 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.4.18 · port 8080 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.4.18 · port 8080 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.18 · port 8080 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.18 · port 8080 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.18 · port 8080 |
| CVE-2018-1283 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2018-17189 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2020-11985 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.18 · port 8080 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.18 · port 8080 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.18 · port 8080 |
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 2 MEDIUM 2
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.18 · port 8080 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4.18 · port 8080 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.18 · port 8080 |
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.