Check DNS Report – Mail Servers Health Of Domain

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 :

Category Status Test name Information send feedback
Parent info Domain NS records Nameserver records returned by the parent servers are:




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

pass TLD Parent Check Good., 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.
pass Your nameservers are listed Good. 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.
pass 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)
pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found.
NS info NS records from your nameservers NS records got from your nameservers listed at the parent NS are:  [‘’]
[TTL=86400]  [‘’]

pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
pass 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!
info 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:
You can fix this for example by adding A records to your nameservers for the zones listed above.

pass Mismatched NS records OK. The NS records at all your nameservers are identical.
pass DNS servers responded Good. All nameservers listed at the parent server responded.
pass Name of nameservers are valid OK. All of the NS records that your nameservers report seem valid.
pass 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.
pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers.
pass Missing nameservers reported by your nameservers OK. All nameservers returned by the parent server are the same as the ones reported by your nameservers.
pass 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.
pass 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.
warn Different subnets WARNING: Not all of your nameservers are in different subnets
pass 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
pass 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.
warn Different autonomous systems WARNING: Single point of failure
pass Stealth NS records sent Ok. No stealth ns records are sent
SOA info SOA record The SOA record is:
Primary nameserver:
Hostmaster E-mail address:
Serial #: 2015081800
Refresh: 86400
Retry: 7200
Expire: 3600000   5 weeks
Default TTL: 86400
pass NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is 2015081800.
pass SOA MNAME entry OK. That server is listed at the parent servers.
pass SOA Serial Your SOA serial number is: 2015081800.

This appears to be in the recommended format of YYYYMMDDnn.

pass SOA REFRESH OK. Your SOA REFRESH interval is: 86400. That is OK
pass SOA RETRY Your SOA RETRY value is: 7200. Looks ok
warn SOA EXPIRE Your SOA EXPIRE number is: 3600000. That is NOT OK
pass SOA MINIMUM TTL Your 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.
MX info MX Records Your 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. ]
pass Different MX records at nameservers Good. 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
pass MX name validity Good. I did not detect any invalid hostnames for your MX records.
pass MX IPs are public OK. All of your MX records appear to use public IPs.
pass MX CNAME Check OK. No problems here.
pass MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
pass MX is not IP OK. All of your MX records are host names.
info 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.
pass Mismatched MX A OK. I did not detect differing IPs for your MX records.
pass Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
pass Reverse MX A records (PTR) Your reverse (PTR) record: ->

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

WWW info WWW A Record Your A record -> ->

[Looks like you have CNAME’s]

pass IPs are public OK. All of your WWW IPs appear to be public IPs.
pass WWW CNAME OK. 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.

Add Comment