- Status
- 200 OK
Raw response
HTTP/1.1 200 OK Access-Control-Allow-Origin: * Content-Type: application/json; charset=UTF-8 Content-Length: 14 Date: Tue, 11 Aug 2026 03:47:02 GMT Connection: keep-alive Keep-Alive: timeout=5 no bid request
Host
Tags: Hosting Expired certificate
As of our latest check on 2026-08-11, 89.40.226.115 (Melbikomas UAB, AS8849, Singapore) had 2 open ports (80, 443) and 45 known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-08-11.
CVEs by severity: CRITICAL 4 HIGH 23 MEDIUM 18
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
All of them on a software version from an earlier observation: a service of that kind is open now.
Not counted: 34 from an older observation (mongodb 7.0.14; matched 2026-06-08). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
HTTP/1.1 200 OK Access-Control-Allow-Origin: * Content-Type: application/json; charset=UTF-8 Content-Length: 14 Date: Tue, 11 Aug 2026 03:47:02 GMT Connection: keep-alive Keep-Alive: timeout=5 no bid request
YU�O�r/�V���H���͔���DOWNGRD 5��4��wFng�B"M�]��O�Q�h֒��S�/ ����0�0���1�3 q�ֳ�����0 *�H�� 0310 UUS10U Let's Encrypt10 UYR20 260713075207Z 261011075206Z010U dcntr-ads.com0�"0 *�H�� �0� ��<�����I+��G����y�����;,<�*����x��W��]��Āys?!�OJFW����C(�2�5߱ny��<�nQ��~�Фg�? �9��ȍLƗ;W����pXL쭞sÍ��$���XG*�j���v��e1��5:�3�̹@���1�W}�+��Ǥ�f�z?*x%/%�Q��gb��I�LE�~�R!��l�VZ��3�� �����7��8]���`��XR�nd�M:dy&��h�A�;��G�o����c���y��1���*0�&0U��0U%0 +0U�00U@��"S�ݨ�^r���20U#0�@-&y�2 �ߚr�2��03+'0%0#+0�http://yr2.i.lencr.org/0)U"0 �*.dcntr-ads.com� dcntr-ads.com0U 0 0g�0.U'0%0#�!��http://yr2.c.lencr.org/46.crl0� +�y�����...<truncated>
These CVEs were matched on software this host reported in an earlier observation (matched 2026-06-08), not on a port that is open now, and no service of that kind was open at the latest check (2026-08-11). They are not counted above; 1 of them is known to be exploited.
CVEs by severity: CRITICAL 1 HIGH 16 MEDIUM 17
| CVE | Software |
|---|---|
| CVE-2025-14847 HIGH 8.7 known exploited | mongodb 7.0.14 |
| CVE-2025-3085 CRITICAL 9.8 | mongodb 7.0.14 |
| CVE-2025-6706 HIGH 8.8 | mongodb 7.0.14 |
| CVE-2026-4148 HIGH 8.7 | mongodb 7.0.14 |
| CVE-2026-8053 HIGH 8.7 | mongodb 7.0.14 |
| CVE-2024-10921 HIGH 8.1 | mongodb 7.0.14 |
| CVE-2025-0755 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-10060 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-13644 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-3083 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-6709 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-6710 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-6714 HIGH 7.5 | mongodb 7.0.14 |
| CVE-2025-13507 HIGH 7.1 | mongodb 7.0.14 |
| CVE-2026-4147 HIGH 7.1 | mongodb 7.0.14 |
| CVE-2026-6914 HIGH 7.1 | mongodb 7.0.14 |
| CVE-2026-8199 HIGH 7.1 | mongodb 7.0.14 |
| CVE-2025-10059 MEDIUM 6.5 | mongodb 7.0.14 |
| CVE-2025-10061 MEDIUM 6.5 | mongodb 7.0.14 |
| CVE-2025-11979 MEDIUM 6.5 | mongodb 7.0.14 |
| CVE-2025-13643 MEDIUM 6.5 | mongodb 7.0.14 |
| CVE-2025-3084 MEDIUM 6.5 | mongodb 7.0.14 |
| CVE-2025-6713 MEDIUM 6.5 | mongodb 7.0.14 |
| CVE-2026-4358 MEDIUM 6.1 | mongodb 7.0.14 |
| CVE-2026-8201 MEDIUM 6.1 | mongodb 7.0.14 |
| CVE-2026-5170 MEDIUM 6.0 | mongodb 7.0.14 |
| CVE-2025-12657 MEDIUM 5.5 | mongodb 7.0.14 |
| CVE-2025-12893 MEDIUM 5.4 | mongodb 7.0.14 |
| CVE-2025-14345 MEDIUM 5.4 | mongodb 7.0.14 |
| CVE-2025-6707 MEDIUM 5.4 | mongodb 7.0.14 |
| CVE-2026-6915 MEDIUM 5.3 | mongodb 7.0.14 |
| CVE-2026-8202 MEDIUM 5.3 | mongodb 7.0.14 |
| CVE-2025-6711 MEDIUM 4.9 | mongodb 7.0.14 |
| CVE-2026-8200 MEDIUM 4.8 | mongodb 7.0.14 |
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.