DNS Test and Check – Free DNS Report
DNSsy Report Results
Results for google.com
|
Test |
Results |
Status |
|
Checking domain format: |
Hostname looks good. |
Pass |
|
Checking for parent nameservers: |
Found 13 parent nameservers. |
Pass |
|
Checking for parent glue: |
Glue from root nameservers to parent nameservers is missing. This means that an extra lookup is required to find your parent nameservers. There is nothing you can do about this. |
Info |
|
NS records at parent nameserver: |
Your NS records at your parent nameserver are: |
Info |
|
Nameservers listed at parent: |
Your nameservers are listed at the parent nameserver. |
Pass |
|
Glue at parent nameserver: |
Glue is provided from parent nameserver to your nameservers. This means they provided the IP address of your nameservers, so one less step is required in resolving your domain. This gives better performance. |
Pass |
|
Nameserver name validity: |
The parent nameserver responded with NS records that appear valid. |
Pass |
|
Nameserver A records: |
All of your nameservers have A records. |
Pass |
|
Nameserver A records match parent glue: |
All of the glue provided by the parent nameserver matches the A records for your nameservers. |
Pass |
|
NS records at your nameservers: |
Your NS records at your nameservers are: |
Info |
|
Nameservers listed at your namservers: |
Your nameservers are listed at your nameservers. |
Pass |
|
Glue at your nameservers: |
Glue is provided by your nameservers. This means they provided the IP address of your nameservers. |
Pass |
|
Nameserver A records match nameserver glue: |
All of the glue provided by your nameserver matches the A records for your nameservers. |
Pass |
|
Parent glue matches your glue: |
The glue provided by the parent nameserver and your nameserver matches. |
Pass |
|
Nameservers match (parent): |
All nameservers returned by the parent nameserver are also returned by your nameserver. |
Pass |
|
Nameservers match (yours): |
All nameservers returned by the your nameservers are also returned by the parent nameserver. |
Pass |
|
All nameservers responded: |
All of your nameservers responded. |
Pass |
|
Only root nameservers returned: |
Your nameservers returned at least 1 non-root nameserver referernce. |
Pass |
|
Any root nameservers returned: |
Your nameservers did not return any root nameserver referernces. |
Pass |
|
All of your nameservers match: |
All of your nameservers return the same nameserver records. |
Pass |
|
All of your nameservers return an A record: |
All of your nameservers returned an A record for your domain. |
Pass |
|
Recursive lookups: |
None of your nameservers support recursive lookups. |
Pass |
|
Nameservers respond authoritatively: |
All of your nameservers responded authoritatively for your domain. |
Pass |
|
Nameserver name validity: |
All of your nameservers responded with NS records that appear va |
Pass |
|
Number of nameservers: |
You have 4. nameservers. This is perfect. |
Pass |
|
CNAME returned: |
No CNAMES found when looking up your domain at your nameservers. |
Pass |
|
Nameservers on different class C: |
Your nameservers are of different class C IP addresses. This is an indication (but not proof) that they may not be co-located. |
Pass |
|
Nameservers on private IPs: |
Your nameservers appear to be on public IP addresses. |
Pass |
|
SOA record: |
Your SOA record at ns4.google.com: |
Info |
|
Number of SOA records: |
Each of your nameservers returned exactly 1 SOA record. |
Pass |
|
SOA Serial Match: |
Each of your nameservers returned the same SOA serial number. |
Pass |
|
SOA Master Nameserver Match: |
Each of your nameservers returned the same SOA master nameserver. |
Pass |
|
SOA Admin Email Match: |
Each of your nameservers returned the same SOA admin email address. |
Pass |
|
SOA Refresh Match: |
Each of your nameservers returned the same SOA refresh value. |
Pass |
|
SOA Retry Match: |
Each of your nameservers returned the same SOA retry value. |
Pass |
|
SOA Expire Match: |
Each of your nameservers returned the same SOA expire value. |
Pass |
|
SOA Minimum TTL Match: |
Each of your nameservers returned the same SOA minimum TTL value. |
Pass |
|
SOA Serial Number: |
Your SOA serial number matches the recommended format YYYYMMDDnn [RIPE-203]. |
Pass |
|
SOA Master Nameserver: |
Your SOA master nameserver is ns1.google.com. It is also listed at the parent nameservers. This is correct. |
Pass |
|
SOA Admin Email: |
Your SOA admin email address is dns-admin@google.com. This seems to be a valid email address. |
Pass |
|
SOA Refresh: |
Your SOA refresh value is 2 hours. This specifies how often a slave nameserver checks for DNS updates at the master. This seems to be OK. RFC 1912 recommends values between 20 minutes and 12 hours. |
Pass |
|
SOA Retry: |
Your SOA retry value is 30 mins. This is the time a slave nameserver will wait if an attempt to contact a primary nameserver failed before it tries again. This seems to be OK. |
Pass |
|
SOA Expire: |
Your SOA expire value is 14 days. This is how long a slave nameserver will cache data if it cannot reach the master nameserver. If your master nameserver is unreachable for longer than this your slave nameservers will no longer cache your DNS. This seems to be OK. |
Pass |
|
SOA Minimum TTL: |
Your SOA minimum TTL value is 5 mins. This is interpreted by servers as the default TTL. It can be overridden on individual DNS entries. This seems low. Unless you are expecting frequent DNS changes or must react quickly to DNS changes you should consider increasing this value. Anything between 1 hour and 4 hours is OK with me. |
Performance |
|
MX records: |
I found the following MX records: |
Info |
|
All nameservers return same MX: |
All of your nameservers returned the same MX records. |
Pass |
|
MX records have A records: |
All of your MX servers have A records. |
Pass |
|
MX records have CNAMEs: |
None of your MX servers have CNAME records. This is good. |
Pass |
|
MX records are IPs: |
None of your MX records are IP addresses. This is good. |
Pass |
|
MX records are valid: |
All of your MX records appear to be valid hostnames. |
Pass |
|
MX use public IP: |
All of your MX servers have public IP addresses. |
Pass |
|
MX IPs have reverse DNS: |
All of your MX servers have reverse DNS (PTR) entries. This is good since some mail server will refuse to accept email from you. |
Pass |
|
Connecting to MX 173.194.67.26: |
I was unable to connect to the SMTP port on 173.194.67.26. I only waited 5 seconds, so it may be that your mail server is slow, or may not be responding. Skipping further tests for 173.194.67.26 |
Fail |
|
Connecting to MX 173.194.70.26: |
I was unable to connect to the SMTP port on 173.194.70.26. I only waited 5 seconds, so it may be that your mail server is slow, or may not be responding. Skipping further tests for 173.194.70.26 |
Fail |
|
Connecting to MX 74.125.141.26: |
I was unable to connect to the SMTP port on 74.125.141.26. I only waited 5 seconds, so it may be that your mail server is slow, or may not be responding. Skipping further tests for 74.125.141.26 |
Fail |
|
Connecting to MX 173.194.69.27: |
I was unable to connect to the SMTP port on 173.194.69.27. I only waited 5 seconds, so it may be that your mail server is slow, or may not be responding. Skipping further tests for 173.194.69.27 |
Fail |
|
Connecting to MX 173.194.71.27: |
I was unable to connect to the SMTP port on 173.194.71.27. I only waited 5 seconds, so it may be that your mail server is slow, or may not be responding. Skipping further tests for 173.194.71.27 |
Fail |
|
WWW record: |
You have a WWW record setup for your domain. |
Pass |
|
WWW is public: |
Your WWW record is a public IP address. |
Pass |
|
Connecting to WWW server: |
Connected to WWW port on www.google.com OK. |
Pass |
|
Checking HTTP version: |
HTTP version 1.1 supported. |
Pass |
|
WWW server type: |
Your web server says it is: |
Info |
|
WWW server version: |
Your web server does not appear to reveal version information. |
Pass |
|
WWW home page: |
Your web server is redirecting your home page to http://www.google.co.uk/ |
Info |
Source: DNSsy – DNS Test and Check – Free DNS Report
Resources:
intoDNS: google.com – check DNS server and mail server health
Traceroute, Ping, Domain Name Server (DNS) Lookup, WHOIS ping www.google.com
<
