Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (2)
80/tcpHTTPnginx/1.24.0 (Ubuntu)first 2026-08-27 · last 2026-08-27
Status
502 Bad Gateway
Title
502 Bad Gateway
Server
nginx/1.24.0 (Ubuntu)
Raw response
HTTP/1.1 502 Bad Gateway
Server: nginx/1.24.0 (Ubuntu)
Date: Thu, 27 Aug 2026 18:13:10 GMT
Content-Type: text/html
Content-Length: 568
Connection: keep-alive
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.24.0 (Ubuntu)</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
443/tcpHTTPnginx/1.24.0 (Ubuntu)first 2026-08-27 · last 2026-08-27
Status
502 Bad Gateway
Title
502 Bad Gateway
Server
nginx/1.24.0 (Ubuntu)
Raw response
HTTP/1.1 400 Bad Request
Server: nginx/1.24.0 (Ubuntu)
Date: Thu, 27 Aug 2026 18:13:11 GMT
Content-Type: text/html
Content-Length: 166
Connection: close
<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.24.0 (Ubuntu)</center>
</body>
</html>
Distribution build — the fix may be backported (2)
These CVEs were matched on software built by an operating-system distribution whose package revision the service does not show. Distributions often fix a flaw without changing the upstream version number, so whether this build is affected cannot be told from its version. They are not counted. 1 of them is known to be exploited.
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.