|Parent||Domain NS records||Nameserver records returned by the parent servers are:|
. 518400 IN NS h.root-servers.net.
. 518400 IN NS i.root-servers.net.
. 518400 IN NS j.root-servers.net.
. 518400 IN NS k.root-servers.net.
. 518400 IN NS l.root-servers.net.
. 518400 IN NS m.root-servers.net.
. 518400 IN NS a.root-servers.net.
. 518400 IN NS b.root-servers.net.
. 518400 IN NS c.root-servers.net.
. 518400 IN NS d.root-servers.net.
. 518400 IN NS e.root-servers.net.
. 518400 IN NS f.root-servers.net.
. 518400 IN NS g.root-servers.net.
a.gtld-servers.net was kind enough to give us that information.
|TLD Parent Check||Not Good. a.gtld-servers.net, the parent server I interrogated, might not has information for your TLD.|
|Nameservers listed||Not Good. The parent server a.gtld-servers.net has your nameservers might not 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||Not Good. The parent nameserver might not 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.|
|Nameservers A records||Good. Every nameserver listed probably 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:
ns1.avx.re ['188.8.131.52'] [TTL=600]
ns2.avx.re ['184.108.40.206'] [TTL=600]
|Mismatched NS records||Not OK. The NS records at all your nameservers are not 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. You must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok.|
|Domain CNAMEs||OK. There should be no CNAMEs if an NS (or any other) record is present.|
|NSs CNAME check||OK. There should be no CNAMEs if an NS (or any other) record is present.|
|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.|
The SOA record is:
Primary nameserver: ns1.avx.re
Hostmaster E-mail address: noc.avxhome.se
Serial #: 2017053100
Default TTL: 600
|SOA MNAME entry||Not OK. ns1.avx.re That server is not listed at the parent servers.|
|SOA Serial||Your SOA serial number is: 2017053100. This appears to be in the recommended format of YYYYMMDDnn.|
|SOA REFRESH||OK. Your SOA REFRESH interval is: 28800. That is OK.|
|SOA RETRY||Your SOA RETRY value is: 900. Looks ok|
|SOA EXPIRE||Your SOA EXPIRE number is: 86400. That is not OK|
|SOA MINIMUM TTL||Your SOA MINIMUM TTL is: 600. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). Recommended value is 1-3 hours. Your value of 600 is not OK.|
|MX||MX Records||Your MX records that were reported by your nameservers are:
10 mx.yandex.ru 220.127.116.11
[These are all the MX records that I found.]
|MX name validity||Good. I did not detect any invalid hostnames for your MX records.|
|MX IPs are public||OK. All of your MX records appear to use public IPs.|
|MX is not IP||OK. All of your MX records are host names.|
|Number of MX records||OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.|
|WWW||WWW A Record||
Your avxhome.se A record is:
avxhome.se -> [ 18.104.22.168 ][ 22.214.171.124 ][ 126.96.36.199 ]
|IPs are public||OK. All of your WWW IPs appear to be public IPs.|