Host
Tags: Expired certificate
As of our latest check on 2026-05-23, 80.95.30.21 (Telecoms-Net Ltd., AS16154, Bulgaria) had 2 open ports (80, 443) and 4 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-05-23.
CVEs by severity: HIGH 1 MEDIUM 3
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 counted: 32 on a distribution build — the fix may be backported (http_server 2.4.67). See them
Not counted: 1 fixed by the distribution (http_server 2.4.67). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
HTTP/1.1 200 OK Date: Sat, 23 May 2026 14:02:18 GMT Server: Apache/2.4.67 (Debian) OpenSSL/1.1.1w Last-Modified: Wed, 01 Feb 2012 15:46:07 GMT ETag: "0-4b7e8fa54cdc0" Accept-Ranges: bytes Content-Length: 0 Content-Type: text/html
HTTP/1.1 400 Bad Request Date: Sat, 23 May 2026 14:02:18 GMT Server: Apache/2.4.67 (Debian) OpenSSL/1.1.1w Content-Length: 402 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <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>
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: CRITICAL 6 HIGH 19 MEDIUM 6 LOW 1
| CVE | Software |
|---|---|
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.67 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.67 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.67 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.67 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.67 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.67 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.67 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.67 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.67 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.67 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.67 · port 80 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.67 · port 80 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.67 · port 80 |
The distribution's security data says the package revision this service shows already has the fix for these CVEs, or that its build is not affected. They are not counted.
CVEs by severity: HIGH 1
| CVE | Software |
|---|---|
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.67 · port 80 |
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.
1 name · as answered by each domain's own name servers