- Server
- SSH-2.0-OpenSSH_9.7 FreeBSD-20240318
- Host key
- ssh-ed25519 2c693ceba31a89e6…
Raw response
SSH-2.0-OpenSSH_9.7 FreeBSD-20240318 Invalid SSH identification string.
Host
Tags: Hosting
As of our latest check on 2026-10-24, 148.72.133.125 (velia.net, AS30083, United States) had 3 open ports (22, 25, 80) and 24 known CVEs, 2 known to be exploited.
Open ports and CVEs as of our latest check of this host, 2026-10-24.
CVEs by severity: CRITICAL 5 HIGH 7 MEDIUM 11 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
Not counted: 129 on a distribution build — the fix may be backported (http_server 2.4.64, openssl 3.0.13, openssh 9.7). See them
Not counted: 3 only affect another platform (php 8.2.29, openssh 9.7). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_9.7 FreeBSD-20240318 Invalid SSH identification string.
554 5.5.0 Error: SMTP protocol synchronization
HTTP/1.1 200 OK Date: Sat, 24 Oct 2026 00:20:10 GMT Server: Apache/2.4.64 (FreeBSD) OpenSSL/3.0.13 X-Powered-By: PHP/8.2.29 Transfer-Encoding: chunked Content-Type: text/html; charset=UTF-8 3 ok 0
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 15 HIGH 57 MEDIUM 42 LOW 15
| CVE | Software |
|---|---|
| CVE-2024-4741 CRITICAL 9.8 | openssl 3.0.13 · port 80 |
| CVE-2025-15467 CRITICAL 9.8 | openssl 3.0.13 · port 80 |
| CVE-2025-9230 CRITICAL 9.8 | openssl 3.0.13 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.64 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.64 · port 80 |
| CVE-2026-31789 CRITICAL 9.8 | openssl 3.0.13 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.64 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.64 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.64 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.64 · port 80 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 9.7 · port 22 |
| CVE-2024-5535 CRITICAL 9.1 | openssl 3.0.13 · port 80 |
| CVE-2026-34182 CRITICAL 9.1 | openssl 3.0.13 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.64 · port 80 |
| CVE-2026-75803 CRITICAL 9.1 | openssl 3.0.13 · port 80 |
| CVE-2024-9143 HIGH 8.8 | openssl 3.0.13 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.64 · port 80 |
| CVE-2026-45447 HIGH 8.8 | openssl 3.0.13 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.64 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.64 · port 80 |
| CVE-2026-84782 HIGH 8.2 | openssl 3.0.13 · port 80 |
| CVE-2024-6387 HIGH 8.1 | openssh 9.7 · port 22 |
| CVE-2026-119618 HIGH 8.1 | http_server 2.4.64 · port 80 |
| CVE-2026-28387 HIGH 8.1 | openssl 3.0.13 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 9.7 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 9.7 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.64 · port 80 |
| CVE-2026-7383 HIGH 8.1 | openssl 3.0.13 · port 80 |
| CVE-2026-106583 HIGH 7.8 | openssh 9.7 · port 22 |
| CVE-2024-39894 HIGH 7.5 | openssh 9.7 · port 22 |
| CVE-2024-6119 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2025-69420 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2025-69421 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-106553 HIGH 7.5 | openssh 9.7 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 9.7 · port 22 |
| CVE-2026-107496 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-28388 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-28389 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-28390 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-31790 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-34180 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-45445 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-54874 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-59999 HIGH 7.5 | openssh 9.7 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 9.7 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-63072 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-63076 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.64 · port 80 |
| CVE-2026-9076 HIGH 7.5 | openssl 3.0.13 · port 80 |
| CVE-2025-69419 HIGH 7.4 | openssl 3.0.13 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.64 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.64 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.64 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.64 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.64 · port 80 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 9.7 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.64 · port 80 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 9.7 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 9.7 · port 22 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.64 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 9.7 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.64 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 9.7 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 9.7 · port 22 |
| CVE-2025-54090 MEDIUM 6.3 | http_server 2.4.64 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.64 · port 80 |
| CVE-2024-2511 MEDIUM 5.9 | openssl 3.0.13 · port 80 |
| CVE-2025-26466 MEDIUM 5.9 | openssh 9.7 · port 22 |
| CVE-2025-9231 MEDIUM 5.9 | openssl 3.0.13 · port 80 |
| CVE-2025-9232 MEDIUM 5.9 | openssl 3.0.13 · port 80 |
| CVE-2026-42766 MEDIUM 5.9 | openssl 3.0.13 · port 80 |
| CVE-2026-42767 MEDIUM 5.9 | openssl 3.0.13 · port 80 |
| CVE-2026-63074 MEDIUM 5.9 | openssl 3.0.13 · port 80 |
| CVE-2026-22795 MEDIUM 5.5 | openssl 3.0.13 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.64 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.64 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 9.7 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 9.7 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 9.7 · port 22 |
| CVE-2024-4603 MEDIUM 5.3 | openssl 3.0.13 · port 80 |
| CVE-2026-22796 MEDIUM 5.3 | openssl 3.0.13 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.64 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.64 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.64 · port 80 |
| CVE-2026-35189 MEDIUM 5.3 | openssl 3.0.13 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.64 · port 80 |
| CVE-2026-75805 MEDIUM 5.3 | openssl 3.0.13 · port 80 |
| CVE-2026-75806 MEDIUM 5.3 | openssl 3.0.13 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.64 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.64 · port 80 |
| CVE-2026-45446 MEDIUM 4.8 | openssl 3.0.13 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 9.7 · port 22 |
| CVE-2025-68160 MEDIUM 4.7 | openssl 3.0.13 · port 80 |
| CVE-2024-13176 MEDIUM 4.6 | openssl 3.0.13 · port 80 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 9.7 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.64 · port 80 |
| CVE-2025-69418 MEDIUM 4.0 | openssl 3.0.13 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 9.7 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 9.7 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.64 · port 80 |
| CVE-2026-42770 LOW 3.7 | openssl 3.0.13 · port 80 |
| CVE-2026-54872 LOW 3.7 | openssl 3.0.13 · port 80 |
| CVE-2026-77696 LOW 3.7 | openssl 3.0.13 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 9.7 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 9.7 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 9.7 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 9.7 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 9.7 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 9.7 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 9.7 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 9.7 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 9.7 · port 22 |
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. 1 of them is known to be exploited.
CVEs by severity: HIGH 2 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2026-123158 HIGH 8.1 known exploited | openssh 9.7 · port 22 |
| CVE-2026-17545 HIGH 7.5 | php 8.2.29 · port 80 |
| CVE-2025-1218 MEDIUM 5.9 | php 8.2.29 · 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.
16 names · as answered by each domain's own name servers