Host
As of our latest check on 2026-11-01, 166.70.34.7 (XMission, L.C., AS6315, United States) had 3 open ports (25, 80, 443) and 8 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-11-01.
CVEs by severity: HIGH 5 MEDIUM 2 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: 74 on a distribution build — the fix may be backported (http_server 2.4.52). See them
Not counted: 3 only affect another platform (http_server 2.4.52). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
554 mail.mjnservices.com ESMTP not accepting messages 421 4.7.0 mail.mjnservices.com Rejecting open proxy mail3.lpswtjs.com [104.168.87.60] (may be forged)
HTTP/1.1 302 Found Date: Sun, 01 Nov 2026 23:23:31 GMT Server: Apache/2.4.52 (Ubuntu) Expires: Sun, 01 Nov 2026 23:23:31 GMT Cache-Control: private, no-cache, no-store, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache X-Frame-Options: sameorigin Set-Cookie: roundcube_sessid=v9unrdjepolu4b4fodk44fr8mo; path=/; HttpOnly Upgrade: h2,h2c Connection: Upgrade Last-Modified: Sun, 01 Nov 2026 23:23:31 GMT Location: https://166.70.34.7/ Content-Length: 0 Content-Type: text/html; charset=UTF-8
HTTP/1.1 400 Bad Request Date: Sun, 01 Nov 2026 23:23:31 GMT Server: Apache/2.4.52 (Ubuntu) Content-Length: 452 Connection: close Content-Type: text/html; charset=iso-8859-1 <!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 /> </p> <hr> <address>Apache/2.4.52 (Ubuntu) Server at webmail.mjnservices.com Port 443</address> </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. 1 of them is known to be exploited.
CVEs by severity: CRITICAL 18 HIGH 40 MEDIUM 16
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.52 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.52 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.52 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.52 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.52 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.52 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.52 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.52 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.52 · port 80 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2023-27522 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.52 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.52 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.52 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.52 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.52 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.52 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.52 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.52 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.52 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.52 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.52 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.52 · 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: HIGH 2 MEDIUM 1
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.52 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.52 · 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.
3 names · as answered by each domain's own name servers