Host

217.118.35.100

Tags: Self-signed certificate Expired certificate

As of our latest check on 2026-06-09, 217.118.35.100 (GLOBALCONNECT AS, AS2116, Norway) 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
GLOBALCONNECT AS AS2116
Open ports
443 · at our latest check, 2026-06-09
Location
Norway NO
Route
217.118.32.0/19 · announced by GLOBALCONNECT AS AS2116 RPKI valid
Organisation
GlobalConnect Group · Access network (cable / DSL / ISP)
Registry network
NO-GLOBALCONNECT-20010212 · 217.118.32.0 - 217.118.63.255 · GLOBALCONNECT AS · RIPE
Abuse contact
[email protected] · for NO-GLOBALCONNECT-20010212
First seen
2026-02-10 12:41 UTC
Last seen alive
2026-06-09 01:02 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
zywall_110_A0E4CB7DCAB0
Issued by
zywall_110_A0E4CB7DCAB0
Valid
2015-02-27 → 2025-02-24
Note
self-signed certificate
Raw response
HTTP/1.1 400 Bad Request
Date: Tue, 09 Jun 2026 01:01:33 GMT
Content-Length: 362
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>
</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.