Host

217.136.171.190

As of our latest check on 2026-06-09, 217.136.171.190 (Proximus NV, AS5432, Belgium) had 1 open port (443) and no known CVEs.

Known CVEs on this host

1open port

0names pointing here

0known CVEs

0known exploited

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

No known CVEs on this host.

Network: Proximus NV AS5432
Open ports: 443 · at our latest check, 2026-06-09
Location: Belgium BE
Hostname: 190.171-136-217.adsl-static.isp.belgacom.be · reverse DNS, checked 2026-10-05
Route: 217.136.0.0/16 · announced by Proximus NV AS5432 RPKI valid
Organisation: Proximus NV · Access network (cable / DSL / ISP)
Registry network: BE-SKYNET-20011108 · 217.136.171.0 - 217.136.171.255 · RIPE
Abuse contact: [email protected] · for BE-SKYNET-20011108
First seen: 2026-06-09 03:50 UTC
Last seen alive: 2026-06-09 03:50 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 (1)

443/tcp TLS first 2026-06-09 · last 2026-06-09

TLS: TLSv1.2
Certificate for: *.triangle-trading.be, triangle-trading.be
Issued by: Trust Provider B.V. TLS RSA CA G1
Valid: 2025-07-09 → 2026-07-20

Raw response

@Mj'�n2��#&���>�C���^+�:x Z=84�
��e�����=�5��p���8�э��/����0��0�x��rOn�G�g��:&0
	*�H��
0v10	UNL10U
Trust Provider B.V.10UDomain Validated SSL1*0(U!Trust Provider B.V. TLS RSA CA G10
250709000000Z
260720235959Z0 10U*.triangle-trading.be0�"0
	*�H��
�0�
��ެ~����a�$3`�{�(K޼Q���S�`�!M7��$jO�����R�{��X\	��3`g���r������>Q��p�2Uf�01]�7�c���9��l�U�C�������n%��>�:�][
���T"Zp�����>L\�Y�<
���%/R�\��Ԥ��>��J5a���-�UF�^�4�����*ޭ�H���BY��Y�gp�e�ނ��\5Rח����7�:Sm[���z5����l�06Wc�p�(K���8�XkF9��n0�j0U#0��V"ٿkY$R��j���Wg��0U���\�Bk���-�l<�nG�05U.0,�*.triangle-trading.be�triangle-trading.be0>U 70503g�0)0'+http://www.digicert.com/CPS0U�...<truncated>

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