82.202.5.183 — 2 open ports, 6 known CVEs, network CEZNET s.r.o.

Known CVEs on this host

2open ports

0names pointing here

6known CVEs

0known exploited

Open ports and CVEs as of our latest check of this host, 2026-05-24.

CVEs by severity: HIGH 4 MEDIUM 1 LOW 1

A match is an indication, not proof: it is based on the software version a service reported, and fixes are often backported without changing the version. See the list

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

Not counted: 3 only affect another platform (http_server 2.4.52). See them

Network: CEZNET s.r.o. AS6740
Open ports: 80, 443 · at our latest check, 2026-05-24
Location: Zlin, CZ-72 · Czechia CZ
Hostname: cust-82-202-5-183.inext.cz · reverse DNS, checked 2026-10-04
Route: 82.202.0.0/18 · announced by CEZNET s.r.o. AS6740 RPKI valid
Organisation: CEZNET s.r.o.
Registry network: INEXT-NET-TSD · 82.202.5.0 - 82.202.5.255 · RIPE
Abuse contact: [email protected] · for INEXT-NET-TSD
First seen: 2026-05-24 21:03 UTC
Last seen alive: 2026-05-24 21:04 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.52 (Ubuntu) 6 CVEs first 2026-05-24 · last 2026-05-24

Status: 301 Moved Permanently
Title: 301 Moved Permanently
Server: Apache/2.4.52 (Ubuntu)

Raw response

HTTP/1.1 301 Moved Permanently
Date: Sun, 24 May 2026 21:03:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://82.202.5.183/
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://82.202.5.183/">here</a>.</p>
<hr>
<address>Apache/2.4.52 (Ubuntu) Server at 82.202.5.183 Port 80</address>
</body></html>

443/tcp TLS first 2026-05-24 · last 2026-05-24

TLS: TLSv1.2
Certificate for: hub.capka.info
Issued by: R12
Valid: 2026-04-12 → 2026-07-11

Raw response

HTTP/1.1 400 Bad Request
Date: Sun, 24 May 2026 21:03:52 GMT
Server: Apache/2.4.52 (Ubuntu)
Strict-Transport-Security: max-age=63072000
Content-Length: 442
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.52 (Ubuntu) Server at hub.capka.info Port 80</address>
</body></html>

Vulnerabilities

Distribution build — the fix may be backported (74)

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 18 HIGH 40 MEDIUM 16

CVE	Software
CVE-2024-38475 CRITICAL 9.1 known exploited	http_server 2.4.52 · port 80
CVE-2022-22720 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2022-23943 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2022-31813 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2023-25690 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2024-38474 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2024-38476 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2026-28780 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2026-29167 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2026-44631 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2026-56154 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2026-57941 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2026-59797 CRITICAL 9.8	http_server 2.4.52 · port 80
CVE-2022-22721 CRITICAL 9.1	http_server 2.4.52 · port 80
CVE-2022-28615 CRITICAL 9.1	http_server 2.4.52 · port 80
CVE-2025-23048 CRITICAL 9.1	http_server 2.4.52 · port 80
CVE-2026-42535 CRITICAL 9.1	http_server 2.4.52 · port 80
CVE-2022-36760 CRITICAL 9.0	http_server 2.4.52 · port 80
CVE-2026-24072 HIGH 8.8	http_server 2.4.52 · port 80
CVE-2026-93546 HIGH 8.8	http_server 2.4.52 · port 80
CVE-2025-58098 HIGH 8.3	http_server 2.4.52 · port 80
CVE-2024-38473 HIGH 8.1	http_server 2.4.52 · port 80
CVE-2026-73636 HIGH 8.1	http_server 2.4.52 · port 80
CVE-2006-20001 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2022-22719 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2022-26377 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2022-29404 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2022-30556 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2023-27522 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2023-31122 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-27316 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-38472 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-38477 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-39573 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-42516 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-43204 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2024-47252 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2025-49630 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2025-53020 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2025-55753 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2025-59775 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-29169 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-34059 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-34355 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-34356 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-42536 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-49975 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-59685 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-63045 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-63292 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-63686 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2026-63718 HIGH 7.5	http_server 2.4.52 · port 80
CVE-2025-49812 HIGH 7.4	http_server 2.4.52 · port 80
CVE-2023-38709 HIGH 7.3	http_server 2.4.52 · port 80
CVE-2026-29168 HIGH 7.3	http_server 2.4.52 · port 80
CVE-2026-44185 HIGH 7.3	http_server 2.4.52 · port 80
CVE-2026-44186 HIGH 7.3	http_server 2.4.52 · port 80
CVE-2026-73637 HIGH 7.3	http_server 2.4.52 · port 80
CVE-2025-65082 MEDIUM 6.5	http_server 2.4.52 · port 80
CVE-2026-33523 MEDIUM 6.5	http_server 2.4.52 · port 80
CVE-2026-43951 MEDIUM 6.5	http_server 2.4.52 · port 80
CVE-2024-24795 MEDIUM 6.3	http_server 2.4.52 · port 80
CVE-2026-29170 MEDIUM 6.1	http_server 2.4.52 · port 80
CVE-2023-45802 MEDIUM 5.9	http_server 2.4.52 · port 80
CVE-2026-44119 MEDIUM 5.5	http_server 2.4.52 · port 80
CVE-2025-66200 MEDIUM 5.4	http_server 2.4.52 · port 80
CVE-2022-28614 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2022-37436 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2026-33007 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2026-33857 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2026-34032 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2026-58415 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2026-79768 MEDIUM 5.3	http_server 2.4.52 · port 80
CVE-2026-33006 MEDIUM 4.8	http_server 2.4.52 · port 80

Only affects another platform (3)

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

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