Solve DNS Tests imdbcom.ru
    

All Tools  |  DNS Speed Test  |  Traceroute  |  Ping  |  Reverse DNS  |  DNS Analytics  |  DNS Comparison  |  Statistics  |  Blog  |  RBL  |  DNS Propagation

Imdbcom.ru DNS Tests

  
TLD ▼  |  Name Servers ▼  |  A Records ▼  |  Speed and Health ▼  |  AAAA Records ▼  |  MX Records ▼  |  SOA Record ▼
Top Level Domain

INFO
Using Root Server h.root-servers.net
PASS
Your TLD is recognized at the root servers.
INFO
Got redirected to a.dns.ripn.net
INFO
Got redirected to ns1.beget.com
PASS
You have 4 name servers. Anything more than 1 is good.

Name Servers

INFO
Name Server (NS) records at the TLD name server a.dns.ripn.net:

ns1.beget.com
ns1.beget.pro
ns2.beget.com
ns2.beget.pro
INFO
The TLD name server a.dns.ripn.net did not send A records (GLUE) for the name servers in the additional section!
INFO
ns1.beget.com has the following A Records:

5.101.159.11 (TTL: 229 seconds), located at
INFO
ns1.beget.pro has the following A Records:

5.101.159.11 (TTL: 230 seconds), located at
INFO
ns2.beget.com has the following A Records:

185.50.27.12 (TTL: 228 seconds), located at Europe
INFO
ns2.beget.pro has the following A Records:

185.50.27.12 (TTL: 228 seconds), located at Europe
PASS
All of your name servers have A records.
WARNING
Some of your name servers point to the same IP address! Having these seperate entries as NS records does not make sense.
PASS
Your name servers are geo distributed. This is the right thing to do to ensure the best availability
PASS
Your name server ns1.beget.com is responding to DNS queries.
WARNING
Name Servers Found at ns1.beget.com for imdbcom.ru NOT found at a.dns.ripn.net:

ns1.beget.ru
ns2.beget.ru
WARNING
Your name server ns1.beget.com is responding with a different set of NS records as compared to the TLD server a.dns.ripn.net!
WARNING
Name server ns1.beget.com did not send A records (GLUE) along with the response for the NS records query for imdbcom.ru.
PASS
Your name server ns1.beget.pro is responding to DNS queries.
WARNING
Name Servers Found at ns1.beget.pro for imdbcom.ru NOT found at a.dns.ripn.net:

ns1.beget.ru
ns2.beget.ru
WARNING
Your name server ns1.beget.pro is responding with a different set of NS records as compared to the TLD server a.dns.ripn.net!
WARNING
Name server ns1.beget.pro did not send A records (GLUE) along with the response for the NS records query for imdbcom.ru.
PASS
Your name server ns2.beget.com is responding to DNS queries.
WARNING
Name Servers Found at ns2.beget.com for imdbcom.ru NOT found at a.dns.ripn.net:

ns1.beget.ru
ns2.beget.ru
WARNING
Your name server ns2.beget.com is responding with a different set of NS records as compared to the TLD server a.dns.ripn.net!
WARNING
Name server ns2.beget.com did not send A records (GLUE) along with the response for the NS records query for imdbcom.ru.
PASS
Your name server ns2.beget.pro is responding to DNS queries.
WARNING
Name Servers Found at ns2.beget.pro for imdbcom.ru NOT found at a.dns.ripn.net:

ns1.beget.ru
ns2.beget.ru
WARNING
Your name server ns2.beget.pro is responding with a different set of NS records as compared to the TLD server a.dns.ripn.net!
WARNING
Name server ns2.beget.pro did not send A records (GLUE) along with the response for the NS records query for imdbcom.ru.
WARNING
The NS records returned by your name servers are not consistent with either the TLD server a.dns.ripn.net or some of your other name servers. See above. The reason for this could be that you have different name servers at your domain name registrar as compared to your NS records. Even if this could be ok, you should always have the same name servers at your registrar and at your NS records.
PASS
Your name server ns1.beget.com is authoritative for the domain name imdbcom.ru.
PASS
Your name server ns1.beget.pro is authoritative for the domain name imdbcom.ru.
PASS
Your name server ns2.beget.com is authoritative for the domain name imdbcom.ru.
PASS
Your name server ns2.beget.pro is authoritative for the domain name imdbcom.ru.
PASS
The SOA serial is the same at all your name servers.
PASS
None of your name servers seem to allow recursive queries.

A Records

INFO
imdbcom.ru has the following A Records:

87.236.16.208 (TTL: 600 seconds) is located at Russian Federation
PASS
The WWW record for imdbcom.ru (www.imdbcom.ru) has A Records. This is recommended. www.imdbcom.ru has the following A Records:

87.236.16.208 (TTL: 600)

AAAA Records

INFO
There are no AAAA records for your domain name at ns1.beget.com.

SOA Record

INFO
SOA Record:

Serial: 1570943219
Refresh: 300 seconds
Retry: 600 seconds
Expire: 86400 seconds
Minimum TTL: 300 seconds
Primary Name Server: ns1.beget.com
Contact: hostmaster.beget.com
WARNING
Your SOA refresh value is 300. The recommended value is between 1200 and 86400.
PASS
Your SOA Retry value 600 is OK. The recommended value is between 120 and 7200.
WARNING
Your SOA Expire value is 86400. The recommended value is between 604800 and 2419200.
WARNING
Your SOA Minimum TTL value is 300. This might be a little low. The recommended value is between 1800 and 86400.
PASS
The primary name server in the SOA record (ns1.beget.com) is sent by the TLD name server a.dns.ripn.net for queries on imdbcom.ru.

MX Records

INFO
imdbcom.ru has the following MX records:

mx1.beget.com
mx2.beget.com
INFO
Your name servers did not send A Records (GLUE) for your mail servers for MX queries.
INFO
Mail Server mx1.beget.com has the following A Records:

185.78.30.71 (TTL: 300 seconds), located at .
5.101.158.68 (TTL: 300 seconds), located at .
185.78.30.48 (TTL: 300 seconds), located at .
INFO
Mail Server mx2.beget.com has the following A Records:

5.101.158.67 (TTL: 300 seconds), located at .
185.78.30.48 (TTL: 300 seconds), located at .
185.78.30.71 (TTL: 300 seconds), located at .
PASS
All of your MX servers have A records.
WARNING
Some of your MX servers have duplicate IP addresses in the A records. This is not recommended. You should fix this.
PASS
You have 2 MX Records. Anything more than 1 is recommended.
PASS
Your domain name has an SPF record (v=spf1 redirect=beget.com). This prevents email spoofing.

Name Server Speed and Health

PASS
After 10 lookups, the average response time of your name server ns1.beget.com is 137.87 milliseconds:

Los Angeles:181.47 ms
Dallas:160.37 ms
New York:113.68 ms
Singapore:213.85 ms
London:58.96 ms
Amsterdam:52.7 ms
San Francisco:184.06 ms
INFO
Health: Across all queries that we sent to ns1.beget.com, the success rate is 99.97% (uptime).
PASS
After 8 lookups, the average response time of your name server ns1.beget.pro is 132.45 milliseconds:

Los Angeles:181.23 ms
Dallas:156.93 ms
New York:112.39 ms
Singapore:199.81 ms
London:51.26 ms
Amsterdam:48.08 ms
San Francisco:177.48 ms
INFO
Health: Across all queries that we sent to ns1.beget.pro, the success rate is 99.96% (uptime).
PASS
After 9 lookups, the average response time of your name server ns2.beget.com is 134.37 milliseconds:

Los Angeles:181.6 ms
Dallas:155.65 ms
New York:114.45 ms
Singapore:204.13 ms
London:59.05 ms
Amsterdam:47.98 ms
San Francisco:177.72 ms
INFO
Health: Across all queries that we sent to ns2.beget.com, the success rate is 99.97% (uptime).
PASS
After 9 lookups, the average response time of your name server ns2.beget.pro is 134.12 milliseconds:

Los Angeles:181.31 ms
Dallas:154.97 ms
New York:115.04 ms
Singapore:199.93 ms
London:58.53 ms
Amsterdam:48.43 ms
San Francisco:180.65 ms
INFO
Health: Across all queries that we sent to ns2.beget.pro, the success rate is 99.97% (uptime).

DNS Rating

B-
Rating by SolveDNS
imdbcom.ru DNS tests had 0 failed tests and 18 warnings.

57.14% out of 100



DNS Speed Test  |  SolveDNS Blog  |  NameServer Analytics  |  DNS Speed Comparison  |  Web Statistics  |  DNS Reviews

Contact: infoATsolvedns.com

© Copyright SolveDNS, All Rights Reserved