Solve DNS Tests google.org
    

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

Google.org DNS Tests

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

INFO
Using Root Server d.root-servers.net
PASS
Your TLD is recognized at the root servers.
INFO
Got redirected to b2.org.afilias-nst.org
INFO
Got redirected to ns1.google.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 b2.org.afilias-nst.org:

ns1.google.com
ns2.google.com
ns3.google.com
ns4.google.com
INFO
The TLD name server b2.org.afilias-nst.org did not send A records (GLUE) for the name servers in the additional section!
INFO
ns1.google.com has the following A Records:

216.239.32.10 (TTL: 117705 seconds), located at Mountain View, United States
INFO
ns2.google.com has the following A Records:

216.239.34.10 (TTL: 120585 seconds), located at Mountain View, United States
INFO
ns3.google.com has the following A Records:

216.239.36.10 (TTL: 30817 seconds), located at Mountain View, United States
INFO
ns4.google.com has the following A Records:

216.239.38.10 (TTL: 170032 seconds), located at Mountain View, United States
PASS
All of your name servers have A records.
PASS
All of your name servers are on seperate IP addresses.
INFO
The A records of your name servers indicate that your name servers are not geo distributed. It is recommended that your name servers be in different geographical locations to ensure the best availability.
PASS
Your name server ns1.google.com is responding to DNS queries.
PASS
Your name server ns1.google.com is responding with the same set of NS records as compared to the TLD server b2.org.afilias-nst.org.
PASS
Name server ns1.google.com sent A records (GLUE) along with the response for the NS records query for google.org.
PASS
Your name server ns2.google.com is responding to DNS queries.
PASS
Your name server ns2.google.com is responding with the same set of NS records as compared to the TLD server b2.org.afilias-nst.org.
PASS
Name server ns2.google.com sent A records (GLUE) along with the response for the NS records query for google.org.
PASS
Your name server ns3.google.com is responding to DNS queries.
PASS
Your name server ns3.google.com is responding with the same set of NS records as compared to the TLD server b2.org.afilias-nst.org.
PASS
Name server ns3.google.com sent A records (GLUE) along with the response for the NS records query for google.org.
PASS
Your name server ns4.google.com is responding to DNS queries.
PASS
Your name server ns4.google.com is responding with the same set of NS records as compared to the TLD server b2.org.afilias-nst.org.
PASS
Name server ns4.google.com sent A records (GLUE) along with the response for the NS records query for google.org.
PASS
All of your name servers return the same NS records.
PASS
Your name server ns1.google.com is authoritative for the domain name google.org.
PASS
Your name server ns2.google.com is authoritative for the domain name google.org.
PASS
Your name server ns3.google.com is authoritative for the domain name google.org.
PASS
Your name server ns4.google.com is authoritative for the domain name google.org.
WARNING
The SOA record serial number differs between your name servers! This is not expected unless you have recently created your domain name or name servers and the data has not propagated to all your servers yet. Please check after a few hours and then if this test fails again, you need to fix it.
PASS
None of your name servers seem to allow recursive queries.

A Records

INFO
google.org has the following A Records:

216.239.32.27 (TTL: 300 seconds) is located at Mountain View, United States
PASS
The WWW record for google.org (www.google.org) has A Records. This is recommended. www.google.org has the following A Records:

216.239.32.27 (TTL: 300)

AAAA Records

INFO
google.org has the following AAAA Records:

2001:4860:4802:32:0:0:0:1b (TTL: 300 seconds). The IPv6 address is valid.

SOA Record

INFO
SOA Record:

Serial: 147997944
Refresh: 900 seconds
Retry: 900 seconds
Expire: 1800 seconds
Minimum TTL: 60 seconds
Primary Name Server: ns2.google.com
Contact: dns-admin.google.com
WARNING
Your SOA refresh value is 900. The recommended value is between 1200 and 86400.
PASS
Your SOA Retry value 900 is OK. The recommended value is between 120 and 7200.
WARNING
Your SOA Expire value is 1800. The recommended value is between 604800 and 2419200.
WARNING
Your SOA Minimum TTL value is 60. This might be a little low. The recommended value is between 1800 and 86400.
PASS
The primary name server in the SOA record (ns2.google.com) is sent by the TLD name server b2.org.afilias-nst.org for queries on google.org.

MX Records

INFO
google.org has the following MX records:

aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
PASS
Your name servers sent A Records (GLUE) for your mail servers for MX queries. This speeds up the DNS lookups.
INFO
Mail Server aspmx.l.google.com has the following A Records:

74.125.128.27, located at Mountain View, United States.
INFO
Mail Server alt3.aspmx.l.google.com has the following A Records:

74.125.128.27, located at Mountain View, United States.
INFO
Mail Server alt4.aspmx.l.google.com has the following A Records:

74.125.128.27, located at Mountain View, United States.
INFO
Mail Server alt1.aspmx.l.google.com has the following A Records:

74.125.128.27, located at Mountain View, United States.
INFO
Mail Server alt2.aspmx.l.google.com has the following A Records:

74.125.128.27, located at Mountain View, United States.
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 5 MX Records. Anything more than 1 is recommended.
PASS
Your domain name has an SPF record (v=spf1 include:_spf.google.com ~all). This prevents email spoofing.

Name Server Speed and Health

PASS
After 8 lookups, the average response time of your name server ns1.google.com is 22.3 milliseconds:

Los Angeles:29.53 ms
Dallas:11.5 ms
New York:15.51 ms
Singapore:52.73 ms
London:11.48 ms
Amsterdam:14.09 ms
San Francisco:21.26 ms
INFO
Health: Across all queries that we sent to ns1.google.com, the success rate is 99.95% (uptime).
PASS
After 11 lookups, the average response time of your name server ns2.google.com is 19.35 milliseconds:

Los Angeles:41.12 ms
Dallas:8.21 ms
New York:21.63 ms
Singapore:2.59 ms
London:11.14 ms
Amsterdam:4.41 ms
San Francisco:46.36 ms
INFO
Health: Across all queries that we sent to ns2.google.com, the success rate is 99.90% (uptime).
PASS
After 9 lookups, the average response time of your name server ns3.google.com is 35.03 milliseconds:

Los Angeles:65.5 ms
Dallas:34.71 ms
New York:15.61 ms
Singapore:52.41 ms
London:6.68 ms
Amsterdam:4.3 ms
San Francisco:65.99 ms
INFO
Health: Across all queries that we sent to ns3.google.com, the success rate is 99.93% (uptime).
PASS
After 8 lookups, the average response time of your name server ns4.google.com is 37.9 milliseconds:

Los Angeles:30.15 ms
Dallas:28.69 ms
New York:19.4 ms
Singapore:153.83 ms
London:7.07 ms
Amsterdam:5 ms
San Francisco:21.16 ms
INFO
Health: Across all queries that we sent to ns4.google.com, the success rate is 99.95% (uptime).

DNS Rating

A
Rating by SolveDNS
google.org DNS tests had 0 failed tests and 5 warnings.

86.84% 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