INFO: GLUE was not sent when I asked your nameservers for your NS records.
This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS records.
You need to make sure that these nameservers are working. dns3.fastdns24dns4.fastdns24dns.fastdns24dns2.fastdns24ERROR: 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: ns1.ns1.ns2.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). It seems you are safe from a single point of failure. Your MX records that were reported by your nameservers are: 10 mail..112 [These are all the MX records that I found.
Nameserver records returned by the parent servers are: ns1. ['188.8.131.52'] (NO GLUE) [TTL=172800] ns1. ['1.223'] [TTL=172800] f.was kind enough to give us that information. f.gtld-servers.net, the parent server I interrogated, has information for your TLD.
This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
Evildating has a mediocre Google pagerank and bad results in terms of Yandex topical citation index.