- Server
- SSH-2.0-OpenSSH_10.0 FreeBSD-20250801
- Host key
- ssh-ed25519 ae612e5772772e6c…
Raw response
SSH-2.0-OpenSSH_10.0 FreeBSD-20250801
Host
Tags: Hosting Expired certificate
As of our latest check on 2026-06-09, 217.182.192.77 (OVH SAS, AS16276, France) had 3 open ports (22, 80, 443) and 11 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-06-09.
CVEs by severity: CRITICAL 4 HIGH 3 MEDIUM 4
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: 119 on a distribution build — the fix may be backported (openssl 3.5.4, http_server 2.4.67, openssh 10.0). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_10.0 FreeBSD-20250801
HTTP/1.1 403 Forbidden Date: Tue, 09 Jun 2026 07:33:34 GMT Server: Apache/2.4.67 (FreeBSD) OpenSSL/3.5.4 X-Powered-By: PHP/8.3.30 Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8 c8 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> </body></html> 0
HTTP/1.1 400 Bad Request Date: Tue, 09 Jun 2026 07:33:33 GMT Server: Apache/2.4.67 (FreeBSD) OpenSSL/3.5.4 Content-Length: 402 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <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 /> </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.
CVEs by severity: CRITICAL 10 HIGH 52 MEDIUM 35 LOW 21 UNRATED 1
| CVE | Software |
|---|---|
| CVE-2025-15467 CRITICAL 9.8 | openssl 3.5.4 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-31789 CRITICAL 9.8 | openssl 3.5.4 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-34182 CRITICAL 9.1 | openssl 3.5.4 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.67 · port 80 |
| CVE-2026-75803 CRITICAL 9.1 | openssl 3.5.4 · port 80 |
| CVE-2026-45447 HIGH 8.8 | openssl 3.5.4 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.67 · port 80 |
| CVE-2026-84782 HIGH 8.2 | openssl 3.5.4 · port 80 |
| CVE-2026-28387 HIGH 8.1 | openssl 3.5.4 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 10.0 · port 22 |
| CVE-2026-35386 HIGH 8.1 | openssh 10.0 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 10.0 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.67 · port 80 |
| CVE-2026-7383 HIGH 8.1 | openssl 3.5.4 · port 80 |
| CVE-2026-60002 HIGH 7.7 | openssh 10.0 · port 22 |
| CVE-2025-69420 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2025-69421 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-14456 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-14457 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-18798 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-28388 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-28389 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-28390 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-31790 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-34180 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-34183 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-42764 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-45445 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-54873 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-54874 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-60000 HIGH 7.5 | openssh 10.0 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63072 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-63075 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-63076 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-72897 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-84784 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2026-9076 HIGH 7.5 | openssl 3.5.4 · port 80 |
| CVE-2025-69419 HIGH 7.4 | openssl 3.5.4 · port 80 |
| CVE-2026-34181 HIGH 7.4 | openssl 3.5.4 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 10.0 · port 22 |
| CVE-2026-2673 MEDIUM 6.5 | openssl 3.5.4 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 10.0 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.67 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 10.0 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 10.0 · port 22 |
| CVE-2025-11187 MEDIUM 6.1 | openssl 3.5.4 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.67 · port 80 |
| CVE-2025-15468 MEDIUM 5.9 | openssl 3.5.4 · port 80 |
| CVE-2025-66199 MEDIUM 5.9 | openssl 3.5.4 · port 80 |
| CVE-2026-42766 MEDIUM 5.9 | openssl 3.5.4 · port 80 |
| CVE-2026-42767 MEDIUM 5.9 | openssl 3.5.4 · port 80 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 10.0 · port 22 |
| CVE-2026-63074 MEDIUM 5.9 | openssl 3.5.4 · port 80 |
| CVE-2025-15469 MEDIUM 5.5 | openssl 3.5.4 · port 80 |
| CVE-2026-22795 MEDIUM 5.5 | openssl 3.5.4 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.67 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 10.0 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 10.0 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 10.0 · port 22 |
| CVE-2026-22796 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-35189 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-42769 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-42772 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.67 · port 80 |
| CVE-2026-75804 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-75805 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-75806 MEDIUM 5.3 | openssl 3.5.4 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.67 · port 80 |
| CVE-2026-45446 MEDIUM 4.8 | openssl 3.5.4 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 10.0 · port 22 |
| CVE-2025-68160 MEDIUM 4.7 | openssl 3.5.4 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.67 · port 80 |
| CVE-2026-106552 MEDIUM 4.2 | openssh 10.0 · port 22 |
| CVE-2025-69418 MEDIUM 4.0 | openssl 3.5.4 · port 80 |
| CVE-2026-106582 LOW 3.7 | openssh 10.0 · port 22 |
| CVE-2026-35191 LOW 3.7 | openssl 3.5.4 · port 80 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.67 · port 80 |
| CVE-2026-42768 LOW 3.7 | openssl 3.5.4 · port 80 |
| CVE-2026-42770 LOW 3.7 | openssl 3.5.4 · port 80 |
| CVE-2026-54872 LOW 3.7 | openssl 3.5.4 · port 80 |
| CVE-2026-54875 LOW 3.7 | openssl 3.5.4 · port 80 |
| CVE-2026-77696 LOW 3.7 | openssl 3.5.4 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 10.0 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 10.0 · port 22 |
| CVE-2026-106587 LOW 3.6 | openssh 10.0 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 10.0 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 10.0 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 10.0 · port 22 |
| CVE-2026-106583 LOW 2.5 | openssh 10.0 · port 22 |
| CVE-2026-106584 LOW 2.5 | openssh 10.0 · port 22 |
| CVE-2026-106586 LOW 2.5 | openssh 10.0 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 10.0 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 10.0 · port 22 |
| CVE-2026-106553 LOW 2.2 | openssh 10.0 · port 22 |
| CVE-2026-106555 LOW 2.2 | openssh 10.0 · port 22 |
| CVE-2026-63073 NONE | openssl 3.5.4 · 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.