- Banner
- 220 Ancrix ESMTP Mail Server, v1.3
Raw response
220 Ancrix ESMTP Mail Server, v1.3 500 5.5.1 Command unrecognized: "" 500 5.5.1 Command unrecognized: "" 500 5.5.1 Command unrecognized: "" 500 5.5.1 Command unrecognized: ""
Host
As of our latest check on 2026-10-25, 212.142.79.253 (JSC BALTICOM, AS24651, Latvia) had 2 open ports (25, 143) and 3 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-10-25.
CVEs by severity: HIGH 1 MEDIUM 1 LOW 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
All of them on a software version from an earlier observation: a service of that kind is open now.
Not counted: 88 from an older observation (http_server 2.2.22, bind 9.9.1-p1; matched 2026-06-08). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 Ancrix ESMTP Mail Server, v1.3 500 5.5.1 Command unrecognized: "" 500 5.5.1 Command unrecognized: "" 500 5.5.1 Command unrecognized: "" 500 5.5.1 Command unrecognized: ""
* OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE AUTH=SCRAM-SHA-1 AUTH=GSSAPI AUTH=DIGEST-MD5 AUTH=OTP AUTH=NTLM AUTH=CRAM-MD5 AUTH=LOGIN AUTH=PLAIN SASL-IR] core.macom.lv Cyrus IMAP v2.4.16 server ready
These CVEs were matched on software this host reported in an earlier observation (matched 2026-06-08), not on a port that is open now, and no service of that kind was open at the latest check (2026-10-25). They are not counted above; 2 of them are known to be exploited.
CVEs by severity: CRITICAL 13 HIGH 37 MEDIUM 36 LOW 2
| CVE | Software |
|---|---|
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.2.22 |
| CVE-2015-5477 HIGH 7.8 known exploited | bind 9.9.1-p1 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2021-25216 CRITICAL 9.8 | bind 9.9.1-p1 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.2.22 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.2.22 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.2.22 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.2.22 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.2.22 |
| CVE-2016-1286 HIGH 8.6 | bind 9.9.1-p1 |
| CVE-2020-8616 HIGH 8.6 | bind 9.9.1-p1 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.2.22 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.2.22 |
| CVE-2020-8625 HIGH 8.1 | bind 9.9.1-p1 |
| CVE-2015-5722 HIGH 7.8 | bind 9.9.1-p1 |
| CVE-2017-3141 HIGH 7.8 | bind 9.9.1-p1 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.2.22 |
| CVE-2016-2776 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.2.22 |
| CVE-2016-8864 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2016-9131 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2017-3145 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.2.22 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.2.22 |
| CVE-2018-5740 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2018-5743 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2021-25215 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.2.22 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.2.22 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.2.22 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.2.22 |
| CVE-2022-38177 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.2.22 |
| CVE-2023-3341 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2023-4408 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2023-50387 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2023-50868 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.2.22 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.2.22 |
| CVE-2026-3039 HIGH 7.5 | bind 9.9.1-p1 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.2.22 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.2.22 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.2.22 |
| CVE-2015-5986 HIGH 7.1 | bind 9.9.1-p1 |
| CVE-2012-0883 MEDIUM 6.9 | http_server 2.2.22 |
| CVE-2014-0226 MEDIUM 6.8 | http_server 2.2.22 |
| CVE-2016-1285 MEDIUM 6.8 | bind 9.9.1-p1 |
| CVE-2016-6170 MEDIUM 6.5 | bind 9.9.1-p1 |
| CVE-2018-5741 MEDIUM 6.5 | bind 9.9.1-p1 |
| CVE-2020-8622 MEDIUM 6.5 | bind 9.9.1-p1 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.2.22 |
| CVE-2016-2775 MEDIUM 5.9 | bind 9.9.1-p1 |
| CVE-2017-3136 MEDIUM 5.9 | bind 9.9.1-p1 |
| CVE-2017-3143 MEDIUM 5.9 | bind 9.9.1-p1 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.2.22 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.2.22 |
| CVE-2020-8617 MEDIUM 5.9 | bind 9.9.1-p1 |
| CVE-2019-6465 MEDIUM 5.3 | bind 9.9.1-p1 |
| CVE-2021-25219 MEDIUM 5.3 | bind 9.9.1-p1 |
| CVE-2022-2795 MEDIUM 5.3 | bind 9.9.1-p1 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.2.22 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.2.22 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.2.22 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.2.22 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.2.22 |
| CVE-2013-1862 MEDIUM 5.1 | http_server 2.2.22 |
| CVE-2013-5704 MEDIUM 5.0 | http_server 2.2.22 |
| CVE-2013-6438 MEDIUM 5.0 | http_server 2.2.22 |
| CVE-2014-0098 MEDIUM 5.0 | http_server 2.2.22 |
| CVE-2014-0231 MEDIUM 5.0 | http_server 2.2.22 |
| CVE-2015-0228 MEDIUM 5.0 | http_server 2.2.22 |
| CVE-2015-3183 MEDIUM 5.0 | http_server 2.2.22 |
| CVE-2018-5745 MEDIUM 4.9 | bind 9.9.1-p1 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.2.22 |
| CVE-2008-0455 MEDIUM 4.3 | http_server 2.2.22 |
| CVE-2012-3499 MEDIUM 4.3 | http_server 2.2.22 |
| CVE-2012-4558 MEDIUM 4.3 | http_server 2.2.22 |
| CVE-2013-1896 MEDIUM 4.3 | http_server 2.2.22 |
| CVE-2014-0118 MEDIUM 4.3 | http_server 2.2.22 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.2.22 |
| CVE-2017-3142 LOW 3.7 | bind 9.9.1-p1 |
| CVE-2012-2687 LOW 2.6 | http_server 2.2.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.
4 names · as answered by each domain's own name servers