Host

117.55.203.188

As of our latest check on 2026-05-31, 117.55.203.188 (PUSHPKT OU, AS3920, Netherlands) had 2 open ports (80, 443) and 80 known CVEs, 1 known to be exploited.

Known CVEs on this host

2open ports

0names pointing here

80known CVEs

1known exploited

Open ports and CVEs as of our latest check of this host, 2026-05-31.

CVEs by severity: CRITICAL 13 HIGH 43 MEDIUM 23 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

Network: PUSHPKT OU AS3920
Open ports: 80, 443 · at our latest check, 2026-05-31
Location: Netherlands NL
Route: 117.55.203.0/24 · announced by ESTOXY OU AS61254 no RPKI authorisation
Organisation: ESTOXY OU · Content / hosting
Registry network: ESTOXY-NL-EX1-DSRV-02 · 117.55.203.0 - 117.55.203.255 · ESTOXY OU · RIPE
Abuse contact: [email protected] · for ESTOXY-NL-EX1-DSRV-02
First seen: 2026-05-31 21:50 UTC
Last seen alive: 2026-05-31 21:51 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 (2)

80/tcp HTTP Apache/2.4.58 (Win64) OpenSSL/3.1.3 80 CVEs first 2026-05-31 · last 2026-05-31

Status: 200 OK
Server: Apache/2.4.58 (Win64) OpenSSL/3.1.3

Raw response

HTTP/1.1 200 OK
Date: Sun, 31 May 2026 21:50:41 GMT
Server: Apache/2.4.58 (Win64) OpenSSL/3.1.3
Content-Length: 0
Content-Type: text/html; charset=UTF-8

443/tcp TLS first 2026-05-31 · last 2026-05-31

TLS: TLSv1.2
Certificate for: cs-16.duckdns.org
Issued by: E7
Valid: 2026-05-10 → 2026-08-08

Raw response

HTTP/1.1 400 Bad Request
Date: Sun, 31 May 2026 21:50:41 GMT
Server: Apache/2.4.58 (Win64) OpenSSL/3.1.3
Content-Length: 457
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 (Win64) OpenSSL/3.1.3 Server at www.example.com Port 443</address>
</body></html>

Vulnerabilities

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.

Report an issue with this page