Check DNS Report – Mail Servers Health Of Domain

DNS Report - Mail Servers Health

DNS (Domain Name System) and mail server configuration checking is extremely vital for a domain.You need to make sure that all DNS status are green marked and active.I had trouble regarding launching my site.I published my homepage but the I saw a blank page.I tried to configure all possible DNS setting and name server but I couldn’t solve it.I am hosting with Hostgator,therefore, I went for of their online chat support.

I explained all issues and name server setting which I did from my side.The chat person tried to resolve my problem.They use smart tool for verifying the DNS error and mail server setting.He informed me that the name server I am using was incorrect as they have changed recently their server.Well,I got the solution in a minute and learn about their checking process.

What do they use ?

I thought that they manually checked my site.I was wrong,my site was checked at IntoDNS.I found all the major reports regarding DNS and mail server setting.From now you don’t need assistance for checking any misconfiguration.You can do it following simple steps :

  1. Visit IntoDNS
  2. Enter domain name without HTTP:// (i.e –
  3. Click on Report button.

Check DNS Report - Mail Servers Health Of Domain

I checked my site and found no error.let me share the status I received :

CategoryStatusTest nameInformation send feedback
ParentinfoDomain NS recordsNameserver records returned by the parent servers are:




[TTL=172800] was kind enough to give us that information.

passTLD Parent CheckGood., the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like “” for example that are missing a direct check.
passYour nameservers are listedGood. The parent server 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.
passDNS Parent sent GlueGood. 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)
passNameservers A recordsGood. Every nameserver listed has A records. This is a must if you want to be found.
NSinfoNS records from your nameserversNS records got from your nameservers listed at the parent NS are:  [‘’]
[TTL=86400]  [‘’]

passRecursive QueriesGood. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
passSame GlueThe 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!
infoGlue for NS recordsINFO: 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:
You can fix this for example by adding A records to your nameservers for the zones listed above.

passMismatched NS recordsOK. The NS records at all your nameservers are identical.
passDNS servers respondedGood. All nameservers listed at the parent server responded.
passName of nameservers are validOK. All of the NS records that your nameservers report seem valid.
passMultiple NameserversGood. 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.
passNameservers are lameOK. All the nameservers listed at the parent servers answer authoritatively for your domain.
passMissing nameservers reported by parentOK. All NS records are the same at the parent and at your nameservers.
passMissing nameservers reported by your nameserversOK. All nameservers returned by the parent server are the same as the ones reported by your nameservers.
passDomain CNAMEsOK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
passNSs CNAME checkOK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
warnDifferent subnetsWARNING: Not all of your nameservers are in different subnets
passIPs of nameservers are publicOk. 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
passDNS servers allow TCP connectionOK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
warnDifferent autonomous systemsWARNING: Single point of failure
passStealth NS records sentOk. No stealth ns records are sent
SOAinfoSOA recordThe SOA record is:
Primary nameserver:
Hostmaster E-mail address:
Serial #: 2015081800
Refresh: 86400
Retry: 7200
Expire: 3600000   5 weeks
Default TTL: 86400
passNSs have same SOA serialOK. All your nameservers agree that your SOA serial number is 2015081800.
passSOA MNAME entryOK. That server is listed at the parent servers.
passSOA SerialYour SOA serial number is: 2015081800.

This appears to be in the recommended format of YYYYMMDDnn.

passSOA REFRESHOK. Your SOA REFRESH interval is: 86400. That is OK
passSOA RETRYYour SOA RETRY value is: 7200. Looks ok
warnSOA EXPIREYour SOA EXPIRE number is: 3600000. That is NOT OK
passSOA MINIMUM TTLYour SOA MINIMUM TTL is: 86400. 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). RFC2308 recommends a value of 1-3 hours. Your value of 86400 is OK.
MXinfoMX RecordsYour MX records that were reported by your nameservers are:
0   latestweb4.com103.21.59.198[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
passDifferent MX records at nameserversGood. Looks like all your nameservers have the same set of MX records. This tests to see if there are
any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
passMX name validityGood. I did not detect any invalid hostnames for your MX records.
passMX IPs are publicOK. All of your MX records appear to use public IPs.
passMX CNAME CheckOK. No problems here.
passMX A request returns CNAMEOK. No CNAMEs returned for A records lookups.
passMX is not IPOK. All of your MX records are host names.
infoNumber of MX recordsOK. 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.
passMismatched MX AOK. I did not detect differing IPs for your MX records.
passDuplicate MX A recordsOK. I have not found duplicate IP(s) for your MX records. This is a good thing.
passReverse MX A records (PTR)Your reverse (PTR) record: ->

You have reverse (PTR) records for all your IPs, that is a good thing.

WWWinfoWWW A RecordYour A record -> ->

[Looks like you have CNAME’s]

passIPs are publicOK. All of your WWW IPs appear to be public IPs.
passWWW CNAMEOK. You do have a CNAME record for CNAME entry also returns the A record for the CNAME entry, which is good.

If you see any error with a red alert that means you need to re-configure.Correct the setting and again recheck with intoDNS.

Intaj Mondal
Intaj Mondal,He is a passionate blogger from India.He loves to write on several topics related Blog,Internet,Money making methods and more others.You can find me on