Language
Your IP Address is:
SERP Analysis| Category | Status | Test Name | Information |
|---|---|---|---|
| Parent |  |
Domain NS records |
Nameserver records returned by the parent servers are: KINOPOISK.RU. 345600 IN NS ns4.yandex.RU. KINOPOISK.RU. 345600 IN NS ns3.yandex.RU. a.dns.ripn.net was kind enough to give us that information. |
 |
TLD Parent Check | Good. a.dns.ripn.net, the parent server I interrogated, has information for your TLD. | |
|
Nameservers listed | Good. The parent server a.dns.ripn.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. | |
|
DNS Parent sent Glue | Good. The parent nameserver 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. | |
|
Nameservers A records | Good. Every nameserver listed probably 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: ns3.yandex.ru ['87.250.250.1'] [TTL=86400] ns4.yandex.ru ['77.88.21.1'] [TTL=86400] |
|
Mismatched NS records | OK. The NS records at all your nameservers are identical. | |
|
DNS servers responded | Good. All nameservers listed at the parent server responded. | |
|
Name of nameservers are valid | OK. All of the NS records that your nameservers report seem valid. | |
|
Multiple Nameservers | Good. You have multiple nameservers. You must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok. | |
|
Domain CNAMEs | OK. There should be no CNAMEs if an NS (or any other) record is present. | |
|
NSs CNAME check | OK. There should be no CNAMEs if an NS (or any other) record is present. | |
|
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. | |
| SOA | |
SOA record |
The SOA record is: Primary nameserver: ns3.yandex.ru Hostmaster E-mail address: sysadmin.yandex.ru Serial #: 1660172227 Refresh: 900 Retry: 600 Expire: 3600000 Default TTL: 300 |
|
SOA MNAME entry | OK. ns3.yandex.ru That server is listed at the parent servers. | |
 |
SOA Serial | Your SOA serial number is: 1660172227. This can be ok if you know what you are doing. | |
|
SOA REFRESH | Looks not within recommended range. Your SOA REFRESH interval is: 900. | |
|
SOA RETRY | Your SOA RETRY value is: 600. Looks ok | |
|
SOA EXPIRE | Your SOA EXPIRE number is: 3600000. That is not OK | |
|
SOA MINIMUM TTL | Your SOA MINIMUM TTL is: 300. 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). Recommended value is 1-3 hours. Your value of 300 is OK. | |
| MX | |
MX Records | Your MX records that were reported by your nameservers are: 10 mx.yandex.ru 77.88.21.249 [These are all the MX records that I found.] |
|
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 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. | |
| WWW | |
WWW A Record |
Your www.kinopoisk.ru A record is: www.kinopoisk.ru -> [ 213.180.199.9 ] |
|
IPs are public | OK. All of your WWW IPs appear to be public IPs. |