The evidence posted on this thread shows nothing other than a dns problem followed by some server issues. It does not show a scam, or negligence, or incompetence. There is absolutely no way you can tell, unless you get on that server and poke around from the inside.
Whilst this server
might just be port forwarding / proxying to a bunch of internal (secured) servers, the presence of an open rpcinfo port (port 111) absolutely indicates negligence and incompetence on the part of the server administrator. There is
zero reason for this port to be open on a public facing server. This very strongly suggests that this server is not a proxy, but is directly running all of these services.
FWIW, the server response string of "OpenSSL/1.0.1e-fips" does
not necessarily indicate a HeartBleed vulnerable version of OpenSSL. Some Linux distributions (especially RedHat and derivatives) ship with particular version numbers for packages, but back-port essential patches without bumping the version number.