Loading...
Category Status Test name Information
Parent
Info
Domain NS records Nameserver records returned by the parent servers are:

ns2.ploger.ir.   ['115.124.118.10']   [TTL=14400]

ns1.ploger.ir.   ['115.124.118.9']   [TTL=14400]

auth02.ns.uu.net was kind enough to give me that information.
Pass
TLD Parent Check Good. auth02.ns.uu.net, the parent server I interogated, 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.
Pass
Your nameservers are listed Good. The parent server auth02.ns.uu.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.
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 nameserversNS records got from your nameservers listed at the parent NS are:

Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.

Pass
Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
error
Same Glue Sorry , but the A records (the GLUE) got from the parent zone check are not the same as the ones got from your nameservers.
Pass
Glue for NS records OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
error
Mismatched NS records Sorry. The NS records at one or more your nameservers are not identical.
Pass
DNS servers responded Good. All nameservers listed at the parent server responded.
error
Multiple Nameservers Sorry , but you have less than 2 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.
error
Nameservers are lame ERROR: looks like you have lame nameservers. The following nameservers are lame:
115.124.118.10
115.124.118.9
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 auth02.ns.uu.net are the same as the ones reported by your nameservers.
error
Domain CNAMEs Sorry , RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
error
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 usefull even if UDP connections are used by default.
error
Different autonomous systems WARNING: Single point of failure
Pass
Stealth NS records sent Ok. No stealth ns records are sent
SOA
Info
SOA recordThe SOA record is:
Primary nameserver:
Hostmaster E-mail address:
Serial #:
Refresh:
Retry:
Expire:
Default TTL:
Pass
NSs have same SOA serial OK. All your nameservers agree that your SOA serial number is .
warn
SOA MNAME entry Sorry, But is not listed at the parent servers.
Pass
SOA Serial Your SOA serial number is: . This appears to be in the recommended format of YYYYMMDDnn.
Pass
SOA REFRESH OK. Your SOA REFRESH interval is: . That is OK
Pass
SOA RETRY Your SOA RETRY value is: . Looks ok
Pass
SOA EXPIRE Your SOA EXPIRE number is: .Looks ok
Pass
SOA MINIMUM TTL Your SOA MINIMUM TTL is: . 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). Your value of is OK.
MX
Info
MX RecordsYour MX records that were reported by your nameservers are:



[These are all the MX records that I found.]
warn
Different MX records at nameservers Sorry , i found Different MX records at nameservers
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 is not IP OK. All of your MX records are host names.
error
Number of MX records Sorry. Looks like you have no MX record at your nameservers !!
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 www.night-skin.ir A record is:
www.night-skin.ir ->


Static Link to the Status and Trends of http://www.night-skin.ir