Host
Tags: Hosting Self-signed certificate Expired certificate End-of-life software
As of our latest check on 2026-06-09, 217.172.179.131 (velia.net Internetdienste GmbH, AS29066, France) had 2 open ports (22, 443) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-06-09.
No known CVEs now
Not counted: 62 on a distribution build — the fix may be backported (openssh 5.9p1). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.10
<!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 /> <blockquote>Hint: <a href="https://default-217_172_179_131/"><b>https://default-217_172_179_131/</b></a></blockquote></p> <hr> <address>Apache Server at default-217_172_179_131 Port 443</address> </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 2 HIGH 16 MEDIUM 29 LOW 15
| CVE | Software |
|---|---|
| CVE-2016-1908 CRITICAL 9.8 | openssh 5.9p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 5.9p1 · port 22 |
| CVE-2015-5600 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2016-0778 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 5.9p1 · port 22 |
| CVE-2015-8325 HIGH 7.8 | openssh 5.9p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 5.9p1 · port 22 |
| CVE-2026-60002 HIGH 7.7 | openssh 5.9p1 · port 22 |
| CVE-2010-5107 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2016-10708 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2016-6515 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 5.9p1 · port 22 |
| CVE-2020-15778 HIGH 7.4 | openssh 5.9p1 · port 22 |
| CVE-2014-1692 HIGH 7.3 | openssh 5.9p1 · port 22 |
| CVE-2016-10009 HIGH 7.3 | openssh 5.9p1 · port 22 |
| CVE-2015-6564 HIGH 7.0 | openssh 5.9p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 5.9p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 5.9p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 5.9p1 · port 22 |
| CVE-2014-2653 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2016-0777 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 5.9p1 · port 22 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 5.9p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 5.9p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 5.9p1 · port 22 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2026-59999 MEDIUM 5.9 | openssh 5.9p1 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 5.9p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 5.9p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 5.9p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2018-15473 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2018-15919 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 5.9p1 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 5.9p1 · port 22 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 5.9p1 · port 22 |
| CVE-2014-2532 MEDIUM 4.2 | openssh 5.9p1 · port 22 |
| CVE-2026-106552 MEDIUM 4.2 | openssh 5.9p1 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 5.9p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 5.9p1 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 5.9p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 5.9p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 5.9p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 5.9p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 5.9p1 · port 22 |
| CVE-2026-106583 LOW 2.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106584 LOW 2.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106586 LOW 2.5 | openssh 5.9p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 5.9p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 5.9p1 · port 22 |
| CVE-2026-106553 LOW 2.2 | openssh 5.9p1 · port 22 |
| CVE-2026-106555 LOW 2.2 | openssh 5.9p1 · port 22 |
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.
3 names · as answered by each domain's own name servers