INFO | Name Server (NS) records at the TLD name server a.gtld-servers.net:
ns1.dynamicnetworkservices.net
ns2.dynamicnetworkservices.net
ns3.dynamicnetworkservices.net
ns4.dynamicnetworkservices.net
ns5.dynamicnetworkservices.net
ns6.dynamicnetworkservices.net
ns7.dynamicnetworkservices.net |
PASS | The TLD name server a.gtld-servers.net sent A records (GLUE) for the name servers of dyntld.net in the additional section of the response. This speeds up the computation by avoiding an additional DNS query for the A records of the name servers. |
INFO | ns1.dynamicnetworkservices.net has the following A Records:
208.78.70.136, located at Manchester, United States |
INFO | ns2.dynamicnetworkservices.net has the following A Records:
204.13.250.136, located at Manchester, United States |
INFO | ns3.dynamicnetworkservices.net has the following A Records:
208.78.71.136, located at Manchester, United States |
INFO | ns4.dynamicnetworkservices.net has the following A Records:
204.13.251.136, located at Manchester, United States |
INFO | ns5.dynamicnetworkservices.net has the following A Records:
162.88.60.21, located at Wheeling, United States |
INFO | ns6.dynamicnetworkservices.net has the following A Records:
162.88.61.21, located at Wheeling, United States |
INFO | ns7.dynamicnetworkservices.net has the following A Records:
108.59.165.1, located at Pepperell, United States |
PASS | All of your name servers have A records. |
PASS | All of your name servers are on seperate IP addresses. |
PASS | Your name servers are geo distributed. This is the right thing to do to ensure the best availability |
PASS | Your name server ns1.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns1.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
WARNING | Name server ns1.dynamicnetworkservices.net did not send A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | Your name server ns2.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns2.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
WARNING | Name server ns2.dynamicnetworkservices.net did not send A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | Your name server ns3.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns3.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
WARNING | Name server ns3.dynamicnetworkservices.net did not send A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | Your name server ns4.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns4.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
WARNING | Name server ns4.dynamicnetworkservices.net did not send A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | Your name server ns5.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns5.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
PASS | Name server ns5.dynamicnetworkservices.net sent A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | Your name server ns6.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns6.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
PASS | Name server ns6.dynamicnetworkservices.net sent A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | Your name server ns7.dynamicnetworkservices.net is responding to DNS queries. |
PASS | Your name server ns7.dynamicnetworkservices.net is responding with the same set of NS records as compared to the TLD server a.gtld-servers.net. |
PASS | Name server ns7.dynamicnetworkservices.net sent A records (GLUE) along with the response for the NS records query for dyntld.net. |
PASS | All of your name servers return the same NS records. |
PASS | Your name server ns1.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | Your name server ns2.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | Your name server ns3.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | Your name server ns4.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | Your name server ns5.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | Your name server ns6.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | Your name server ns7.dynamicnetworkservices.net is authoritative for the domain name dyntld.net. |
PASS | The SOA serial is the same at all your name servers. |
PASS | None of your name servers seem to allow recursive queries. |
INFO | dyntld.net has the following MX records:
ALT1.ASPMX.L.GOOGLE.COM
ALT2.ASPMX.L.GOOGLE.COM
ASPMX3.GOOGLEMAIL.COM
ASPMX2.GOOGLEMAIL.COM
ASPMX.L.GOOGLE.COM |
INFO | Your name servers did not send A Records (GLUE) for your mail servers for MX queries. |
INFO | Mail Server alt1.aspmx.l.google.com has the following A Records:
209.85.146.26 (TTL: 271 seconds), located at Mountain View, United States. |
INFO | Mail Server alt2.aspmx.l.google.com has the following A Records:
173.194.209.26 (TTL: 96 seconds), located at Mountain View, United States. |
INFO | Mail Server aspmx3.googlemail.com has the following A Records:
173.194.209.26 (TTL: 69 seconds), located at Mountain View, United States. |
INFO | Mail Server aspmx2.googlemail.com has the following A Records:
209.85.146.27 (TTL: 279 seconds), located at Mountain View, United States. |
INFO | Mail Server aspmx.l.google.com has the following A Records:
142.250.138.26 (TTL: 14 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 5 MX Records. Anything more than 1 is recommended. |
WARNING | Your domain name does not appear to have an SPF record. This makes it vulnerable to email spoofing. |
PASS | After 8 lookups, the average response time of your name server ns1.dynamicnetworkservices.net is 3.46 milliseconds:
 | Los Angeles: | 4.37 ms | | Dallas: | 4.49 ms | | New York: | 3.68 ms | | Singapore: | 1.74 ms | | London: | 2.95 ms | | Amsterdam: | 2.18 ms | | San Francisco: | 4.8 ms |
|
INFO | Health: Across all queries that we sent to ns1.dynamicnetworkservices.net, the success rate is 99.65% (uptime). |
PASS | After 8 lookups, the average response time of your name server ns2.dynamicnetworkservices.net is 9.81 milliseconds:
| Los Angeles: | 14.88 ms | | Dallas: | 34.57 ms | | New York: | 5.04 ms | | Singapore: | 1.54 ms | | London: | 7.2 ms | | Amsterdam: | 1.91 ms | | San Francisco: | 3.5 ms |
|
INFO | Health: Across all queries that we sent to ns2.dynamicnetworkservices.net, the success rate is 99.80% (uptime). |
PASS | After 10 lookups, the average response time of your name server ns3.dynamicnetworkservices.net is 2.42 milliseconds:
| Los Angeles: | 3.66 ms | | Dallas: | 1.81 ms | | New York: | 2.11 ms | | Singapore: | 1.31 ms | | London: | 1.74 ms | | Amsterdam: | 2.04 ms | | San Francisco: | 4.28 ms |
|
INFO | Health: Across all queries that we sent to ns3.dynamicnetworkservices.net, the success rate is 99.89% (uptime). |
PASS | After 8 lookups, the average response time of your name server ns4.dynamicnetworkservices.net is 9.2 milliseconds:
| Los Angeles: | 4.22 ms | | Dallas: | 1.73 ms | | New York: | 7.15 ms | | Singapore: | 36.65 ms | | London: | 2.09 ms | | Amsterdam: | 1.87 ms | | San Francisco: | 10.71 ms |
|
INFO | Health: Across all queries that we sent to ns4.dynamicnetworkservices.net, the success rate is 99.94% (uptime). |
PASS | After 10 lookups, the average response time of your name server ns5.dynamicnetworkservices.net is 7.52 milliseconds:
| Los Angeles: | 16.86 ms | | Dallas: | 2.82 ms | | New York: | 7.91 ms | | Singapore: | 2.65 ms | | London: | 2.97 ms | | Amsterdam: | 9.2 ms | | San Francisco: | 10.26 ms |
|
INFO | Health: Across all queries that we sent to ns5.dynamicnetworkservices.net, the success rate is 99.93% (uptime). |
PASS | After 8 lookups, the average response time of your name server ns6.dynamicnetworkservices.net is 7.63 milliseconds:
| Los Angeles: | 18.03 ms | | Dallas: | 1.87 ms | | New York: | 7.15 ms | | Singapore: | 2.57 ms | | London: | 2.51 ms | | Amsterdam: | 9.31 ms | | San Francisco: | 11.99 ms |
|
INFO | Health: Across all queries that we sent to ns6.dynamicnetworkservices.net, the success rate is 99.93% (uptime). |
PASS | After 8 lookups, the average response time of your name server ns7.dynamicnetworkservices.net is 205.94 milliseconds:
| Los Angeles: | 277.91 ms | | Dallas: | 247.72 ms | | New York: | 217.7 ms | | Singapore: | 117.18 ms | | London: | 142.26 ms | | Amsterdam: | 158.26 ms | | San Francisco: | 280.58 ms |
|
INFO | Health: Across all queries that we sent to ns7.dynamicnetworkservices.net, the success rate is 99.67% (uptime). |
