- Server
- SSH-2.0-OpenSSH_5.0
- Host key
- ssh-rsa c023cbe4b59f54a4…
Raw response
SSH-2.0-OpenSSH_5.0
Host
Tags: End-of-life software
As of our latest check on 2026-07-19, 66.207.213.84 (Beanfield Technologies Inc., AS21949, Canada) had 2 open ports (22, 80) and 372 known CVEs, 2 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-07-19.
CVEs by severity: CRITICAL 64 HIGH 135 MEDIUM 156 LOW 17
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: 84 on a distribution build — the fix may be backported (http_server 2.2.8). See them
Not counted: 8 only affect another platform (php 5.2.5, http_server 2.2.8). See them
Earlier software versions of this host and the CVEs they had are kept as its history. See the history
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_5.0
HTTP/1.1 302 Found Date: Sun, 19 Jul 2026 22:06:51 GMT Server: Apache/2.2.8 (Fedora) X-Powered-By: PHP/5.2.5 Status: 302 Moved Temporarily Set-Cookie: My_Session=01fef71d1c92f8aa5642b19ed4cebc95; expires=Sun, 19-Jul-2026 22:07:51 GMT; path=/ Location: http://66.207.213.84/index_ultranet.php?My_Session=01fef71d1c92f8aa5642b19ed4cebc95 Content-Length: 0 Connection: close Content-Type: text/html; charset=UTF-8
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 22 MEDIUM 45 LOW 4
| CVE | Software |
|---|---|
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.2.8 · port 80 |
| CVE-2009-3555 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2017-3167 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2017-7679 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.2.8 · port 80 |
| CVE-2017-9788 CRITICAL 9.1 | http_server 2.2.8 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.2.8 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.2.8 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.2.8 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.2.8 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.2.8 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.2.8 · port 80 |
| CVE-2016-5387 HIGH 8.1 | http_server 2.2.8 · port 80 |
| CVE-2011-3192 HIGH 7.8 | http_server 2.2.8 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2009-1955 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2009-2699 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2016-8743 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2017-9798 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.2.8 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.2.8 · port 80 |
| CVE-2009-1890 HIGH 7.1 | http_server 2.2.8 · port 80 |
| CVE-2009-1891 HIGH 7.1 | http_server 2.2.8 · port 80 |
| CVE-2012-0883 MEDIUM 6.9 | http_server 2.2.8 · port 80 |
| CVE-2014-0226 MEDIUM 6.8 | http_server 2.2.8 · port 80 |
| CVE-2009-1956 MEDIUM 6.4 | http_server 2.2.8 · port 80 |
| CVE-2016-4975 MEDIUM 6.1 | http_server 2.2.8 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.2.8 · port 80 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.2.8 · port 80 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.2.8 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.2.8 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.2.8 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.2.8 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.2.8 · port 80 |
| CVE-2013-1862 MEDIUM 5.1 | http_server 2.2.8 · port 80 |
| CVE-2007-6750 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2008-2364 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2009-3095 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2009-3560 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2009-3720 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2010-0408 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2010-1452 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2010-1623 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2011-3368 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2013-5704 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2013-6438 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2014-0098 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2014-0231 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2015-0228 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2015-3183 MEDIUM 5.0 | http_server 2.2.8 · port 80 |
| CVE-2009-1195 MEDIUM 4.9 | http_server 2.2.8 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.2.8 · port 80 |
| CVE-2012-0031 MEDIUM 4.6 | http_server 2.2.8 · port 80 |
| CVE-2011-3607 MEDIUM 4.4 | http_server 2.2.8 · port 80 |
| CVE-2007-6420 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2008-0455 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2008-2939 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2009-0023 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2010-0434 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2011-0419 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2011-3639 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2011-4317 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2012-0053 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2012-3499 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2012-4558 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2013-1896 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2014-0118 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2016-8612 MEDIUM 4.3 | http_server 2.2.8 · port 80 |
| CVE-2008-0456 LOW 2.6 | http_server 2.2.8 · port 80 |
| CVE-2009-3094 LOW 2.6 | http_server 2.2.8 · port 80 |
| CVE-2012-2687 LOW 2.6 | http_server 2.2.8 · port 80 |
| CVE-2011-4415 LOW 1.2 | http_server 2.2.8 · port 80 |
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 3 MEDIUM 3
| CVE | Software |
|---|---|
| CVE-2010-0425 HIGH 10.0 | http_server 2.2.8 · port 80 |
| CVE-2012-2376 HIGH 10.0 | php 5.2.5 · port 80 |
| CVE-2015-4642 CRITICAL 9.8 | php 5.2.5 · port 80 |
| CVE-2024-3566 CRITICAL 9.8 | php 5.2.5 · port 80 |
| CVE-2024-40898 HIGH 7.5 | http_server 2.2.8 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.2.8 · port 80 |
| CVE-2009-3294 MEDIUM 5.0 | php 5.2.5 · port 80 |
| CVE-2011-0754 MEDIUM 4.4 | php 5.2.5 · port 80 |
Software versions this host showed earlier, when we saw each, why it no longer applies, and the CVEs matched on it then. None of them is counted.
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.