217.6.8.91 — 2 open ports, 0 known CVEs, network Deutsche Telekom AG

Known CVEs on this host

2open 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: 75 on a distribution build — the fix may be backported (http_server 2.4.59, openssl 1.1.1n). See them

Not counted: 4 fixed by the distribution (http_server 2.4.59, openssl 1.1.1n). See them

Not counted: 2 only affect another platform (http_server 2.4.59). See them

Network: Deutsche Telekom AG AS3320
Open ports: 80, 443 · at our latest check, 2026-06-08
Location: Hausach, DE-BW · Germany DE
Hostname: mail.r-neumayer.de · reverse DNS, checked 2026-10-05
Route: 217.0.0.0/13 · announced by Deutsche Telekom AG AS3320 RPKI valid
Organisation: Deutsche Telekom AG · Network service provider (transit)
Registry network: RICHARDNEUMAYER-HAUSACH-NET · 217.6.8.88 - 217.6.8.95 · RIPE
Abuse contact: [email protected] · for RICHARDNEUMAYER-HAUSACH-NET
First seen: 2026-06-08 05:46 UTC
Last seen alive: 2026-06-08 05:46 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)

80/tcp HTTP Apache/2.4.59 (Debian) OpenSSL/1.1.1n first 2026-06-08 · last 2026-06-08

Status: 503 Service Unavailable
Title: Error 503 Service Unavailable
Server: Apache/2.4.59 (Debian) OpenSSL/1.1.1n

Raw response

HTTP/1.1 503 Service Unavailable
Date: Mon, 08 Jun 2026 05:46:21 GMT
Server: Apache/2.4.59 (Debian) OpenSSL/1.1.1n
Retry-After: 18000
Last-Modified: Sat, 28 Feb 2026 18:57:43 GMT
ETag: "11f-64be6edb6b7c0"
Accept-Ranges: bytes
Content-Length: 287
Connection: close
Content-Type: text/html

<!DOCTYPE html>
<html>
<head>
<title>Error 503 Service Unavailable</title>
</head>
<body>
<h1>503 Service Unavailable</h1>
Our apologies for the temporary inconvenience. The requested URL generated 503 "Service Unavailable" error due to overloading or maintenance of the server.
</body>

443/tcp TLS first 2026-06-08 · last 2026-06-08

TLS: TLSv1.2
Certificate for: *.r-neumayer.net, r-neumayer.net
Issued by: Certum DV TLS G2 R39 CA
Valid: 2025-10-28 → 2026-10-28

Raw response

HTTP/1.1 400 Bad Request
Date: Mon, 08 Jun 2026 05:46:21 GMT
Server: Apache/2.4.59 (Debian) OpenSSL/1.1.1n
Retry-After: 18000
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>

Distribution build — the fix may be backported (75)

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. 1 of them is known to be exploited.

CVEs by severity: CRITICAL 11 HIGH 40 MEDIUM 23 LOW 1

CVE	Software
CVE-2024-38475 CRITICAL 9.1 known exploited	http_server 2.4.59 · port 80
CVE-2024-38474 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2024-38476 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2026-28780 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2026-29167 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2026-44631 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2026-56154 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2026-57941 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2026-59797 CRITICAL 9.8	http_server 2.4.59 · port 80
CVE-2025-23048 CRITICAL 9.1	http_server 2.4.59 · port 80
CVE-2026-42535 CRITICAL 9.1	http_server 2.4.59 · port 80
CVE-2026-24072 HIGH 8.8	http_server 2.4.59 · port 80
CVE-2026-93546 HIGH 8.8	http_server 2.4.59 · port 80
CVE-2025-58098 HIGH 8.3	http_server 2.4.59 · port 80
CVE-2024-38473 HIGH 8.1	http_server 2.4.59 · port 80
CVE-2026-73636 HIGH 8.1	http_server 2.4.59 · port 80
CVE-2022-4450 HIGH 7.5	openssl 1.1.1n · port 80
CVE-2023-0215 HIGH 7.5	openssl 1.1.1n · port 80
CVE-2023-0464 HIGH 7.5	openssl 1.1.1n · port 80
CVE-2024-38477 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2024-39573 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2024-42516 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2024-43204 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2024-47252 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2024-4741 HIGH 7.5	openssl 1.1.1n · port 80
CVE-2025-49630 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2025-53020 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2025-55753 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-29169 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-34059 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-34355 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-34356 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-42536 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-46729 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-48005 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-49975 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-56153 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-56449 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-63045 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-63292 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-63686 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-63718 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2023-0286 HIGH 7.4	openssl 1.1.1n · port 80
CVE-2025-49812 HIGH 7.4	http_server 2.4.59 · port 80
CVE-2022-1292 HIGH 7.3	openssl 1.1.1n · port 80
CVE-2022-2068 HIGH 7.3	openssl 1.1.1n · port 80
CVE-2026-29168 HIGH 7.3	http_server 2.4.59 · port 80
CVE-2026-44185 HIGH 7.3	http_server 2.4.59 · port 80
CVE-2026-44186 HIGH 7.3	http_server 2.4.59 · port 80
CVE-2026-48913 HIGH 7.3	http_server 2.4.59 · port 80
CVE-2026-73637 HIGH 7.3	http_server 2.4.59 · port 80
CVE-2023-2650 MEDIUM 6.5	openssl 1.1.1n · port 80
CVE-2025-65082 MEDIUM 6.5	http_server 2.4.59 · port 80
CVE-2026-33523 MEDIUM 6.5	http_server 2.4.59 · port 80
CVE-2026-43951 MEDIUM 6.5	http_server 2.4.59 · port 80
CVE-2026-29170 MEDIUM 6.1	http_server 2.4.59 · port 80
CVE-2022-4304 MEDIUM 5.9	openssl 1.1.1n · port 80
CVE-2024-2511 MEDIUM 5.9	openssl 1.1.1n · port 80
CVE-2024-0727 MEDIUM 5.5	openssl 1.1.1n · port 80
CVE-2026-44119 MEDIUM 5.5	http_server 2.4.59 · port 80
CVE-2024-36387 MEDIUM 5.4	http_server 2.4.59 · port 80
CVE-2025-66200 MEDIUM 5.4	http_server 2.4.59 · port 80
CVE-2022-2097 MEDIUM 5.3	openssl 1.1.1n · port 80
CVE-2023-0465 MEDIUM 5.3	openssl 1.1.1n · port 80
CVE-2023-0466 MEDIUM 5.3	openssl 1.1.1n · port 80
CVE-2023-3817 MEDIUM 5.3	openssl 1.1.1n · port 80
CVE-2023-5678 MEDIUM 5.3	openssl 1.1.1n · port 80
CVE-2026-33007 MEDIUM 5.3	http_server 2.4.59 · port 80
CVE-2026-33857 MEDIUM 5.3	http_server 2.4.59 · port 80
CVE-2026-34032 MEDIUM 5.3	http_server 2.4.59 · port 80
CVE-2026-58415 MEDIUM 5.3	http_server 2.4.59 · port 80
CVE-2026-79768 MEDIUM 5.3	http_server 2.4.59 · port 80
CVE-2026-33006 MEDIUM 4.8	http_server 2.4.59 · port 80
CVE-2026-42528 MEDIUM 4.3	http_server 2.4.59 · port 80
CVE-2026-42356 LOW 3.7	http_server 2.4.59 · port 80

Fixed by the distribution (4)

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 4

CVE	Software
CVE-2023-4807 HIGH 7.8	openssl 1.1.1n · port 80
CVE-2024-38472 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2025-59775 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2026-59685 HIGH 7.5	http_server 2.4.59 · port 80

Only affects another platform (2)

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 2

CVE	Software
CVE-2024-40898 HIGH 7.5	http_server 2.4.59 · port 80
CVE-2024-43394 HIGH 7.5	http_server 2.4.59 · 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.

Report an issue with this page