Host

217.181.200.47

As of our latest check on 2026-06-09, 217.181.200.47 (SEWAN SAS, AS8399, France) had 2 open ports (22, 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-09.

No known CVEs on this host.

Network: SEWAN SAS AS8399
Open ports: 22, 443 · at our latest check, 2026-06-09
Location: France FR
Route: 217.181.128.0/17 · announced by SEWAN SAS AS8399 RPKI valid
Organisation: Sewan SAS · Access network (cable / DSL / ISP)
Registry network: FR-SEWAN-20010302 · 217.181.128.0 - 217.181.255.255 · SEWAN SAS · RIPE
Abuse contact: [email protected] · for FR-SEWAN-20010302
First seen: 2026-06-09 04:36 UTC
Last seen alive: 2026-06-09 04: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 (2)

22/tcp SSH Zyxel first 2026-06-09 · last 2026-06-09

Server: SSH-2.0-Zyxel SSH server
Host key: ssh-rsa f50a97ee4a9465c0…

Raw response

SSH-2.0-Zyxel SSH server

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

TLS: TLSv1.0
Certificate for: usg100_0019CBFE6CE4
Issued by: usg100_0019CBFE6CE4
Valid: 2009-03-01 → 2029-02-24
Note: self-signed certificate

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://www.example.com/"><b>https://www.example.com/</b></a></blockquote></p>
<hr>
<address>  Server at www.example.com Port 443</address>
</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.

Report an issue with this page