105.25.112.7 — 1 open port, 0 known CVEs, network SEACOM Limited

Known CVEs on this host

1open port

1name pointing here

0known CVEs

0known exploited

Open ports and CVEs as of our latest check of this host, 2026-05-31.

No known CVEs on this host.

Network: SEACOM Limited AS37100
Open ports: 443 · at our latest check, 2026-05-31
Location: United Kingdom GB
Hostname: monitoring.cloud.nbo.ke.seacomnet.com · reverse DNS, checked 2026-10-04
Route: 105.16.0.0/12 · announced by SEACOM Limited AS37100 no RPKI authorisation
Organisation: SEACOM Limited · Network service provider (transit)
Registry network: SEACOM-ASSIGNMENTS-CUSTOMERS · 105.25.96.0 - 105.25.127.255 · AFRINIC
First seen: 2026-05-31 10:33 UTC
Last seen alive: 2026-05-31 10:39 UTC
Hosted domains: 1 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-05-31 · last 2026-05-31

TLS: TLSv1.2
Certificate for: monitoring.cloud.nbo.ke.seacomnet.com
Issued by: YE2
Valid: 2026-05-31 → 2026-08-29

Raw response

HTTP/1.1 400 Bad Request
Date: Sun, 31 May 2026 10:35:45 GMT
Server: Apache/2.4.58 (Ubuntu)
Content-Length: 465
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>
<hr>
<address>Apache/2.4.58 (Ubuntu) Server at monitoring.cloud.nbo.ke.seacomnet.com Port 80</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.

Hostnames pointing to this address

1 name · as answered by each domain's own name servers

monitoring.cloud.nbo.ke.seacomnet.comfirst seen 2026-10-19

Report an issue with this page