22/tcp
SSH
OpenSSH_6.7p1
first 2026-06-08 · last 2026-06-08
- Server
- SSH-2.0-OpenSSH_6.7p1 Debian-5
- Host key
- ssh-ed25519 a1df2efd0eebebcf…
Raw response
SSH-2.0-OpenSSH_6.7p1 Debian-5
Host
217.23.12.57
Tags: Hosting Expired certificate End-of-life software
As of our latest check on 2026-06-08, 217.23.12.57 (WorldStream B.V., AS49981, Netherlands) had 3 open ports (22, 80, 443) and no known CVEs.
Known CVEs on this host
3open ports
0names pointing here
0known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-06-08.
No known CVEs now
Not counted: 105 on a distribution build — the fix may be backported (openssh 6.7p1, http_server 2.4.65). See them
Not counted: 2 fixed by the distribution (http_server 2.4.65). See them
- Network
- WorldStream B.V. AS49981
- Open ports
- 22, 80, 443 · at our latest check, 2026-06-08
- Location
- Netherlands NL
- Hostname
- customer.worldstream.nl · reverse DNS, checked 2026-10-05
- Route
- 217.23.0.0/20 · announced by WorldStream B.V. AS49981 RPKI valid
- Organisation
- Worldstream B.V. · Network Services
- Registry network
- WORLDSTREAM · 217.23.12.0 - 217.23.12.255 · RIPE
- Abuse contact
- [email protected] · for WORLDSTREAM
- First seen
- 2026-06-08 06:33 UTC
- Last seen alive
- 2026-06-08 06:34 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.65 (Debian)
first 2026-06-08 · last 2026-06-08
- Status
- 301 Moved Permanently
- Title
- 301 Moved Permanently
- Server
- Apache/2.4.65 (Debian)
Raw response
HTTP/1.1 301 Moved Permanently Date: Mon, 08 Jun 2026 06:33:22 GMT Server: Apache/2.4.65 (Debian) Location: https://217.23.12.57/ Content-Length: 307 Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>301 Moved Permanently</title> </head><body> <h1>Moved Permanently</h1> <p>The document has moved <a href="https://217.23.12.57/">here</a>.</p> <hr> <address>Apache/2.4.65 (Debian) Server at 217.23.12.57 Port 80</address> </body></html>
443/tcp
TLS
first 2026-06-08 · last 2026-06-08
- TLS
- TLSv1.2
- Certificate for
- omnomnom.nerp.net
- Issued by
- R12
- Valid
- 2026-05-07 → 2026-08-05
Raw response
HTTP/1.1 400 Bad Request Date: Mon, 08 Jun 2026 06:33:22 GMT Server: Apache/2.4.65 (Debian) Content-Length: 445 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.65 (Debian) Server at omnomnom.nerp.net Port 80</address> </body></html>
Distribution build — the fix may be backported (105)
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 40 LOW 12
| CVE | Software |
|---|---|
| CVE-2016-1908 CRITICAL 9.8 | openssh 6.7p1 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 6.7p1 · port 22 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.65 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.65 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.65 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.65 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.65 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.65 · port 80 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 6.7p1 · port 22 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.65 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.65 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.65 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.65 · port 80 |
| CVE-2015-5600 HIGH 8.1 | openssh 6.7p1 · port 22 |
| CVE-2016-0778 HIGH 8.1 | openssh 6.7p1 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 6.7p1 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 6.7p1 · port 22 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.65 · port 80 |
| CVE-2015-8325 HIGH 7.8 | openssh 6.7p1 · port 22 |
| CVE-2016-10012 HIGH 7.8 | openssh 6.7p1 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 6.7p1 · port 22 |
| CVE-2016-10708 HIGH 7.5 | openssh 6.7p1 · port 22 |
| CVE-2016-6515 HIGH 7.5 | openssh 6.7p1 · port 22 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-106553 HIGH 7.5 | openssh 6.7p1 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 6.7p1 · port 22 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-46729 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-47360 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-48005 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-56153 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-56449 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-59999 HIGH 7.5 | openssh 6.7p1 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 6.7p1 · port 22 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2020-15778 HIGH 7.4 | openssh 6.7p1 · port 22 |
| CVE-2016-10009 HIGH 7.3 | openssh 6.7p1 · port 22 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.65 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.65 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.65 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.65 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.65 · port 80 |
| CVE-2015-6564 HIGH 7.0 | openssh 6.7p1 · port 22 |
| CVE-2016-10010 HIGH 7.0 | openssh 6.7p1 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 6.7p1 · port 22 |
| CVE-2019-6109 MEDIUM 6.8 | openssh 6.7p1 · port 22 |
| CVE-2019-6110 MEDIUM 6.8 | openssh 6.7p1 · port 22 |
| CVE-2016-0777 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.65 · port 80 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.65 · port 80 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.65 · port 80 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 6.7p1 · port 22 |
| CVE-2015-6563 MEDIUM 6.4 | openssh 6.7p1 · port 22 |
| CVE-2016-3115 MEDIUM 6.4 | openssh 6.7p1 · port 22 |
| CVE-2016-10011 MEDIUM 6.2 | openssh 6.7p1 · port 22 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.65 · port 80 |
| CVE-2016-6210 MEDIUM 5.9 | openssh 6.7p1 · port 22 |
| CVE-2019-6111 MEDIUM 5.9 | openssh 6.7p1 · port 22 |
| CVE-2020-14145 MEDIUM 5.9 | openssh 6.7p1 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 6.7p1 · port 22 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.65 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.65 · port 80 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 6.7p1 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 6.7p1 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 6.7p1 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 6.7p1 · port 22 |
| CVE-2017-15906 MEDIUM 5.3 | openssh 6.7p1 · port 22 |
| CVE-2018-15473 MEDIUM 5.3 | openssh 6.7p1 · port 22 |
| CVE-2018-15919 MEDIUM 5.3 | openssh 6.7p1 · port 22 |
| CVE-2018-20685 MEDIUM 5.3 | openssh 6.7p1 · port 22 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.65 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.65 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.65 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.65 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.65 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.65 · port 80 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 6.7p1 · port 22 |
| CVE-2015-5352 MEDIUM 4.3 | openssh 6.7p1 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 6.7p1 · port 22 |
| CVE-2026-42528 MEDIUM 4.3 | http_server 2.4.65 · port 80 |
| CVE-2021-36368 LOW 3.7 | openssh 6.7p1 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 6.7p1 · port 22 |
| CVE-2026-42356 LOW 3.7 | http_server 2.4.65 · port 80 |
| CVE-2025-61984 LOW 3.6 | openssh 6.7p1 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 6.7p1 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 6.7p1 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 6.7p1 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 6.7p1 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 6.7p1 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 6.7p1 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 6.7p1 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 6.7p1 · port 22 |
Fixed by the distribution (2)
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 2
| CVE | Software |
|---|---|
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.65 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.65 · 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.