Host
Tags: Self-signed certificate Expired certificate
As of our latest check on 2026-06-07, 212.65.13.222 (PFALZKOM GmbH, AS21473, Germany) 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: 27 on a distribution build — the fix may be backported (openssh 10.2). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
SSH-2.0-OpenSSH_10.2 FreeBSD-openssh-portable-10.2.p1_1,1
HTTP/1.1 301 Moved Permanently Location: https://212.65.13.222/ Content-Length: 0 Date: Sun, 07 Jun 2026 08:04:55 GMT Server: OPNsense
95��[=�fC�2��x-5@%��0*��DOWNGRD�/
�,(%"0�0��tS�;ZeFN��ƌK�0
*�H��
0��10UOPNsense.localdomain10 UNL10UZuid-Holland10UMiddelharnis1-0+U
$OPNsense self-signed web certificate0
241213134600Z
260114134600Z0��10UOPNsense.localdomain10 UNL10UZuid-Holland10UMiddelharnis1-0+U
$OPNsense self-signed web certificate0�"0
*�H��
�0�
����?9�RE�ɠ�S�B��ǎ.D��R���-���ȶ��Y�
�.E �����.�����nѸ.Be>=(������w(��Y�y��Օ��}���=���3�`��h�5y'��p&nbAK@Â��#cc�aV��ѽ�1N��P�I�UN�_脊~�y�/ٚ
f�\������[T��1VgJ�E����}�[]�jwtl�I�!���zr���`��]<� �Y���O�;�C��C���X�6`e9K��+��eK1�Ļ{%H�/�ܫw��5���w���8�"d�7T�鐱�n���? �*GE�Y��6;��Q^C�ݜ�6R~������wڸ��I�"ϷM)?�%����Wt!7F��...<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.
CVEs by severity: CRITICAL 1 HIGH 8 MEDIUM 10 LOW 8
| CVE | Software |
|---|---|
| CVE-2026-60002 CRITICAL 9.4 | openssh 10.2 · port 22 |
| CVE-2026-35385 HIGH 8.1 | openssh 10.2 · port 22 |
| CVE-2026-35386 HIGH 8.1 | openssh 10.2 · port 22 |
| CVE-2026-35414 HIGH 8.1 | openssh 10.2 · port 22 |
| CVE-2026-106583 HIGH 7.8 | openssh 10.2 · port 22 |
| CVE-2026-106553 HIGH 7.5 | openssh 10.2 · port 22 |
| CVE-2026-106555 HIGH 7.5 | openssh 10.2 · port 22 |
| CVE-2026-59999 HIGH 7.5 | openssh 10.2 · port 22 |
| CVE-2026-60000 HIGH 7.5 | openssh 10.2 · port 22 |
| CVE-2026-106552 MEDIUM 6.5 | openssh 10.2 · port 22 |
| CVE-2026-106585 MEDIUM 6.5 | openssh 10.2 · port 22 |
| CVE-2026-35387 MEDIUM 6.5 | openssh 10.2 · port 22 |
| CVE-2026-59998 MEDIUM 6.5 | openssh 10.2 · port 22 |
| CVE-2026-60001 MEDIUM 6.5 | openssh 10.2 · port 22 |
| CVE-2026-59995 MEDIUM 5.4 | openssh 10.2 · port 22 |
| CVE-2026-59996 MEDIUM 5.4 | openssh 10.2 · port 22 |
| CVE-2026-59997 MEDIUM 5.4 | openssh 10.2 · port 22 |
| CVE-2026-73282 MEDIUM 4.8 | openssh 10.2 · port 22 |
| CVE-2026-106586 MEDIUM 4.3 | openssh 10.2 · port 22 |
| CVE-2026-106582 LOW 3.7 | openssh 10.2 · port 22 |
| CVE-2026-73281 LOW 3.5 | openssh 10.2 · port 22 |
| CVE-2026-106584 LOW 3.3 | openssh 10.2 · port 22 |
| CVE-2026-106587 LOW 3.3 | openssh 10.2 · port 22 |
| CVE-2026-106588 LOW 3.1 | openssh 10.2 · port 22 |
| CVE-2026-106589 LOW 2.9 | openssh 10.2 · port 22 |
| CVE-2026-35388 LOW 2.5 | openssh 10.2 · port 22 |
| CVE-2026-73283 LOW 2.5 | openssh 10.2 · 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.