Host
Tags: Cloud Hosting Expired certificate
As of our latest check on 2026-06-01, 138.68.87.247 (DigitalOcean, LLC, AS14061, Germany) had 2 open ports (80, 443) and 6 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-06-01.
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: 59 on a distribution build — the fix may be backported (http_server 2.4.58). See them
Not counted: 2 only affect another platform (http_server 2.4.58). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
HTTP/1.1 301 Moved Permanently date: Mon, 01 Jun 2026 12:20:00 GMT server: Apache/2.4.58 (Ubuntu) x-redirect-by: WordPress location: https://www.traveltrex.com/ content-length: 0 content-type: text/html; charset=UTF-8
YU�,u���b������
�A~��C��DOWNGRD 8�mC�����ֲEĖ��*�Ej'.���q�q��/
���~�0��0������@D�@��Z0
*�H��
0`10 UGB10U
Sectigo Limited1705U.Sectigo Public Server Authentication CA DV R360
250703000000Z
260703235959Z010Utraveltrex.com0�"0
*�H��
�0�
���6)۵�"�ˢB���2���M�*���P�`�1����vH��3���:�y��ߣ�:rO̙�H����p��c��Mz�7p*��טw�
��.�����+���O1˾����y�`$���~i+$�詿l�N{��6��B��]�
;�ӧQ��͕]|�H�0���l��Ibŷr�V-d�@��Y��+ \̏y�1I�71�A$��yO�M���}�ϭB�{�o��j:���B���� �n?����&;��0��0U#0�h������2W�FQ]�'0U+�T�y�\Y��b�@�
+�10U��0U�00U%0++0IU B0@04+�10%0#+https://sectigo.com/CPS0g�0��+x0v0O+0�Chttp://crt.sectigo.com/SectigoPublicServerAuthentication...<truncated>
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 34 MEDIUM 14
| CVE | Software |
|---|---|
| CVE-2024-38475 CRITICAL 9.1 known exploited | http_server 2.4.58 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-56154 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-57941 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2026-59797 CRITICAL 9.8 | http_server 2.4.58 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 | http_server 2.4.58 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 | http_server 2.4.58 · port 80 |
| CVE-2026-24072 HIGH 8.8 | http_server 2.4.58 · port 80 |
| CVE-2026-93546 HIGH 8.8 | http_server 2.4.58 · port 80 |
| CVE-2025-58098 HIGH 8.3 | http_server 2.4.58 · port 80 |
| CVE-2024-38473 HIGH 8.1 | http_server 2.4.58 · port 80 |
| CVE-2026-73636 HIGH 8.1 | http_server 2.4.58 · port 80 |
| CVE-2024-27316 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-38472 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-38477 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-39573 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-42516 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-43204 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2024-47252 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-49630 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-53020 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-55753 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-59775 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-29169 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34059 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34355 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-34356 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-42536 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-49975 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-59685 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63045 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63292 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63686 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2026-63718 HIGH 7.5 | http_server 2.4.58 · port 80 |
| CVE-2025-49812 HIGH 7.4 | http_server 2.4.58 · port 80 |
| CVE-2023-38709 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-29168 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-44185 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-44186 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-48913 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2026-73637 HIGH 7.3 | http_server 2.4.58 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 | http_server 2.4.58 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 | http_server 2.4.58 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 | http_server 2.4.58 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 | http_server 2.4.58 · port 80 |
| CVE-2024-36387 MEDIUM 5.4 | http_server 2.4.58 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 | http_server 2.4.58 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-58415 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-79768 MEDIUM 5.3 | http_server 2.4.58 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 | http_server 2.4.58 · port 80 |
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.58 · port 80 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.58 · port 80 |
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.
2 names · as answered by each domain's own name servers