DNS audit for grimsby.ca created on 2026-08-14 05:56:38

PDF

1. Name servers

Name servers listed at the parent server d.ca-servers.ca:

ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

Result: 6 name servers found at the parent server (set at the domain provider).
Recommendation: Everything is okay. There is more than one name server added to grimsby.ca.

2. NS records

NS records returned by each name server configured for the domain name

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns2.he.net [216.218.131.2] (4ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns3.he.net [216.218.132.2] (2ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns101.cloudns.net [185.136.96.99] (2ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns102.cloudns.net [185.136.97.99] (1ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns103.cloudns.net [185.136.98.99] (1ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns104.cloudns.net [185.136.99.99] (1ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns2.he.net [216.218.131.2] (273ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns3.he.net [216.218.132.2] (265ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns101.cloudns.net [185.136.96.99] (1ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns102.cloudns.net [185.136.97.99] (113ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns103.cloudns.net [185.136.98.99] (1ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns104.cloudns.net [185.136.99.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns2.he.net [216.218.131.2] (156ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns3.he.net [216.218.132.2] (156ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns101.cloudns.net [185.136.96.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns102.cloudns.net [185.136.97.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns103.cloudns.net [185.136.98.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns104.cloudns.net [185.136.99.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns2.he.net [216.218.131.2] (171ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

ns3.he.net [216.218.132.2] (166ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns101.cloudns.net [185.136.96.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns102.cloudns.net [185.136.97.99] (1ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns103.cloudns.net [185.136.98.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

pns104.cloudns.net [185.136.99.99] (0ms):
ns2.he.net
ns3.he.net
pns101.cloudns.net
pns102.cloudns.net
pns103.cloudns.net
pns104.cloudns.net

Result: The NS records returned by the DNS servers are the same as the name servers set at the parent server.
Recommendation: It is not required to do any changes. All name servers are synchronized.

3. SOA record

SOA record returned by each name server configured for the domain name

San Francisco, US

ns2.he.net [216.218.131.2] (2ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

ns3.he.net [216.218.132.2] (2ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns101.cloudns.net [185.136.96.99] (1ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns102.cloudns.net [185.136.97.99] (1ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns103.cloudns.net [185.136.98.99] (1ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns104.cloudns.net [185.136.99.99] (1ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

Sydney, AU

ns2.he.net [216.218.131.2] (272ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

ns3.he.net [216.218.132.2] (272ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns101.cloudns.net [185.136.96.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns102.cloudns.net [185.136.97.99] (163ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns103.cloudns.net [185.136.98.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns104.cloudns.net [185.136.99.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

Johannesburg, ZA

ns2.he.net [216.218.131.2] (152ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

ns3.he.net [216.218.132.2] (152ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns101.cloudns.net [185.136.96.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns102.cloudns.net [185.136.97.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns103.cloudns.net [185.136.98.99] (4ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns104.cloudns.net [185.136.99.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

Singapore

ns2.he.net [216.218.131.2] (1ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

ns3.he.net [216.218.132.2] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns101.cloudns.net [185.136.96.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns102.cloudns.net [185.136.97.99] (1ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns103.cloudns.net [185.136.98.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

pns104.cloudns.net [185.136.99.99] (0ms):
pns101.cloudns.net. support.cloudns.net. 2026081404 7200 1800 1209600 3600

Result: The SOA record returned by the name servers is the same on all of them.
Recommendation: It is not required to do any changes. The name servers are synchronized.

4. A record distribution by location for grimsby.ca

Shows how the name servers respond to requests for grimsby.ca

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns2.he.net [216.218.131.2] (2ms):
20.104.12.1

ns3.he.net [216.218.132.2] (2ms):
20.104.12.1

pns101.cloudns.net [185.136.96.99] (1ms):
20.104.12.1

pns102.cloudns.net [185.136.97.99] (1ms):
20.104.12.1

pns103.cloudns.net [185.136.98.99] (1ms):
20.104.12.1

pns104.cloudns.net [185.136.99.99] (1ms):
20.104.12.1

ns2.he.net [216.218.131.2] (264ms):
20.104.12.1

ns3.he.net [216.218.132.2] (265ms):
20.104.12.1

pns101.cloudns.net [185.136.96.99] (1ms):
20.104.12.1

pns102.cloudns.net [185.136.97.99] (161ms):
20.104.12.1

pns103.cloudns.net [185.136.98.99] (0ms):
20.104.12.1

pns104.cloudns.net [185.136.99.99] (1ms):
20.104.12.1

ns2.he.net [216.218.131.2] (152ms):
20.104.12.1

ns3.he.net [216.218.132.2] (152ms):
20.104.12.1

pns101.cloudns.net [185.136.96.99] (0ms):
20.104.12.1

pns102.cloudns.net [185.136.97.99] (0ms):
20.104.12.1

pns103.cloudns.net [185.136.98.99] (0ms):
20.104.12.1

pns104.cloudns.net [185.136.99.99] (0ms):
20.104.12.1

ns2.he.net [216.218.131.2] (1ms):
20.104.12.1

ns3.he.net [216.218.132.2] (0ms):
20.104.12.1

pns101.cloudns.net [185.136.96.99] (1ms):
20.104.12.1

pns102.cloudns.net [185.136.97.99] (1ms):
20.104.12.1

pns103.cloudns.net [185.136.98.99] (0ms):
20.104.12.1

pns104.cloudns.net [185.136.99.99] (0ms):
20.104.12.1

5. A record distribution by location for www.grimsby.ca

Shows how the name servers respond to requests for www.grimsby.ca

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns2.he.net [216.218.131.2] (2ms):

ns3.he.net [216.218.132.2] (1ms):

pns101.cloudns.net [185.136.96.99] (1ms):

pns102.cloudns.net [185.136.97.99] (1ms):

pns103.cloudns.net [185.136.98.99] (1ms):

pns104.cloudns.net [185.136.99.99] (1ms):

ns2.he.net [216.218.131.2] (272ms):

ns3.he.net [216.218.132.2] (264ms):

pns101.cloudns.net [185.136.96.99] (0ms):

pns102.cloudns.net [185.136.97.99] (113ms):

pns103.cloudns.net [185.136.98.99] (1ms):

pns104.cloudns.net [185.136.99.99] (1ms):

ns2.he.net [216.218.131.2] (156ms):

ns3.he.net [216.218.132.2] (156ms):

pns101.cloudns.net [185.136.96.99] (0ms):

pns102.cloudns.net [185.136.97.99] (0ms):

pns103.cloudns.net [185.136.98.99] (0ms):

pns104.cloudns.net [185.136.99.99] (0ms):

ns2.he.net [216.218.131.2] (0ms):

ns3.he.net [216.218.132.2] (0ms):

pns101.cloudns.net [185.136.96.99] (0ms):

pns102.cloudns.net [185.136.97.99] (0ms):

pns103.cloudns.net [185.136.98.99] (0ms):

pns104.cloudns.net [185.136.99.99] (1ms):

6. Speed

Result: During the checks in the previous steps, multiple DNS requests were executed to the name servers responsible for the domain name. Average response time of the name servers is 45.34ms.
Recommendation: The name servers have good response time.

Previous reports for grimsby.ca: 2026-08-14 05:56:27 , 2026-08-13 20:49:47 , 2026-08-13 17:15:01 , 2026-08-13 17:14:59
Blog | Cloud DNS
Sponsored by ClouDNS