Byron's utility let you check these DNS records that entire internet sees. He is most likely using the results returned by dns_get_record()
My utility checks the DNS records on ns1.heliohost.org and ns2.heliohost.org specifically. This may be different than what entire internet sees, ie. if one does not use HelioHost nameservers as authoritative for the domain name. I am using DIG to query these nameservers. It's something like http://www.spacereg.com/a.rpl?m=dig
but without possibility to select specific records or custom nameservers. It's designed to check only records on both HelioHost nameservers as quickly as possible - with one click.
My tool will be useful in a case of some problems with HelioHost nameservers. Two times already ns2 did not return any records for some of the domains while ns1 did (nameservers were not synchronised). Now anyone, even someone that don't know what the DIG is, can diagnose such problem very quickly.
Check "grd.net.pl" for example. This domain is NOT parked on HelioHost, so obviously HelioHost nameservers does not have any records about it. My tool will show that there are no records for this domain on ns1/ns2.heliohost.org. Byron's tool will display you what the entire internet sees, that domain name is pointed to dns/dns2/dns3.home.pl (my registrars nameservers).
Check "google.com". Now here you'll be surprised. ; ) Someone did point this domain name to some account on Stevie and using my tool you'll find that HelioHost nameservers points "google.com" to IP 18.104.22.168. This is obviously NOT what entire internet sees, Google does not use HelioHost nameservers as authoritative so records in here does not matter at all, google.com is not served from Stevie for anyone that use public DNS system.edit: Not anymore, records for "google.com" has been deleted on HelioHost nameservers.