Host

213.183.63.97

Tags: Hosting Expired certificate

As of our latest check on 2026-06-08, 213.183.63.97 (Melbikomas UAB, AS56630, Bulgaria) had 2 open ports (22, 443) and 37 known CVEs, 1 known to be exploited.

Known CVEs on this host

2open ports
0names pointing here
37known CVEs
1known exploited

Open ports and CVEs as of our latest check of this host, 2026-06-08.

CVEs by severity: CRITICAL 1 HIGH 14 MEDIUM 13 LOW 9

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

6 of them on a software version from an earlier observation: a service of that kind is open now.

Not counted: 2 on a distribution build — the fix may be backported (openssh 9.6p1). See them

Network
Melbikomas UAB AS56630
Open ports
22, 443 · at our latest check, 2026-06-08
Location
Bulgaria BG
Hostname
free.ds.melbicom.net · reverse DNS, checked 2026-10-05
Route
213.183.63.0/24 · announced by Melbikomas UAB AS56630 RPKI valid
Organisation
Melbikomas UAB · Content / hosting
Registry network
MELBICOM-BG · 213.183.63.0 - 213.183.63.255 · Melbikomas UAB · RIPE
Abuse contact
[email protected] · for MELBICOM-BG
Hostnames
free.ds.melbicom.net, telegram.org
First seen
2026-06-08 02:02 UTC
Last seen alive
2026-06-08 02:03 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 OpenSSH_9.6p1 31 CVEs first 2026-06-08 · last 2026-06-08
Server
SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13
Host key
ssh-rsa 6cae1e8ea3326676…
Raw response
SSH-2.0-OpenSSH_9.6p1 Ubuntu-3ubuntu13
443/tcp TLS nginx 1.18.0 6 CVEs first 2026-06-08 · last 2026-06-08
TLS
TLSv1.2
Certificate for
*.telegram.org, telegram.org
Issued by
Go Daddy Secure Certificate Authority - G2
Valid
2025-08-11 → 2026-09-12
Raw response
HTTP/1.1 400 Bad Request
Server: nginx/1.30.1
Date: Mon, 08 Jun 2026 02:02:47 GMT
Content-Type: text/html
Content-Length: 657
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.30.1</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 -->

Vulnerabilities

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.

CVEs by severity: LOW 2

CVESoftware
CVE-2026-106588 LOW 3.1 openssh 9.6p1 · port 22
CVE-2026-106589 LOW 2.9 openssh 9.6p1 · port 22

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.