- Banner
- 220 (vsFTPd 3.0.3)
Raw response
220 (vsFTPd 3.0.3)
Host
104.236.172.13
Tags: Cloud Hosting Expired certificate
As of our latest check on 2026-08-28, 104.236.172.13 (DigitalOcean, LLC, AS14061, United States) had 4 open ports (21, 22, 80, 443) and 6 known CVEs.
Known CVEs on this host
4open ports
0names pointing here
6known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-08-28.
CVEs by severity: HIGH 2 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: 149 on a distribution build — the fix may be backported (http_server 2.4.29, openssh 7.6p1). See them
Not counted: 4 only affect another platform (http_server 2.4.29). See them
- Network
- DigitalOcean, LLC AS14061
- Open ports
- 21, 22, 80, 443 · at our latest check, 2026-08-28
- Location
- United States US
- Hostname
- redso.mx · reverse DNS, checked 2026-10-04
- Route
- 104.236.128.0/18 · announced by DigitalOcean, LLC AS14061 RPKI valid
- Organisation
- DigitalOcean · Content / hosting
- Cloud
- DigitalOcean · region US-CA
- Registry network
- DIGITALOCEAN-104-236-0-0 · 104.236.0.0 - 104.236.255.255 · DigitalOcean, LLC · ARIN
- Abuse contact
- [email protected] · for DIGITALOCEAN-104-236-0-0
- First seen
- 2026-08-27 23:25 UTC
- Last seen alive
- 2026-08-28 04:41 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 (4)
- Server
- SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
- Host key
- ssh-ed25519 7ff61879c3a3ec6a…
Raw response
SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
80/tcp
HTTP
Apache/2.4.29 (Ubuntu)
first 2026-08-27 · last 2026-08-28
- Status
- 302 Found
- Server
- Apache/2.4.29 (Ubuntu)
Raw response
HTTP/1.1 302 Found Date: Fri, 28 Aug 2026 04:39:56 GMT Server: Apache/2.4.29 (Ubuntu) Location: http://www.redso.mx Content-Length: 0 Content-Type: text/html; charset=UTF-8
443/tcp
TLS
first 2026-08-27 · last 2026-08-28
- TLS
- TLSv1.2
- Certificate for
- www.redso.mx, redso.mx
- Issued by
- StartCom Class 1 Primary Intermediate Server CA
- Valid
- 2014-09-15 → 2015-09-16
Raw response
HTTP/1.1 400 Bad Request Date: Fri, 28 Aug 2026 04:39:56 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 437 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.29 (Ubuntu) Server at redso.mx Port 443</address> </body></html>
Vulnerabilities
Distribution build — the fix may be backported (149)
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. 3 of them are known to be exploited.
CVEs by severity: CRITICAL 25 HIGH 65 MEDIUM 46 LOW 13
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.29 · port 80 |
| CVE-2021-40438 CRITICAL 9.0 known exploited | http_server 2.4.29 · port 80 |
| CVE-2019-0211 HIGH 7.8 known exploited | http_server 2.4.29 · port 80 |
| CVE-2018-1312 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2021-26691 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2021-39275 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2021-44790 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 7.6p1 · port 22 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.29 · port 80 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 7.6p1 · port 22 |
| CVE-2019-10082 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.29 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 | http_server 2.4.29 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.29 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.29 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.29 · port 80 |
| CVE-2021-44224 HIGH 8.2 | http_server 2.4.29 · port 80 |
| CVE-2017-15715 HIGH 8.1 | http_server 2.4.29 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.29 · port 80 |
| CVE-2026-35385 HIGH 8.1 | openssh 7.6p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 7.6p1 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.29 · port 80 |
| CVE-2026-106583 HIGH 7.8 | openssh 7.6p1 · port 22 |
| CVE-2006-20001 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2017-15710 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2018-1303 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2018-1333 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2018-17199 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2019-0217 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2019-10081 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2019-9517 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-11993 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-9490 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2021-26690 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2021-33193 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2021-34798 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-22719 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-26377 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-29404 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2022-30556 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2023-31122 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-106553 HIGH 7.5 | openssh 7.6p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 7.6p1 · port 22 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-59999 HIGH 7.5 | openssh 7.6p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 7.6p1 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-15778 HIGH 7.4 | openssh 7.6p1 · port 22 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.29 · port 80 |
| CVE-2020-35452 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.29 · port 80 |
| CVE-2021-41617 HIGH 7.0 | openssh 7.6p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 7.6p1 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 7.6p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 7.6p1 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.29 · port 80 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 7.6p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 7.6p1 · port 22 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.29 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 7.6p1 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.29 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 7.6p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 7.6p1 · port 22 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.29 · port 80 |
| CVE-2019-10092 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2019-10098 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2020-1927 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.29 · port 80 |
| CVE-2018-11763 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2018-1301 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2018-1302 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 7.6p1 · port 22 |
| CVE-2023-45802 MEDIUM 5.9 | http_server 2.4.29 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 7.6p1 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.29 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.29 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 7.6p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 7.6p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 7.6p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 7.6p1 · port 22 |
| CVE-2018-1283 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2018-15919 MEDIUM 5.3 | openssh 7.6p1 · port 22 |
| CVE-2018-17189 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2019-0196 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2019-0220 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2019-17567 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2020-1934 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.29 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.29 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 7.6p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 7.6p1 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.29 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 7.6p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 7.6p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 7.6p1 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.29 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 7.6p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 7.6p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 7.6p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 7.6p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 7.6p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 7.6p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 7.6p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 7.6p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 7.6p1 · port 22 |
Only affects another platform (4)
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 2
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.29 · port 80 |
| CVE-2020-13938 MEDIUM 5.5 | http_server 2.4.29 · port 80 |
| CVE-2022-28330 MEDIUM 5.3 | http_server 2.4.29 · 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.