Raw response
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
Host
Tags: End-of-life software
As of our latest check on 2026-06-07, 212.72.183.201 (Artfiles New Media GmbH, AS8893, Germany) had 2 open ports (22, 443) and 82 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-06-07.
CVEs by severity: CRITICAL 6 HIGH 30 MEDIUM 35 LOW 11
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: 161 on a distribution build — the fix may be backported (php 5.4.45, http_server 2.2.22). See them
Not counted: 1 fixed by the distribution (http_server 2.2.22). See them
Not counted: 3 only affect another platform (http_server 2.2.22, php 5.4.45). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_6.0p1 Debian-4+deb7u7
<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>Bad request!</title> <link rev="made" href="mailto:[email protected]" /> <style type="text/css"><!--/*--><![CDATA[/*><!--*/ body { color: #000000; background-color: #FFFFFF; } a:link { color: #0000CC; } p, address {margin-left: 3em;} span {font-size: smaller;} /*]]>*/--></style> </head> <body> <h1>Bad request!</h1> <p> Your browser (or proxy) sent a request that this server could not understand. </p> <p> If you think this is a server error, please contact the <a href="mailto:[email protected]">webmaster</a>. </p> <h2>Error 400</h2> <address> <a href="/">cwhadmin.cyberwebhosting.de</a><br /> <span>Sun Jun 7 10:25:46 2026<br /> Apache/2.2.22 (Debian)</span> </address
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 56 HIGH 64 MEDIUM 39 LOW 2
| CVE | Software |
|---|---|
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.2.22 · port 443 |
| CVE-2015-4116 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2015-4601 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-2554 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-3141 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4537 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4538 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4539 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4540 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4541 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4542 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-4543 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-5768 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-5769 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-5770 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-5771 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-5772 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-5773 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-6288 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-6290 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-6291 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-6294 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-6295 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-6296 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7124 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7126 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7127 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7129 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7411 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7413 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7414 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-7417 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-9137 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-9138 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2016-9935 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2017-12933 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2017-3169 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2017-8923 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2017-9224 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2017-9225 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2017-9226 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2018-7584 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.2.22 · port 443 |
| CVE-2016-1903 CRITICAL 9.1 | php 5.4.45 · port 443 |
| CVE-2016-5114 CRITICAL 9.1 | php 5.4.45 · port 443 |
| CVE-2017-11147 CRITICAL 9.1 | php 5.4.45 · port 443 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.2.22 · port 443 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.2.22 · port 443 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.2.22 · port 443 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.2.22 · port 443 |
| CVE-2016-4342 HIGH 8.8 | php 5.4.45 · port 443 |
| CVE-2016-4343 HIGH 8.8 | php 5.4.45 · port 443 |
| CVE-2016-6297 HIGH 8.8 | php 5.4.45 · port 443 |
| CVE-2018-10549 HIGH 8.8 | php 5.4.45 · port 443 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.2.22 · port 443 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.2.22 · port 443 |
| CVE-2016-5093 HIGH 8.6 | php 5.4.45 · port 443 |
| CVE-2016-5094 HIGH 8.6 | php 5.4.45 · port 443 |
| CVE-2016-5095 HIGH 8.6 | php 5.4.45 · port 443 |
| CVE-2016-5096 HIGH 8.6 | php 5.4.45 · port 443 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.2.22 · port 443 |
| CVE-2016-3142 HIGH 8.2 | php 5.4.45 · port 443 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.2.22 · port 443 |
| CVE-2016-7412 HIGH 8.1 | php 5.4.45 · port 443 |
| CVE-2016-5399 HIGH 7.8 | php 5.4.45 · port 443 |
| CVE-2016-6289 HIGH 7.8 | php 5.4.45 · port 443 |
| CVE-2017-11628 HIGH 7.8 | php 5.4.45 · port 443 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2013-3735 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2014-0236 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2014-9425 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2015-1351 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2015-8874 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2015-8877 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2015-8879 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2015-8994 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-10158 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-10159 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-10161 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-10397 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-10712 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-4070 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7125 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7130 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7131 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7132 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7416 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7418 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-7478 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2016-9934 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-11142 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-11143 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-11144 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-11145 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-16642 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-7963 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-9229 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2018-10546 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2018-10548 HIGH 7.5 | php 5.4.45 · port 443 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2017-7272 HIGH 7.4 | php 5.4.45 · port 443 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.2.22 · port 443 |
| CVE-2014-9426 HIGH 7.3 | php 5.4.45 · port 443 |
| CVE-2015-8865 HIGH 7.3 | php 5.4.45 · port 443 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.2.22 · port 443 |
| CVE-2011-4718 MEDIUM 6.8 | php 5.4.45 · port 443 |
| CVE-2013-7327 MEDIUM 6.8 | php 5.4.45 · port 443 |
| CVE-2014-0226 MEDIUM 6.8 | http_server 2.2.22 · port 443 |
| CVE-2015-7803 MEDIUM 6.8 | php 5.4.45 · port 443 |
| CVE-2015-7804 MEDIUM 6.8 | php 5.4.45 · port 443 |
| CVE-2015-9253 MEDIUM 6.5 | php 5.4.45 · port 443 |
| CVE-2016-6292 MEDIUM 6.5 | php 5.4.45 · port 443 |
| CVE-2017-7890 MEDIUM 6.5 | php 5.4.45 · port 443 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.2.22 · port 443 |
| CVE-2018-10547 MEDIUM 6.1 | php 5.4.45 · port 443 |
| CVE-2018-5712 MEDIUM 6.1 | php 5.4.45 · port 443 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.2.22 · port 443 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.2.22 · port 443 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.2.22 · port 443 |
| CVE-2018-5711 MEDIUM 5.5 | php 5.4.45 · port 443 |
| CVE-2016-7128 MEDIUM 5.3 | php 5.4.45 · port 443 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.2.22 · port 443 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.2.22 · port 443 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.2.22 · port 443 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.2.22 · port 443 |
| CVE-2013-1862 MEDIUM 5.1 | http_server 2.2.22 · port 443 |
| CVE-2013-5704 MEDIUM 5.0 | http_server 2.2.22 · port 443 |
| CVE-2013-6438 MEDIUM 5.0 | http_server 2.2.22 · port 443 |
| CVE-2014-0098 MEDIUM 5.0 | http_server 2.2.22 · port 443 |
| CVE-2014-0231 MEDIUM 5.0 | http_server 2.2.22 · port 443 |
| CVE-2014-2020 MEDIUM 5.0 | php 5.4.45 · port 443 |
| CVE-2015-0228 MEDIUM 5.0 | http_server 2.2.22 · port 443 |
| CVE-2015-3183 MEDIUM 5.0 | http_server 2.2.22 · port 443 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.2.22 · port 443 |
| CVE-2018-10545 MEDIUM 4.7 | php 5.4.45 · port 443 |
| CVE-2013-6501 MEDIUM 4.6 | php 5.4.45 · port 443 |
| CVE-2014-4670 MEDIUM 4.6 | php 5.4.45 · port 443 |
| CVE-2008-0455 MEDIUM 4.3 | http_server 2.2.22 · port 443 |
| CVE-2012-3499 MEDIUM 4.3 | http_server 2.2.22 · port 443 |
| CVE-2012-4558 MEDIUM 4.3 | http_server 2.2.22 · port 443 |
| CVE-2013-1896 MEDIUM 4.3 | http_server 2.2.22 · port 443 |
| CVE-2014-0118 MEDIUM 4.3 | http_server 2.2.22 · port 443 |
| CVE-2014-9767 MEDIUM 4.3 | php 5.4.45 · port 443 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.2.22 · port 443 |
| CVE-2014-5459 LOW 3.6 | php 5.4.45 · port 443 |
| CVE-2012-2687 LOW 2.6 | http_server 2.2.22 · port 443 |
The distribution's security data says the package revision this service shows already has the fix for these CVEs, or that its build is not affected. They are not counted.
CVEs by severity: MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2012-0883 MEDIUM 6.9 | http_server 2.2.22 · port 443 |
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 1 HIGH 1 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-3566 CRITICAL 9.8 | php 5.4.45 · port 443 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.2.22 · port 443 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.2.22 · port 443 |
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.