- Banner
- 220 mail.bmw.md FTP server (Version 6.00LS) ready.
Raw response
220 mail.bmw.md FTP server (Version 6.00LS) ready.
Host
Tags: Self-signed certificate Expired certificate End-of-life software
As of our latest check on 2026-09-11, 95.65.9.19 (StarNet Solutii SRL, AS31252, Moldova) had 5 open ports (21, 22, 25, 80, 443) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-09-11.
No known CVEs now
Not counted: 398 on a distribution build — the fix may be backported (php 5.2.17, http_server 2.2.20, openssh 5.4p1, openssl 0.9.8q and 1 more). See them
Not counted: 6 only affect another platform (php 5.2.17, http_server 2.2.20). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
220 mail.bmw.md FTP server (Version 6.00LS) ready.
SSH-2.0-OpenSSH_5.4p1 FreeBSD-20100308
220-bmw.md ESMTP Fri, 11 Sep 2026 21:54:04 +0300 220-. 220-WARNING: Unsolicited commercial E-Mail (UCE/SPAM), pornographic 220-material, viruses and relaying is prohibited by this server and 220-any such messages will be rejected/filtered automatically 220-depending on content. 220-. 220-By using this server, you agree not to send any messages of the 220-above nature. Please disconnect immediately if you do not agree 220-to these terms and conditions. 220-. 220-Please contact POSTMASTER if you have any 220-enquiries about or problems with this server. 220 .
HTTP/1.1 200 OK Date: Fri, 11 Sep 2026 18:53:55 GMT Server: Apache/2.2.20 (FreeBSD) mod_ssl/2.2.20 OpenSSL/0.9.8q DAV/2 PHP/5.2.17 with Suhosin-Patch Last-Modified: Sat, 20 Nov 2004 20:16:24 GMT ETag: "639091-2c-3e9564c23b600" Accept-Ranges: bytes Content-Length: 44 Content-Type: text/html <html><body><h1>It works!</h1></body></html>
<!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://web.bmw.md/"><b>https://web.bmw.md/</b></a></blockquote></p> </body></html>
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. 2 of them are known to be exploited.
CVEs by severity: CRITICAL 76 HIGH 140 MEDIUM 164 LOW 18
| CVE | Software |
|---|---|
| CVE-2012-1823 CRITICAL 9.8 known exploited | php 5.2.17 · port 80 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.2.20 · port 80 |
| CVE-2011-3268 HIGH 10.0 | php 5.2.17 · port 80 |
| CVE-2012-2688 HIGH 10.0 | php 5.2.17 · port 80 |
| CVE-2010-4478 CRITICAL 9.8 | openssh 5.4p1 · port 22 |
| CVE-2011-1939 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2014-9912 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4116 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4599 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4600 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4601 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4602 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4603 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-4643 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-5589 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-6834 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-6835 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2015-8835 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-1908 CRITICAL 9.8 | openssh 5.4p1 · port 22 |
| CVE-2016-2108 CRITICAL 9.8 | openssl 0.9.8q · port 80 |
| CVE-2016-2554 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-3141 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4537 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4538 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4539 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4540 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4541 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4542 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-4543 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-5768 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-5769 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-5770 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-5771 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-5772 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-5773 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-6288 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-6290 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-6291 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-6294 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-6295 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-6296 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7124 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7126 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7127 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7129 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7411 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7413 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7414 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-7417 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-9137 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-9138 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2016-9935 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2017-12933 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2017-8923 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2017-9224 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2017-9225 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2017-9226 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2018-7584 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2019-9020 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2019-9021 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2019-9023 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2019-9641 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 5.4p1 · port 22 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.2.20 · port 80 |
| CVE-2011-4109 HIGH 9.3 | openssl 0.9.8q · port 80 |
| CVE-2016-1903 CRITICAL 9.1 | php 5.2.17 · port 80 |
| CVE-2016-5114 CRITICAL 9.1 | php 5.2.17 · port 80 |
| CVE-2017-11147 CRITICAL 9.1 | php 5.2.17 · port 80 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.2.20 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.2.20 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.2.20 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.2.20 · port 80 |
| CVE-2016-4342 HIGH 8.8 | php 5.2.17 · port 80 |
| CVE-2016-4343 HIGH 8.8 | php 5.2.17 · port 80 |
| CVE-2016-6297 HIGH 8.8 | php 5.2.17 · port 80 |
| CVE-2018-10549 HIGH 8.8 | php 5.2.17 · port 80 |
| CVE-2018-19520 HIGH 8.8 | php 5.2.17 · port 80 |
| CVE-2019-6977 HIGH 8.8 | php 5.2.17 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.2.20 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.2.20 · port 80 |
| CVE-2016-5093 HIGH 8.6 | php 5.2.17 · port 80 |
| CVE-2016-5094 HIGH 8.6 | php 5.2.17 · port 80 |
| CVE-2016-5095 HIGH 8.6 | php 5.2.17 · port 80 |
| CVE-2016-5096 HIGH 8.6 | php 5.2.17 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.2.20 · port 80 |
| CVE-2016-2176 HIGH 8.2 | openssl 0.9.8q · port 80 |
| CVE-2016-3142 HIGH 8.2 | php 5.2.17 · port 80 |
| CVE-2015-5600 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2016-0778 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.2.20 · port 80 |
| CVE-2016-6174 HIGH 8.1 | php 5.2.17 · port 80 |
| CVE-2016-7412 HIGH 8.1 | php 5.2.17 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 5.4p1 · port 22 |
| CVE-2002-0653 HIGH 7.8 | mod_ssl 2.2.20 · port 80 |
| CVE-2015-8325 HIGH 7.8 | openssh 5.4p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 5.4p1 · port 22 |
| CVE-2016-5399 HIGH 7.8 | php 5.2.17 · port 80 |
| CVE-2016-6289 HIGH 7.8 | php 5.2.17 · port 80 |
| CVE-2017-11628 HIGH 7.8 | php 5.2.17 · port 80 |
| CVE-2026-60002 HIGH 7.7 | openssh 5.4p1 · port 22 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2010-4252 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2010-4657 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2010-5107 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2011-1092 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2011-1148 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2011-1153 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2012-2110 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2012-2311 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2012-2386 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2013-1635 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2013-3735 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2013-6420 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-0236 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-3515 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-3669 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-8142 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-8176 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2014-9425 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-9427 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-9653 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2014-9705 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-0231 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-0273 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-0292 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2015-1351 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-2331 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-2787 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-3307 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-3329 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4022 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4025 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4026 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4147 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4604 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4605 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-4644 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-6833 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-6837 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-6838 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-8873 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-8874 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-8877 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-8879 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2015-8994 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-10158 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-10159 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-10161 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-10397 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-10708 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2016-10712 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-2106 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2016-2109 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2016-4070 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-6515 HIGH 7.5 | openssh 5.4p1 · port 22 |
| CVE-2016-7125 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-7130 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-7131 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-7132 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-7416 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-7418 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-7478 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2016-9934 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-11142 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-11143 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-11144 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-11145 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-16642 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-7963 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-9229 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2018-10546 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2018-10548 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2018-14883 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2018-15132 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2018-19395 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2018-19396 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2018-20783 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2019-9024 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2019-9637 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2019-9638 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2019-9639 HIGH 7.5 | php 5.2.17 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2021-4044 HIGH 7.5 | openssl 0.9.8q · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.2.20 · port 80 |
Showing the first 200 of 398.
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: CRITICAL 2 HIGH 2 MEDIUM 2
| CVE | Software |
|---|---|
| CVE-2012-2376 HIGH 10.0 | php 5.2.17 · port 80 |
| CVE-2015-4642 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2024-3566 CRITICAL 9.8 | php 5.2.17 · port 80 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.2.20 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.2.20 · port 80 |
| CVE-2011-0754 MEDIUM 4.4 | php 5.2.17 · port 80 |
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.
2 names · as answered by each domain's own name servers