SUCCESS
Parent nameservers know A records for your domain, Very good !
NS
Mismatched glue
0/7
The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(dns1.namecheaphosting.com. 172800 IN A 216.87.155.33) present at Parent, missing at (216.87.152.33)
(dns2.namecheaphosting.com. 172800 IN A 216.87.152.33) present at Parent, missing at (216.87.152.33)
Nameservers A records
0/7
Some servers does not provide A records for nameservers.
missing A record(s) for (dns11.namecheaphosting.com,dns12.namecheaphosting.com) at nameserver 216.87.152.33
Nameservers report identical NS records
7/7
SUCCESS
The NS records at all your nameservers are identical.
Nameservers respond
0/10
Some nameservers does not respond:
2620:74:19::33
Nameserver name validity
7/7
SUCCESS
All of the NS records that your nameservers report are valid (no IPs or partial domain names).
Number of nameservers
2/5
WARNING
You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
Lame nameservers
7/7
SUCCESS
All the nameservers listed at the parent servers answer authoritatively for your domain.
Missing (stealth) nameservers
0/7
DANGER
There are nameservers not listed at the parent servers:
SUCCESS
All of your NS records appear to use public IPs.
SOA
SOA record
SOA record is:
Hostmaster email
cpanel.tech.namecheap.com
Serial
2017080200
Refresh
86400
Retry
7200
Expire
3600000
TTL
1800000
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2017080200 That means that all your nameservers are using the same data.
SOA MNAME
0/3
DANGER
SOA (Start of Authority) record states that your master (primary) name server is: dns11.namecheaphosting.com, but that server is not listed at the parent servers.
Serial value
1/1
SUCCESS
SOA serial number is: 2017080200 This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. This number must be incremented every time you make a DNS change.
Refresh value
0/1
WARNING
SOA Retry interval is : 86400 seconds. This seems too big;. (Values about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.
Retry value
1/1
SUCCESS
SOA Retry interval is : 7200 seconds. This seems OK. (Values about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
Expire value
0/1
WARNING
SOA Expire time is : 3600000 seconds. This seems too big;. (Values 604800 to 2419200 seconds (1-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
TTL value
0/1
WARNING
SOA Expire time is : 1800000 seconds. This seems too big;. (about 300 to 86400 seconds or 5 min - 24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.
Info
DNS trace
Trace to shahzadnews.com
lookup shahzadnews.com at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup shahzadnews.com at e.gtld-servers.net(192.12.94.30) 9 ms
e.gtld-servers.net(192.12.94.30) refer to dns1.namecheaphosting.com(216.87.155.33)
lookup shahzadnews.com at dns1.namecheaphosting.com(216.87.155.33) 42 ms
got A record 'shahzadnews.com IN A 162.213.255.59' from shahzadnews.com(216.87.155.33)