Category	Status	Test name	Information send feedback
Parent		Domain NS records	Nameserver records returned by the parent servers are: ns-cloud-a1.googledomains.com.   ['216.239.32.106'] (NO GLUE)   [TTL=3600] ns-cloud-a2.googledomains.com.   ['216.239.34.106'] (NO GLUE)   [TTL=3600] a2.nic.me was kind enough to give us that information.
		TLD Parent Check	Good. a2.nic.me, 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.
		Your nameservers are listed	Good. The parent server a2.nic.me has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
		DNS Parent sent Glue	The parent nameserver a2.nic.me is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
		Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS		NS records from your nameservers	NS records got from your nameservers listed at the parent NS are: Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.
		Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
		Same Glue	Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers.
		Glue for NS records	OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!
		Mismatched NS records	WARNING: One or more of your nameservers did not return any of your NS records.
		DNS servers responded	ERROR: One or more of your nameservers did not respond: The ones that did not respond are: 216.239.32.106 216.239.34.106
		Name of nameservers are valid	OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green!
		Multiple Nameservers	ERROR: Looks like you have less than 2 nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
		Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
		Missing nameservers reported by parent	OK. All NS records are the same at the parent and at your nameservers.
		Missing nameservers reported by your nameservers	You should already know that your NS records at your nameservers are missing, so here it is again: ns-cloud-a1.googledomains.com. ns-cloud-a2.googledomains.com.
		Domain CNAMEs	OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
		NSs CNAME check	OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
		Different subnets	OK. Looks like you have nameservers on different subnets!
		IPs of nameservers are public	Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like
		DNS servers allow TCP connection	OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
		Different autonomous systems	OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
		Stealth NS records sent	Ok. No stealth ns records are sent
SOA		SOA record	No valid SOA record came back!
MX		MX Records	Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
WWW		WWW A Record	ERROR: I could not get any A records for www.jenco.me! (I only do a cache request, if you recently added a WWW A record, it might not show up here.)

Processed in 0.431 seconds.