![]() |
![]() |
| Category | Status | Test name | Information |
|---|---|---|---|
| Parent | ![]() |
Domain NS records | Nameserver records returned by the parent servers are: ns5.sgnetway.net. ['64.130.209.25'] (NO GLUE) [TTL=14400] dns1.taghrib.ir. ['188.126.135.59'] (NO GLUE) [TTL=14400] ns1.nic.ir was kind enough to give me that information. |
![]() |
TLD Parent Check | Good. ns1.nic.ir, 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. | |
![]() |
Your nameservers are listed | Good. The parent server ns1.nic.ir 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. | |
![]() |
DNS Parent sent Glue | Sorry , one or more of the parent nameserver did not send GLUE. | |
![]() |
Nameservers A records | Good. Every nameserver listed 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: ns5.sgnetway.net. ['64.130.209.25'] [TTL=3600] ns4.sgnetway.net. ['64.130.209.24'] [TTL=3600] dns1.taghrib.ir. ['dns1.taghrib.ir'] [TTL=3600] |
![]() |
Recursive Queries | Sorry , i was able to use your nameservers to performe recursive queries.Problem record(s) are : dns1.taghrib.ir Security Problem : DNS cache poisoning |
|
![]() |
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. | |
![]() |
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. | |
![]() |
Mismatched NS records | Sorry. The NS records at one or more your nameservers are not identical. | |
![]() |
DNS servers responded | Good. All nameservers listed at the parent server responded. | |
![]() |
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. | |
![]() |
Nameservers are lame | ERROR: looks like you have lame nameservers. The following nameservers are lame:
64.130.209.25 188.126.135.59 |
|
![]() |
Missing nameservers reported by parent | FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns4.sgnetway.net |
|
![]() |
Missing nameservers reported by your nameservers | OK. All nameservers returned by the parent server ns1.nic.ir are the same as the ones reported by your nameservers. | |
![]() |
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. | |
![]() |
Different subnets | OK. Looks like you have nameservers on different subnets! | |
![]() |
IPs of nameservers are public | Sorry. Looks like one or more IP addresses of your nameservers are private. This is not a good thing because it will cause DNS delays and other problems like | |
![]() |
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. | |
![]() |
Different autonomous systems | OK. It seems you are safe from a single point of failure. You must be carefull about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. | |
![]() |
Stealth NS records sent | Ok. No stealth ns records are sent | |
| SOA | ![]() |
SOA record | The SOA record is: Primary nameserver: server.taghrib.ir Hostmaster E-mail address: hostmaster Serial #: 26 Refresh: 900 Retry: 600 Expire: 86400 Default TTL: 3600 |
![]() |
NSs have same SOA serial | Sorry , but one or more of your nameservers don't agree that your SOA serial number is 26. | |
![]() |
SOA MNAME entry | Sorry, But server.taghrib.ir is not listed at the parent servers. | |
![]() |
SOA Serial | Your SOA serial number is: 26. This appears to be in the recommended format of YYYYMMDDnn. | |
![]() |
SOA REFRESH | OK. Your SOA REFRESH interval is: 900. That is OK | |
![]() |
SOA RETRY | Your SOA RETRY value is: 600. Looks ok | |
![]() |
SOA EXPIRE | Your SOA EXPIRE number is: 86400.Looks ok | |
![]() |
SOA MINIMUM TTL | Your SOA MINIMUM TTL is: 3600. 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 3600 is OK. | |
| MX | ![]() |
MX Records | Your MX records that were reported by your nameservers are: 10 webmail.taghrib.ir 188.126.135.59 [These are all the MX records that I found.] |
![]() |
Different MX records at nameservers | Sorry , i found Different MX records at nameservers | |
![]() |
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 carefull 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. | |
![]() |
Reverse MX A records (PTR) | Your reverse (PTR) record: 59.135.126.188.in-addr.arpa -> 188.126.135.59.arianrp.ir You have reverse (PTR) records for all your IPs, that is a good thing. |
|
| WWW | ![]() |
WWW A Record |
Your www.taghrib.ir A record is: www.taghrib.ir -> [64.130.209.44] |
I cannot connect to the database because: Access denied for user 'mainseo_main1'@'localhost' (using password: YES)