25/tcp
SMTP
first 2026-08-27 · last 2026-08-27
- Banner
- 220 ESMTP Postfix
Raw response
220 ESMTP Postfix 221 2.7.0 Error: I can break rules, too. Goodbye.
Host
104.232.11.196
Tags: Expired certificate
As of our latest check on 2026-08-27, 104.232.11.196 (ARPHost, LLC, AS401707, United States) had 3 open ports (25, 80, 443) and 19 known CVEs.
Known CVEs on this host
3open ports
0names pointing here
19known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-08-27.
CVEs by severity: CRITICAL 3 HIGH 12 MEDIUM 3 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: 46 on a distribution build — the fix may be backported (http_server 2.4.58). See them
Not counted: 2 only affect another platform (http_server 2.4.58). See them
- Network
- ARPHost, LLC AS401707
- Open ports
- 25, 80, 443 · at our latest check, 2026-08-27
- Location
- United States US
- Hostname
- host-104-232-11-196.fac-tpa1.static.arphost.com · reverse DNS, checked 2026-10-04
- Route
- 104.232.11.0/24 · announced by ARPHost, LLC AS401707 RPKI valid
- Organisation
- ARPHost, LLC · Network service provider (transit)
- First seen
- 2026-08-27 22:32 UTC
- Last seen alive
- 2026-08-27 22:35 UTC
- Hosted domains
- No host name points here
Reputation
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (3)
- Status
- 500 Internal Server Error
- Title
- 4Guard VPN | 4Guard IDPS | 4Guard MXCleaner | Core4 Technologies
- Server
- Apache/2.4.58 (Ubuntu)
Raw response
HTTP/1.0 500 Internal Server Error Date: Thu, 27 Aug 2026 22:32:53 GMT Server: Apache/2.4.58 (Ubuntu) Content-Length: 4024 Connection: close Content-Type: text/html; charset=UTF-8 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title> 4Guard VPN | 4Guard IDPS | 4Guard MXCleaner | Core4 Technologies </title> <meta name="keywords" content="network design, network implementation, network support, network monitoring, network security, personal vpn service, personal vpn services, network cabling, network cables" /> <meta name="description" content="4Guard personal VPN and business VPN services, also network design, implementation and network security services" /> <link href="https://www.core4tech.com/css/bootstrap.css" rel="stylesheet" type="text/css" /> <li
443/tcp
TLS
first 2026-08-27 · last 2026-08-27
- TLS
- TLSv1.2
- Certificate for
- *.core4tech.com, core4tech.com
- Issued by
- R10
- Valid
- 2025-05-08 → 2025-08-06
Raw response
HTTP/1.1 400 Bad Request Date: Thu, 27 Aug 2026 22:32:53 GMT Server: Apache/2.4.58 (Ubuntu) Content-Length: 441 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.58 (Ubuntu) Server at core4tech.com Port 80</address> </body></html>
Vulnerabilities
Distribution build — the fix may be backported (46)
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 8 HIGH 26 MEDIUM 12
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.58 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.58 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.58 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.58 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.58 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.58 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.58 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.58 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.58 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.58 · port 80 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4.58 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.58 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.58 · port 80 |
Only affects another platform (2)
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
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.58 · port 80 |
Port history
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.