22/tcp
SSH
OpenSSH_8.7
first 2026-06-07 · last 2026-06-07
- Server
- SSH-2.0-OpenSSH_8.7
- Host key
- ssh-ed25519 13333c1542fe66f5…
Raw response
SSH-2.0-OpenSSH_8.7
Host
213.97.178.177
Tags: Expired certificate
As of our latest check on 2026-06-07, 213.97.178.177 (TELEFONICA DE ESPANA S.A.U., AS3352, Spain) had 3 open ports (22, 80, 443) and 102 known CVEs.
Known CVEs on this host
3open ports
0names pointing here
102known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-06-07.
CVEs by severity: CRITICAL 12 HIGH 46 MEDIUM 36 LOW 7 UNRATED 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 counted: 2 possible, version too vague to tell (python 3.9). See them
Not counted: 93 on a distribution build — the fix may be backported (http_server 2.4.62, openssh 8.7). See them
Not counted: 4 only affect another platform (python 3.9, http_server 2.4.62). See them
- Network
- TELEFONICA DE ESPANA S.A.U. AS3352
- Open ports
- 22, 80, 443 · at our latest check, 2026-06-07
- Location
- Spain ES
- Hostname
- 177.red-213-97-178.staticip.rima-tde.net · reverse DNS, checked 2026-10-05
- Route
- 213.97.0.0/16 · announced by TELEFONICA DE ESPANA S.A.U. AS3352 RPKI valid
- Organisation
- Telefonica de España · Access network (cable / DSL / ISP)
- Registry network
- RIMA · 213.97.176.0 - 213.97.179.255 · RIPE
- Abuse contact
- [email protected] · for RIMA
- First seen
- 2026-06-07 20:44 UTC
- Last seen alive
- 2026-06-07 20:44 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 (3)
80/tcp
HTTP
Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1 mod_wsgi/4.7.1 Python/3.9
102 CVEs
first 2026-06-07 · last 2026-06-07
- Status
- 200 OK
- Title
- www.leixa.com
- Server
- Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1 mod_wsgi/4.7.1 Python/3.9
Raw response
HTTP/1.1 200 OK
Date: Sun, 07 Jun 2026 20:44:14 GMT
Server: Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1 mod_wsgi/4.7.1 Python/3.9
Last-Modified: Wed, 14 Jul 2010 20:58:15 GMT
ETag: "49c-48b5f3e95c7c0"
Accept-Ranges: bytes
Content-Length: 1180
Content-Type: text/html; charset=UTF-8
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//ES">
<html>
<head>
<title>www.leixa.com</title>
</head>
<head><meta http-equiv="content-type" content="text/html; charset=UTF-8"><title>leixa.com</title>
<style><!--body,td,a,p,.h{font-family:arial,sans-serif;font-size:14}.q{color:#0000cc;}//--></style></head>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
<body
bgcolor="#FFFFFF"
text="#000000"
link="#0000FF"
vlink="#000080"
alink="#FF0000"
>
<h1 align="CENTER">
www.leixa.com
</h1>
<p>
Página en construcción. Disculpen las molestias.
<br>
</p>
</br>
<p>
<blockquote>
</blockquote>
<p>
443/tcp
TLS
first 2026-06-07 · last 2026-06-07
- TLS
- TLSv1.2
- Certificate for
- *.leixa.com
- Issued by
- ZeroSSL ECC DV SSL CA 2
- Valid
- 2026-05-22 → 2026-08-20
Raw response
HTTP/1.1 400 Bad Request Date: Sun, 07 Jun 2026 20:44:14 GMT Server: Apache/2.4.62 (AlmaLinux) OpenSSL/3.5.1 mod_wsgi/4.7.1 Python/3.9 Content-Length: 362 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> </body></html>
Vulnerabilities
Distribution build — the fix may be backported (93)
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 10 HIGH 43 MEDIUM 27 LOW 13
| CVE | Software |
|---|---|
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.7 · port 22 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.62 · port 80 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 8.7 · port 22 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.62 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.62 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.62 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.62 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.62 · port 80 |
| CVE-2024-6387 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-123158 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.62 · port 80 |
| CVE-2026-106583 HIGH 7.8 | openssh 8.7 · port 22 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-106553 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-59999 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.62 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.62 · port 80 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.7 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.7 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.62 · port 80 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.62 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.62 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.62 · port 80 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.7 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.62 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.62 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.7 · port 22 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.62 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.62 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.7 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 8.7 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.62 · port 80 |
| CVE-2025-32728 LOW 3.8 | openssh 8.7 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.7 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 8.7 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.62 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 8.7 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.7 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.7 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 8.7 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 8.7 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 8.7 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 8.7 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.7 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.7 · port 22 |
Only affects another platform (4)
These CVEs need a platform this host visibly does not run (for example a flaw of the Windows build on a Linux host). They are not counted.
CVEs by severity: HIGH 4
| CVE | Software |
|---|---|
| CVE-2018-25032 HIGH 7.5 | python 3.9 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.62 · port 80 |
| CVE-2026-3087 HIGH 7.5 | python 3.9 · port 80 |
| CVE-2022-26488 HIGH 7.0 | python 3.9 · port 80 |
Possible, version too vague to tell (2)
These CVEs were matched on a software version that names only a major release (such as “2”) or no version at all: whether the release running here is affected cannot be told. They are not counted anywhere on this site.
| CVE | Software |
|---|---|
| CVE-2020-15523 HIGH 7.8 | python 3.9 · port 80 |
| CVE-2022-48560 HIGH 7.5 | python 3.9 · port 80 |
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.