217.231.131.99 — 1 open port, 0 known CVEs, network Deutsche Telekom AG

Known CVEs on this host

1open port

0names pointing here

0known CVEs

0known exploited

Open ports and CVEs as of our latest check of this host, 2026-06-09.

No known CVEs now

Not counted: 54 on a distribution build — the fix may be backported (http_server 2.2.22). See them

Not counted: 1 fixed by the distribution (http_server 2.2.22). See them

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

Network: Deutsche Telekom AG AS3320
Open ports: 80 · at our latest check, 2026-06-09
Location: Remscheid, DE-NW · Germany DE
Hostname: pd9e78363.dip0.t-ipconnect.de · reverse DNS, checked 2026-10-05
Route: 217.224.0.0/11 · announced by Deutsche Telekom AG AS3320 RPKI valid
Organisation: Deutsche Telekom AG · Network service provider (transit)
Registry network: DTAG-DIAL15 · 217.224.0.0 - 217.237.161.47 · RIPE
Abuse contact: [email protected] · for DTAG-DIAL15
First seen: 2026-06-09 10:23 UTC
Last seen alive: 2026-06-09 10:27 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 (1)

80/tcp HTTP Apache/2.2.22 (Debian) first 2026-06-09 · last 2026-06-09

Status: 200 OK
Server: Apache/2.2.22 (Debian)

Raw response

HTTP/1.1 200 OK
Date: Tue, 09 Jun 2026 10:25:26 GMT
Server: Apache/2.2.22 (Debian)
Last-Modified: Wed, 11 Dec 2019 07:54:24 GMT
ETag: "20324-da-59968efe58c00"
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 181
Content-Type: text/html

�-��
�0��}�%'��x��ATP���ڬM�����������ٙưڪ1���^����0:��H�{��$���U�;��+!kL�#�h����>f�DR�jM����,Y��� `�Ӈ�ԍ62���}������Q��]v�Y�%d�Ogy�ޖ��9E-��yQ�_c_W�

Distribution build — the fix may be backported (54)

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 13 HIGH 17 MEDIUM 23 LOW 1

CVE	Software
CVE-2021-40438 CRITICAL 9.0 known exploited	http_server 2.2.22 · port 80
CVE-2017-3167 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2017-3169 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2017-7679 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2021-39275 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2021-44790 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2022-22720 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2022-31813 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2026-28780 CRITICAL 9.8	http_server 2.2.22 · port 80
CVE-2017-9788 CRITICAL 9.1	http_server 2.2.22 · port 80
CVE-2022-22721 CRITICAL 9.1	http_server 2.2.22 · port 80
CVE-2022-28615 CRITICAL 9.1	http_server 2.2.22 · port 80
CVE-2026-42535 CRITICAL 9.1	http_server 2.2.22 · port 80
CVE-2026-24072 HIGH 8.8	http_server 2.2.22 · port 80
CVE-2026-93546 HIGH 8.8	http_server 2.2.22 · port 80
CVE-2025-58098 HIGH 8.3	http_server 2.2.22 · port 80
CVE-2016-5387 HIGH 8.1	http_server 2.2.22 · port 80
CVE-2006-20001 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2016-8743 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2017-9798 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2018-1303 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2021-34798 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2022-22719 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2022-29404 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2022-30556 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2023-31122 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2026-29169 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2026-34059 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2025-49812 HIGH 7.4	http_server 2.2.22 · port 80
CVE-2023-38709 HIGH 7.3	http_server 2.2.22 · port 80
CVE-2014-0226 MEDIUM 6.8	http_server 2.2.22 · port 80
CVE-2016-4975 MEDIUM 6.1	http_server 2.2.22 · port 80
CVE-2026-29170 MEDIUM 6.1	http_server 2.2.22 · port 80
CVE-2018-1301 MEDIUM 5.9	http_server 2.2.22 · port 80
CVE-2018-1302 MEDIUM 5.9	http_server 2.2.22 · port 80
CVE-2022-28614 MEDIUM 5.3	http_server 2.2.22 · port 80
CVE-2022-37436 MEDIUM 5.3	http_server 2.2.22 · port 80
CVE-2026-33857 MEDIUM 5.3	http_server 2.2.22 · port 80
CVE-2026-34032 MEDIUM 5.3	http_server 2.2.22 · port 80
CVE-2013-1862 MEDIUM 5.1	http_server 2.2.22 · port 80
CVE-2013-5704 MEDIUM 5.0	http_server 2.2.22 · port 80
CVE-2013-6438 MEDIUM 5.0	http_server 2.2.22 · port 80
CVE-2014-0098 MEDIUM 5.0	http_server 2.2.22 · port 80
CVE-2014-0231 MEDIUM 5.0	http_server 2.2.22 · port 80
CVE-2015-0228 MEDIUM 5.0	http_server 2.2.22 · port 80
CVE-2015-3183 MEDIUM 5.0	http_server 2.2.22 · port 80
CVE-2026-33006 MEDIUM 4.8	http_server 2.2.22 · port 80
CVE-2008-0455 MEDIUM 4.3	http_server 2.2.22 · port 80
CVE-2012-3499 MEDIUM 4.3	http_server 2.2.22 · port 80
CVE-2012-4558 MEDIUM 4.3	http_server 2.2.22 · port 80
CVE-2013-1896 MEDIUM 4.3	http_server 2.2.22 · port 80
CVE-2014-0118 MEDIUM 4.3	http_server 2.2.22 · port 80
CVE-2016-8612 MEDIUM 4.3	http_server 2.2.22 · port 80
CVE-2012-2687 LOW 2.6	http_server 2.2.22 · port 80

Fixed by the distribution (1)

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: MEDIUM 1

CVE	Software
CVE-2012-0883 MEDIUM 6.9	http_server 2.2.22 · 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 1 MEDIUM 1

CVE	Software
CVE-2024-40898 HIGH 7.5	http_server 2.2.22 · port 80
CVE-2022-28330 MEDIUM 5.3	http_server 2.2.22 · 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