217.63.64.139

HTTP/1.1 200 OK
Date: Mon, 08 Jun 2026 07:08:33 GMT
Server: Apache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 683
Content-Type: text/html; charset=UTF-8

��TKs�0��+�Lcl @b�g:���\��q�b+�%U�t�߻�&@�C담�׷߮7-]]e��D��p�U��{��h�]v{�k
4X���i�Xu���9⯅XN�%J�m4�7�4p�v�O4��dƢ�
�«��u�N287h˃�x�����7�I�V�������ڇx��A\)�`��'�3���%/:f
t]�zw���\�W��Bo�Ľ�ro����8��h]�~a�fp��j4N���s � )�u�
�Q�m���-��L�
��@��X�P��<�U�L/o����	s��eMU'0k�'�D�
L`a����D[	�q�Kݽ����H51��T����VV8�d9!#N�co;�N�sV�j��w�&��5�U�	�%:�Ӌe҆���}w�����YL+��^�דΟ������~ۛh�i��7ď7�Q�V���OT�*�EQ��4S���1MV�f�Y<�V���3�:�m�����z9�0�...<truncated>

HTTP/1.1 400 Bad Request
Date: Mon, 08 Jun 2026 07:08:33 GMT
Server: Apache
Content-Length: 483
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>
<p>Additionally, a 400 Bad Request
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>