Due Diligence on Private Investors Union:

Here is what I have found out:

FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.

ns2.hannonweb1.net.

ns1.hannonweb1.net.

This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

To myself that indicates that they don't want to be found. Further:

FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:

ns3.hannonweb1.net.

ns4.hannonweb1.net.

Again, they are trying to be hidden.

In addition all of their servers are in the same facility! So should anything happen, like a fire, they would be gone for good!

and...

FAIL Stealth NS record leakage Your DNS servers leak stealth information in non-NS requests:

Stealth nameservers are leaked [ns1.hannonweb1.net.]!

Stealth nameservers are leaked [ns2.hannonweb1.net.]!

This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.

Further hiding.

WARN SOA MNAME Check WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: ns1.hannonweb1.net.. However, that server is not listed at the parent servers as one of your NS records! This is probably legal, but you should be sure that you know what you are doing.

Oh yes, they know what they are doing.

FAIL Reverse DNS entries for MX records ERROR: The IP of one or more of your mail server(s) have no reverse DNS (PTR) entries (if you see "Timeout" below, it may mean that your DNS servers did not respond fast enough). RFC1912 2.1 says you should have a reverse DNS for all your mail servers. It is strongly urged that you have them, as many mailservers will not accept mail from mailservers with no reverse DNS entry. You can double-check using the 'Reverse DNS Lookup' tool at the DNSstuff site (it contacts your servers in real time; the reverse DNS lookups in the DNS report use our local caching DNS server). The problem MX records are:

36.115.98.65.in-addr.arpa [No reverse DNS entry (rcode: 3 ancount: 0) (check it)]

Am starting to get worried.  This one has more FAILs than most I have researched!

Further, they are indeed using a proxy so we cannot find out who the real owners are. The server is in New Jersey, NY.

Disclaimer. We do not promote or own any programs. The information was obtained from sources believed to be reliable and we do not guarantee its accuracy. Some programs may be illegal depending on the laws of your Country. Past Performance of any of the programmes is not a guarantee of the same or similar future performance. Do not spend what you cannot afford to lose and have fun.