Category	Status	Test name	Information send feedback
Parent		Domain NS records	Nameserver records returned by the parent servers are: ns1.free.thdns.com.   ['103.43.162.38']   [TTL=172800] ns2.free.thdns.com.   ['103.43.162.39']   [TTL=172800] a.gtld-servers.net was kind enough to give us that information.
		TLD Parent Check	Good. a.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.
		Your nameservers are listed	Good. The parent server a.gtld-servers.net 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	Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)
		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: ns2.free.thdns.com  ['103.43.162.39']   [TTL=86400] ns1.free.thdns.com  ['103.43.162.38']   [TTL=86400]
		Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
		Same Glue	The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
		Glue for NS records	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. The nameservers without glue are: 103.43.162.39 You can fix this for example by adding A records to your nameservers for the zones listed above.
		Mismatched NS records	OK. The NS records at all your nameservers are identical.
		DNS servers responded	Good. All nameservers listed at the parent server responded.
		Name of nameservers are valid	OK. All of the NS records that your nameservers report seem valid.
		Multiple Nameservers	Good. You have multiple 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	ERROR: looks like you have lame nameservers. The following nameservers are lame: 103.43.162.38
		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	OK. All nameservers returned by the parent server a.gtld-servers.net are the same as the ones reported by your nameservers.
		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	WARNING: Not all of your nameservers are in 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	WARNING: Single point of failure
		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.hzliangli.com! (I only do a cache request, if you recently added a WWW A record, it might not show up here.)

Processed in 2.842 seconds.