217.66.129.7 — 1 open port, 0 known CVEs, network GTT Communications Inc.

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-08.

No known CVEs now

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

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

Network: GTT Communications Inc. AS3257
Open ports: 80 · at our latest check, 2026-06-08
Location: Germany DE
Hostname: www.schiller-wurst.de · reverse DNS, checked 2026-10-05
Route: 217.66.128.0/21 · announced by GTT Communications Inc. AS3257 and others no RPKI authorisation
Organisation: GTT Communications, Inc. · Network service provider (transit)
Registry network: IGSNET1 · 217.66.128.0 - 217.66.132.255 · RIPE
Abuse contact: [email protected] · for IGSNET1
First seen: 2026-06-08 07:15 UTC
Last seen alive: 2026-06-08 07:16 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/1.3.26 (Linux/SuSE) first 2026-06-08 · last 2026-06-08

Status: 200 OK
Title: under construction...
Server: Apache/1.3.26 (Linux/SuSE)

Raw response

HTTP/1.1 200 OK
Date: Mon, 08 Jun 2026 05:15:24 GMT
Server: Apache/1.3.26 (Linux/SuSE)
Transfer-Encoding: chunked
Content-Type: text/html

78 
<html><head><title>under construction...</title></head><body><p><p><center>under construction...</center></body></html>

0

Distribution build — the fix may be backported (67)

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 26 MEDIUM 29 LOW 1

CVE	Software
CVE-2021-40438 CRITICAL 9.0 known exploited	http_server 1.3.26 · port 80
CVE-2004-0492 HIGH 10.0	http_server 1.3.26 · port 80
CVE-2009-3555 CRITICAL 9.8	http_server 1.3.26 · port 80
CVE-2021-39275 CRITICAL 9.8	http_server 1.3.26 · port 80
CVE-2021-44790 CRITICAL 9.8	http_server 1.3.26 · port 80
CVE-2022-22720 CRITICAL 9.8	http_server 1.3.26 · port 80
CVE-2022-31813 CRITICAL 9.8	http_server 1.3.26 · port 80
CVE-2026-28780 CRITICAL 9.8	http_server 1.3.26 · port 80
CVE-2017-9788 CRITICAL 9.1	http_server 1.3.26 · port 80
CVE-2022-22721 CRITICAL 9.1	http_server 1.3.26 · port 80
CVE-2022-28615 CRITICAL 9.1	http_server 1.3.26 · port 80
CVE-2026-42535 CRITICAL 9.1	http_server 1.3.26 · port 80
CVE-2026-24072 HIGH 8.8	http_server 1.3.26 · port 80
CVE-2026-93546 HIGH 8.8	http_server 1.3.26 · port 80
CVE-2025-58098 HIGH 8.3	http_server 1.3.26 · port 80
CVE-2002-2272 HIGH 7.8	http_server 1.3.26 · port 80
CVE-2004-0940 HIGH 7.8	http_server 1.3.26 · port 80
CVE-2002-0843 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2003-0987 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2003-0993 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2004-0174 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2004-1082 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2006-20001 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2017-9798 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2018-1303 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2021-34798 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2022-22719 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2022-29404 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2022-30556 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2023-31122 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2026-29169 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2026-34059 HIGH 7.5	http_server 1.3.26 · port 80
CVE-2025-49812 HIGH 7.4	http_server 1.3.26 · port 80
CVE-2023-38709 HIGH 7.3	http_server 1.3.26 · port 80
CVE-2002-0839 HIGH 7.2	http_server 1.3.26 · port 80
CVE-2003-0542 HIGH 7.2	http_server 1.3.26 · port 80
CVE-2004-2343 HIGH 7.2	http_server 1.3.26 · port 80
CVE-2002-0840 MEDIUM 6.8	http_server 1.3.26 · port 80
CVE-2010-0010 MEDIUM 6.8	http_server 1.3.26 · port 80
CVE-2026-29170 MEDIUM 6.1	http_server 1.3.26 · port 80
CVE-2018-1301 MEDIUM 5.9	http_server 1.3.26 · port 80
CVE-2018-1302 MEDIUM 5.9	http_server 1.3.26 · port 80
CVE-2022-28614 MEDIUM 5.3	http_server 1.3.26 · port 80
CVE-2022-37436 MEDIUM 5.3	http_server 1.3.26 · port 80
CVE-2026-33857 MEDIUM 5.3	http_server 1.3.26 · port 80
CVE-2026-34032 MEDIUM 5.3	http_server 1.3.26 · port 80
CVE-2001-1556 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2003-0020 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2003-0460 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2004-0263 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2004-0942 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2007-6750 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2011-3368 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2015-0228 MEDIUM 5.0	http_server 1.3.26 · port 80
CVE-2026-33006 MEDIUM 4.8	http_server 1.3.26 · port 80
CVE-2007-3304 MEDIUM 4.7	http_server 1.3.26 · port 80
CVE-2002-1658 MEDIUM 4.6	http_server 1.3.26 · port 80
CVE-2003-1418 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2005-3352 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2006-3918 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2006-5752 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2007-5000 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2007-6388 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2008-2939 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2011-4317 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2016-8612 MEDIUM 4.3	http_server 1.3.26 · port 80
CVE-2002-1233 LOW 2.6	http_server 1.3.26 · 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 1.3.26 · port 80
CVE-2022-28330 MEDIUM 5.3	http_server 1.3.26 · 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