- Server
- SSH-2.0-OpenSSH_8.7
- Host key
- ssh-ed25519 35024e3430a918b0…
Raw response
SSH-2.0-OpenSSH_8.7
Host
Tags: Hosting Expired certificate
As of our latest check on 2026-06-07, 198.38.82.163 (WHG Hosting Services Ltd, AS51713, United Kingdom) had 3 open ports (22, 80, 443) and no known CVEs.
Open ports and CVEs as of our latest check of this host, 2026-06-07.
No known CVEs now
Not counted: 38 on a distribution build — the fix may be backported (openssh 8.7). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_8.7
HTTP/1.1 400 Bad Request Server: nginx/1.20.1 Date: Sun, 07 Jun 2026 03:21:01 GMT Content-Type: text/html Content-Length: 157 Connection: close <html> <head><title>400 Bad Request</title></head> <body> <center><h1>400 Bad Request</h1></center> <hr><center>nginx/1.20.1</center> </body> </html>
YUp��*9�P!�#C�B��^s�2�hDOWNGRD ���0k�p�5%�����yY�Ӟ���&-���+
���0��0� �1���a1J���o�J~�w}0
*�H�=0210 UUS10U
Let's Encrypt10 UE80
260120065018Z
260420065017Z010Uauth.mxtouchid.com0Y0*�H�=*�H�=BC��'�g
��*W��Z�V�C)NBV�iUN]���84cJN�I�aYq��Q��L���R�[�b�K�b�B���)0�%0U��0U%0++0U�00U����eC���e�f�k��,�#0U#0��
��.~�Pl38]Y�#r��02+&0$0"+0�http://e8.i.lencr.org/0U0�auth.mxtouchid.com0U 0
0g�0.U'0%0#�!��http://e8.c.lencr.org/126.crl0�
+�y�����vI��i�|��6�͇d��[�
���UR���)�����`��G0E O�K�I�1���*�4�*�`�����L��]-�.!�X�Z�;���6��_H��zM�Vw]�{�.��a�~q~���8�m���I=1�Z�bv-B��g��a���`��aE�G0E!�[���>N?��1��:�7߷�dQ���fZ0�� �,(����...<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 2 HIGH 10 MEDIUM 14 LOW 12
| CVE | Software |
|---|---|
| CVE-2026-123158 HIGH 8.1 known exploited | openssh 8.7 · port 22 |
| CVE-2023-38408 CRITICAL 9.8 | openssh 8.7 · port 22 |
| CVE-2026-60002 CRITICAL 9.4 | openssh 8.7 · port 22 |
| CVE-2024-6387 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 8.7 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 8.7 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-59999 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 8.7 · port 22 |
| CVE-2021-41617 HIGH 7.0 | openssh 8.7 · port 22 |
| CVE-2025-26465 MEDIUM 6.8 | openssh 8.7 · port 22 |
| CVE-2023-51385 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 8.7 · port 22 |
| CVE-2023-48795 MEDIUM 5.9 | openssh 8.7 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 8.7 · port 22 |
| CVE-2016-20012 MEDIUM 5.3 | openssh 8.7 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 8.7 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 8.7 · port 22 |
| CVE-2025-32728 LOW 3.8 | openssh 8.7 · port 22 |
| CVE-2021-36368 LOW 3.7 | openssh 8.7 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 8.7 · port 22 |
| CVE-2025-61984 LOW 3.6 | openssh 8.7 · port 22 |
| CVE-2025-61985 LOW 3.6 | openssh 8.7 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 8.7 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 8.7 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 8.7 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 8.7 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 8.7 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 8.7 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 8.7 · port 22 |
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