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:
ASPMX3.GOOGLEMAIL.COM
ASPMX2.GOOGLEMAIL.COM
ALT1.ASPMX.L.GOOGLE.COM
ALT2.ASPMX.L.GOOGLE.COM
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 aspmx3.googlemail.com has the following A Records:
142.250.11.27 (TTL: 111 seconds), located at . |
INFO | Mail Server aspmx2.googlemail.com has the following A Records:
74.125.129.26 (TTL: 90 seconds), located at Mountain View, United States. |
INFO | Mail Server alt1.aspmx.l.google.com has the following A Records:
74.125.129.26 (TTL: 100 seconds), located at Mountain View, United States. |
INFO | Mail Server alt2.aspmx.l.google.com has the following A Records:
142.250.11.26 (TTL: 212 seconds), located at . |
INFO | Mail Server aspmx.l.google.com has the following A Records:
74.125.28.27 (TTL: 79 seconds), 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. |
WARNING | Your domain name does not appear to have an SPF record. This makes it vulnerable to email spoofing. |
PASS | After 9 lookups, the average response time of your name server ns1.dynamicnetworkservices.net is 3.26 milliseconds:
 | Los Angeles: | 3.39 ms | | Dallas: | 5.12 ms | | New York: | 3.39 ms | | Singapore: | 2.7 ms | | London: | 3.1 ms | | Amsterdam: | 2.43 ms | | San Francisco: | 2.69 ms |
|
INFO | Health: Across all queries that we sent to ns1.dynamicnetworkservices.net, the success rate is 99.61% (uptime). |
PASS | After 9 lookups, the average response time of your name server ns2.dynamicnetworkservices.net is 107.21 milliseconds:
| Los Angeles: | 243.77 ms | | Dallas: | 2.33 ms | | New York: | 192.26 ms | | Singapore: | 60.86 ms | | London: | 129.76 ms | | Amsterdam: | 119.13 ms | | San Francisco: | 2.37 ms |
|
INFO | Health: Across all queries that we sent to ns2.dynamicnetworkservices.net, the success rate is 99.78% (uptime). |
PASS | After 8 lookups, the average response time of your name server ns3.dynamicnetworkservices.net is 2.27 milliseconds:
| Los Angeles: | 3.12 ms | | Dallas: | 2.73 ms | | New York: | 2.12 ms | | Singapore: | 1.77 ms | | London: | 2.1 ms | | Amsterdam: | 1.71 ms | | San Francisco: | 2.36 ms |
|
INFO | Health: Across all queries that we sent to ns3.dynamicnetworkservices.net, the success rate is 99.88% (uptime). |
PASS | After 9 lookups, the average response time of your name server ns4.dynamicnetworkservices.net is 7.88 milliseconds:
| Los Angeles: | 3.07 ms | | Dallas: | 27.9 ms | | New York: | 6.52 ms | | Singapore: | 1.72 ms | | London: | 1.84 ms | | Amsterdam: | 1.64 ms | | San Francisco: | 12.49 ms |
|
INFO | Health: Across all queries that we sent to ns4.dynamicnetworkservices.net, the success rate is 99.93% (uptime). |
PASS | After 8 lookups, the average response time of your name server ns5.dynamicnetworkservices.net is 7.76 milliseconds:
| Los Angeles: | 16.04 ms | | Dallas: | 2.78 ms | | New York: | 7.91 ms | | Singapore: | 2.56 ms | | London: | 2.93 ms | | Amsterdam: | 8.93 ms | | San Francisco: | 13.14 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.38 milliseconds:
| Los Angeles: | 17.03 ms | | Dallas: | 2.57 ms | | New York: | 6.42 ms | | Singapore: | 2.12 ms | | London: | 2.59 ms | | Amsterdam: | 8.78 ms | | San Francisco: | 12.16 ms |
|
INFO | Health: Across all queries that we sent to ns6.dynamicnetworkservices.net, the success rate is 99.93% (uptime). |
PASS | After 9 lookups, the average response time of your name server ns7.dynamicnetworkservices.net is 210.43 milliseconds:
| Los Angeles: | 290.44 ms | | Dallas: | 251.9 ms | | New York: | 218.74 ms | | Singapore: | 119.1 ms | | London: | 144.63 ms | | Amsterdam: | 157.02 ms | | San Francisco: | 291.15 ms |
|
INFO | Health: Across all queries that we sent to ns7.dynamicnetworkservices.net, the success rate is 99.82% (uptime). |
