21/tcp
FTP
first 2026-08-27 · last 2026-08-27
- Banner
- 220 (vsFTPd 3.0.5)
Raw response
220 (vsFTPd 3.0.5)
Host
104.248.52.83
As of our latest check on 2026-08-27, 104.248.52.83 (DigitalOcean, LLC, AS14061, United States) had 4 open ports (21, 80, 443, 3306) and 2 known CVEs, 1 known to be exploited.
Known CVEs on this host
4open ports
0names pointing here
2known CVEs
1known exploited
Open ports and CVEs as of our latest check of this host, 2026-08-27.
CVEs by severity: HIGH 1 MEDIUM 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: 65 on a distribution build — the fix may be backported (mysql 8.0.42). See them
- Network
- DigitalOcean, LLC AS14061
- Open ports
- 21, 80, 443, 3306 · at our latest check, 2026-08-27
- Location
- United States US
- Hostname
- wimpykid.com · reverse DNS, checked 2026-10-04
- Route
- 104.248.48.0/20 · announced by DigitalOcean, LLC AS14061 RPKI valid
- Organisation
- DigitalOcean · Content / hosting
- Cloud
- DigitalOcean · region US-NJ
- Registry network
- DIGITALOCEAN-104-248-0-0 · 104.248.0.0 - 104.248.255.255 · DigitalOcean, LLC · ARIN
- Abuse contact
- [email protected] · for DIGITALOCEAN-104-248-0-0
- First seen
- 2026-08-27 21:32 UTC
- Last seen alive
- 2026-08-27 21:36 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)
- Status
- 200 OK
- Server
- nginx/1.22.1
Raw response
HTTP/1.1 200 OK Server: nginx/1.22.1 Date: Thu, 27 Aug 2026 21:33:10 GMT Content-Type: text/html Content-Length: 0 Last-Modified: Mon, 24 Oct 2022 08:25:21 GMT Connection: keep-alive ETag: "63564bf1-0" Accept-Ranges: bytes
443/tcp
TLS
first 2026-08-27 · last 2026-08-27
- TLS
- TLSv1.2
- Certificate for
- wimpykid.com, www.wimpykid.com
- Issued by
- USERTrust RSA Domain Validation Secure Server CA
- Valid
- 2021-11-19 → 2022-04-06
Raw response
HTTP/1.1 400 Bad Request Server: nginx/1.22.1 Date: Thu, 27 Aug 2026 21:33:10 GMT Content-Type: text/html Content-Length: 657 Connection: close X-Frame-Options: SAMEORIGIN <html> <head><title>400 The plain HTTP request was sent to HTTPS port</title></head> <body> <center><h1>400 Bad Request</h1></center> <center>The plain HTTP request was sent to HTTPS port</center> <hr><center>nginx/1.22.1</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page -->
3306/tcp
MYSQL
first 2026-08-27 · last 2026-08-27
- Protocol
- 8.0.42-0ubuntu0.20.04.1
Raw response
[ 8.0.42-0ubuntu0.20.04.1l�O.!(rbw�����[,* ^q;Cimysql_native_password
Vulnerabilities
Distribution build — the fix may be backported (65)
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: MEDIUM 60 LOW 5
| CVE | Software |
|---|---|
| CVE-2025-50076 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2025-50078 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2025-50082 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2025-50083 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-21968 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-22009 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-22017 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-34270 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-34271 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-34276 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-34303 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-34308 MEDIUM 6.5 | mysql 8.0.42 · port 3306 |
| CVE-2026-34318 MEDIUM 5.8 | mysql 8.0.42 · port 3306 |
| CVE-2025-50085 MEDIUM 5.5 | mysql 8.0.42 · port 3306 |
| CVE-2025-53053 MEDIUM 5.5 | mysql 8.0.42 · port 3306 |
| CVE-2025-53054 MEDIUM 5.5 | mysql 8.0.42 · port 3306 |
| CVE-2024-21176 MEDIUM 5.3 | mysql 8.0.42 · port 3306 |
| CVE-2026-34317 MEDIUM 5.0 | mysql 8.0.42 · port 3306 |
| CVE-2026-34319 MEDIUM 5.0 | mysql 8.0.42 · port 3306 |
| CVE-2025-50077 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50079 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50080 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50084 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50086 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50087 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50091 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50092 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50093 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50094 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50097 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50099 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50101 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50102 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53023 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53040 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53042 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53044 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53045 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53062 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-53069 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-21936 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-21937 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-21941 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-21948 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-21964 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-21998 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-22002 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-22004 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-22005 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-34267 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-34278 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-34293 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-34304 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-35236 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-35237 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-35238 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-35239 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2026-35240 MEDIUM 4.9 | mysql 8.0.42 · port 3306 |
| CVE-2025-50096 MEDIUM 4.4 | mysql 8.0.42 · port 3306 |
| CVE-2026-22015 MEDIUM 4.3 | mysql 8.0.42 · port 3306 |
| CVE-2025-50081 LOW 3.1 | mysql 8.0.42 · port 3306 |
| CVE-2025-50098 LOW 2.7 | mysql 8.0.42 · port 3306 |
| CVE-2025-50104 LOW 2.7 | mysql 8.0.42 · port 3306 |
| CVE-2026-22001 LOW 2.7 | mysql 8.0.42 · port 3306 |
| CVE-2025-50100 LOW 2.2 | mysql 8.0.42 · port 3306 |
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.