Google.org DNS Tests

INFO	Using Root Server f.root-servers.net
PASS	Your TLD is recognized at the root servers.
INFO	Got redirected to a0.org.afilias-nst.info
INFO	Got redirected to ns4.google.com
PASS	You have 4 name servers. Anything more than 1 is good.

INFO	Name Server (NS) records at the TLD name server a0.org.afilias-nst.info: ns4.google.com ns3.google.com ns1.google.com ns2.google.com
INFO	The TLD name server a0.org.afilias-nst.info did not send A records (GLUE) for the name servers in the additional section!
INFO	ns4.google.com has the following A Records: 216.239.38.10 (TTL: 8251 seconds), located at Mountain View, United States
INFO	ns3.google.com has the following A Records: 216.239.36.10 (TTL: 9406 seconds), located at Mountain View, United States
INFO	ns1.google.com has the following A Records: 216.239.32.10 (TTL: 7619 seconds), located at Mountain View, United States
INFO	ns2.google.com has the following A Records: 216.239.34.10 (TTL: 5403 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 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 a0.org.afilias-nst.info.
PASS	Name server ns4.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 a0.org.afilias-nst.info.
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 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 a0.org.afilias-nst.info.
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 a0.org.afilias-nst.info.
PASS	Name server ns2.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 ns4.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 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	The SOA serial is the same at all your name servers.
PASS	None of your name servers seem to allow recursive queries.

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: 99)

INFO	google.org has the following AAAA Records: 2001:4860:4802:32:0:0:0:1b (TTL: 300 seconds). The IPv6 address is valid.

INFO	SOA Record: Serial: 259238398 Refresh: 900 seconds Retry: 900 seconds Expire: 1800 seconds Minimum TTL: 60 seconds Primary Name Server: ns1.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 (ns1.google.com) is sent by the TLD name server a0.org.afilias-nst.info for queries on google.org.

INFO	google.org has the following MX records: aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com alt2.aspmx.l.google.com alt1.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.20.27, located at Mountain View, United States.
INFO	Mail Server alt3.aspmx.l.google.com has the following A Records: 209.85.144.27, located at Mountain View, United States.
INFO	Mail Server alt4.aspmx.l.google.com has the following A Records: 74.125.141.27, located at Mountain View, United States.
INFO	Mail Server alt2.aspmx.l.google.com has the following A Records: 64.233.177.27, located at Mountain View, United States.
INFO	Mail Server alt1.aspmx.l.google.com has the following A Records: 74.125.129.27, located at Mountain View, United States.
PASS	All of your MX servers have A records.
PASS	All of your MX records are on different IP addresses. This is the recommended way of creating A Records for MX servers.
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.

PASS

After 10 lookups, the average response time of your name server ns4.google.com is 47.4 milliseconds:

	Los Angeles:	51.35 ms
	Dallas:	9.95 ms
	New York:	19.03 ms
	Singapore:	195.13 ms
	London:	8.31 ms
	Amsterdam:	9.24 ms
	San Francisco:	38.77 ms

INFO

Health: Across all queries that we sent to ns4.google.com, the success rate is 99.97% (uptime).

PASS

After 9 lookups, the average response time of your name server ns3.google.com is 19.09 milliseconds:

	Los Angeles:	20.3 ms
	Dallas:	7.41 ms
	New York:	14.07 ms
	Singapore:	51.81 ms
	London:	11.35 ms
	Amsterdam:	8.22 ms
	San Francisco:	20.46 ms

INFO

Health: Across all queries that we sent to ns3.google.com, the success rate is 99.95% (uptime).

PASS

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

	Los Angeles:	50.76 ms
	Dallas:	15.78 ms
	New York:	13.64 ms
	Singapore:	1.87 ms
	London:	6.61 ms
	Amsterdam:	8.44 ms
	San Francisco:	38.44 ms

INFO

Health: Across all queries that we sent to ns1.google.com, the success rate is 99.97% (uptime).

PASS

After 9 lookups, the average response time of your name server ns2.google.com is 13.04 milliseconds:

	Los Angeles:	20.78 ms
	Dallas:	7.41 ms
	New York:	13.96 ms
	Singapore:	1.86 ms
	London:	10.77 ms
	Amsterdam:	15.99 ms
	San Francisco:	20.49 ms

INFO

Health: Across all queries that we sent to ns2.google.com, the success rate is 99.95% (uptime).

A	Rating by SolveDNS google.org DNS tests had 0 failed tests and 3 warnings. 92.11% out of 100

Google.org DNS Tests

92.11% out of 100