As of our latest check on 2026-06-09, 217.199.97.100 (SIA "BITE Latvija", AS20910, Latvia) had 2 open ports (80, 443) and 2 known CVEs, 1 known to be exploited.
Known CVEs on this host
2open ports
18names pointing here
2known CVEs
1known exploited
Open ports and CVEs as of our latest check of this host, 2026-06-09.
CVEs by severity: HIGH 1MEDIUM 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
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (2)
80/tcpHTTPnginx/1.24.02 CVEsfirst 2026-06-09 · last 2026-06-09
Status
200 OK
Title
Sorry - Site on maintenance
Server
nginx/1.24.0
Raw response
HTTP/1.1 200 OK
Server: nginx/1.24.0
Date: Tue, 09 Jun 2026 07:09:08 GMT
Content-Type: text/html
Content-Length: 234
Last-Modified: Wed, 18 Jan 2017 11:14:20 GMT
Connection: keep-alive
Keep-Alive: timeout=40
ETag: "587f4e0c-ea"
Accept-Ranges: bytes
<html>
<head><title>Sorry - Site on maintenance</title></head>
<body bgcolor="white">
<center><img alt="Maintenance Error" src="web-design.jpg"></center>
<center><h1>SORRY</h1><hr><h2>Site on Maintenance</h2></center>
</body>
</html>
443/tcpTLSfirst 2026-06-09 · last 2026-06-09
TLS
TLSv1.2
Certificate for
localhost
Issued by
localhost
Valid
2024-07-30 → 2034-07-28
Note
self-signed certificate
Raw response
HTTP/1.1 400 Bad Request
Server: nginx/1.24.0
Date: Tue, 09 Jun 2026 07:09:08 GMT
Content-Type: text/html
Content-Length: 255
Connection: close
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
<hr><center>nginx/1.24.0</center>
</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.
Hostnames pointing to this address
18 names · as answered by each domain's own name servers