72.4.147.17

220 ProFTPD Server (ProFTPD) [72.4.147.17]

SSH-2.0-OpenSSH_5.3

220 mail.seowebsupport.com ESMTP Postfix

HTTP/1.1 301 Moved Permanently
Date: Wed, 29 Jul 2026 23:10:17 GMT
Server: Apache
Location: https://72.4.147.17/
Content-Length: 289
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://72.4.147.17/">here</a>.</p>
<hr>
<address>Apache Server at 72.4.147.17 Port 80</address>
</body></html>

<HTML>
<HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD>
<BODY>
<H1>Bad Request</H1>
Your browser sent a request that this server could not understand.
<P>
Client sent malformed Host header
<P>
<HR>
<ADDRESS>
Web Server at spartical.com
</ADDRESS>
</BODY>
</HTML>

<!--
   - Unfortunately, Microsoft has added a clever new
   - "feature" to Internet Explorer. If the text of
   - an error's message is "too small", specifically
   - less than 512 bytes, Internet Explorer returns
   - its own error message. You can turn that off,
   - but it's pretty tricky to find switch called
   - "smart error messages". That means, of course,
   - that short error messages are censored by default.
   - IIS always returns error messages that are long
   - enough to make Internet Explorer happy. The
   - workaround is pretty simple: pad the error
   - message with a big comment like this to push it
   - over the five hundred and twelve bytes minimum.
   - Of course, that's exactl

J
5.7.17�rKOI%=����%?}lxN:Jmysql_native_password

HTTP/1.1 302 Moved Temporarily
Server: sw-cp-server
Date: Wed, 29 Jul 2026 23:10:17 GMT
Content-Type: text/html
Content-Length: 138
Connection: close
Location: https://72.4.147.17:8443/

<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>