Host

103.241.129.36

Tags: Hosting Database Expired certificate End-of-life software

As of our latest check on 2026-08-26, 103.241.129.36 (IDC Frontier Inc., AS4694, Japan) had 5 open ports (21, 22, 443, 3306, 8443) and 315 known CVEs.

Known CVEs on this host

5open ports
0names pointing here
315known CVEs
0known exploited

Open ports and CVEs as of our latest check of this host, 2026-08-26.

CVEs by severity: CRITICAL 10 HIGH 50 MEDIUM 196 LOW 59

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: 3 only affect a particular platform; this host's is not known (openssh 4.3, mysql 5.0.95). See them

Network
IDC Frontier Inc. AS4694
Open ports
21, 22, 443, 3306, 8443 · at our latest check, 2026-08-26
Location
Japan JP
Route
103.241.128.0/22 · announced by IDC Frontier Inc. AS4694 no RPKI authorisation
Organisation
IDC Frontier Inc. · Content / hosting
Registry network
RIDE-INFLA · 103.241.128.0 - 103.241.131.255 · APNIC
Abuse contact
[email protected] · for RIDE-INFLA
First seen
2026-08-26 01:17 UTC
Last seen alive
2026-08-26 12:26 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 (5)

21/tcp FTP proftpd 1.3.3e 19 CVEs first 2026-08-26 · last 2026-08-26
Banner
220 ProFTPD 1.3.3e Server (ProFTPD) [103.241.129.36]
Raw response
220 ProFTPD 1.3.3e Server (ProFTPD) [103.241.129.36]
22/tcp SSH OpenSSH_4.3 71 CVEs first 2026-08-26 · last 2026-08-26
Server
SSH-2.0-OpenSSH_4.3
Host key
ssh-rsa 623efa9dd5b8773c…
Raw response
SSH-2.0-OpenSSH_4.3
443/tcp TLS first 2026-08-26 · last 2026-08-26
TLS
TLSv1.0
Certificate for
www.daikyo-d.co.jp, daikyo-d.co.jp
Issued by
AlphaSSL CA - SHA256 - G2
Valid
2022-09-20 → 2023-10-22
Raw response
<!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 />
<blockquote>Hint: <a href="https://default-103_241_129_36/"><b>https://default-103_241_129_36/</b></a></blockquote></p>
<hr>
<address>Apache Server at default-103_241_129_36 Port 443</address>
</body></html>
3306/tcp MYSQL mysql 5.0.95 225 CVEs first 2026-08-26 · last 2026-08-26
Protocol
5.0.95
Raw response
4
5.0.95�i~<rJ\n7ds,�6OkO'q*zH8~7
8443/tcp HTTP sw-cp-server first 2026-08-26 · last 2026-08-26
Status
200 OK
Server
sw-cp-server
Raw response
HTTP/1.0 302 Found
Connection: close
Location: https://bs028-303.domainserver.ne.jp:8443/
Content-Length: 0
Date: Wed, 26 Aug 2026 12:24:57 GMT
Server: sw-cp-server

Vulnerabilities

Only affects certain platforms (3)

These CVEs only apply when the software runs on a particular platform (for example Windows), and this host's platform is not known. They are not counted.

CVEs by severity: HIGH 1 MEDIUM 2

CVESoftware
CVE-2017-15945 HIGH 7.8 mysql 5.0.95 · port 3306
CVE-2009-2904 MEDIUM 6.9 openssh 4.3 · port 22
CVE-2008-4109 MEDIUM 5.0 openssh 4.3 · port 22

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.