Host

217.11.131.10

As of our latest check on 2026-06-08, 217.11.131.10 (Timplus sp. z o.o., AS50349, Poland) had 2 open ports (80, 443) and no known CVEs.

Known CVEs on this host

2open ports
0names pointing here
0known CVEs
0known exploited

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

No known CVEs on this host.

Network
Timplus sp. z o.o. AS50349
Open ports
80, 443 · at our latest check, 2026-06-08
Location
Poland PL
Hostname
ip10.radiorsc.pl · reverse DNS, checked 2026-10-05
Route
217.11.128.0/22 · announced by Timplus sp. z o.o. AS50349 RPKI valid
Organisation
Radoslaw Walentowski
Registry network
PL-TIMPLUS-CUSTOMERS · 217.11.128.0 - 217.11.131.255 · RIPE
Abuse contact
[email protected] · for PL-TIMPLUS-CUSTOMERS
First seen
2026-06-08 04:53 UTC
Last seen alive
2026-06-08 04:54 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 first 2026-06-08 · last 2026-06-08
Status
302 Found
Title
302 Found
Server
Apache
Raw response
HTTP/1.1 302 Found
Date: Mon, 08 Jun 2026 05:33:32 GMT
Server: Apache
Location: https://217.11.131.10/
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1

ca 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="https://217.11.131.10/">here</A>.<P>
</BODY></HTML>

0
443/tcp TLS first 2026-06-08 · last 2026-06-08
TLS
TLSv1.0
Certificate for
*.digigram.com
Issued by
digigram.com
Valid
2016-05-12 → 2041-05-06
Raw response
HTTP/1.1 400 Bad Request
Date: Mon, 08 Jun 2026 05:33:32 GMT
Server: Apache
WWW-Authenticate: Basic realm="Digigram Iqoya*Link"
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>
Your browser sent a request that this server could not understand.<P>
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://217.11.131.10:443/"><B>https://217.11.131.10:443/</B></A></BLOCKQUOTE><P>
<P>Additionally, a 401 Authorization Required
error was encountered while trying to use an ErrorDocument to handle the request.
</BODY></HTML>

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.