DNS response history for ns3.maxguard.com

ns3.maxguard.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 524 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns3.maxguard.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

524 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.230.164

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns3.maxguard.com

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
34 2026-08-26 11:28 639233403515141099
40 ms 51.79.230.164
33 2026-08-26 10:33 639233370841350248
14 ms 51.79.230.164
32 2026-08-26 10:16 639233360361507238
21 ms 51.79.230.164
31 2026-08-26 09:59 639233350067824371
39 ms 51.79.230.164
30 2026-08-26 09:41 639233339545274518
67 ms 51.79.230.164
29 2026-08-26 09:24 639233329214918079
4039 ms 51.79.230.164
28 2026-08-26 09:07 639233318749762337
33 ms 51.79.230.164
27 2026-08-26 08:49 639233308387917838
28 ms 51.79.230.164
26 2026-08-26 08:32 639233297961740122
321 ms 51.79.230.164
25 2026-08-26 08:15 639233287487159094
22 ms 51.79.230.164
24 2026-08-26 07:57 639233276995531707
47 ms 51.79.230.164
23 2026-08-26 07:40 639233266521568229
20 ms 51.79.230.164
22 2026-08-26 07:22 639233256081047431
40 ms 51.79.230.164
21 2026-08-26 06:28 639233223620132921
131 ms 51.79.230.164
20 2026-08-26 06:11 639233213287814244
77 ms 51.79.230.164
19 2026-08-26 05:54 639233202925983161
2226 ms 51.79.230.164
18 2026-08-26 05:36 639233192644780696
34 ms 51.79.230.164
17 2026-08-26 05:19 639233182401183833
2037 ms 51.79.230.164
16 2026-08-26 05:02 639233172074181051
27 ms 51.79.230.164
15 2026-08-26 04:45 639233161808421455
30 ms 51.79.230.164
14 2026-08-26 04:28 639233151357344052
31 ms 51.79.230.164
13 2026-08-26 04:10 639233141034116946
23 ms 51.79.230.164
12 2026-08-26 03:53 639233130828334142
23 ms 51.79.230.164
11 2026-08-26 03:36 639233120373450007
10 ms 51.79.230.164
10 2026-08-26 03:19 639233110066216193
29 ms 51.79.230.164
9 2026-08-26 02:25 639233078065410564
2141 ms 51.79.230.164
8 2026-08-26 02:08 639233067787457832
13 ms 51.79.230.164
7 2026-08-26 01:51 639233057501801162
40 ms 51.79.230.164
6 2026-08-26 01:34 639233047089431703
33 ms 51.79.230.164
5 2026-08-26 01:17 639233036754790688
4031 ms 51.79.230.164
4 2026-08-26 00:59 639233026412602472
2068 ms 51.79.230.164
3 2026-08-26 00:42 639233016064066127
30 ms 51.79.230.164
2 2026-08-26 00:25 639233005922655772
18 ms 51.79.230.164
1 2026-08-26 00:08 639232995672256907
28 ms 51.79.230.164