DNS response history for maxzipper.com

maxzipper.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 31 DNS check records, 31 successful responses, 0 failed responses, and 552 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 maxzipper.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

552 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

220.128.119.173

Most recently resolved hosting IP on selected date

Successful Responses

31

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 maxzipper.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
31 2026-08-26 09:53 639233339545274518
619 ms 220.128.119.173
30 2026-08-26 09:35 639233329214918079
603 ms 220.128.119.173
29 2026-08-26 09:18 639233318749762337
603 ms 220.128.119.173
28 2026-08-26 09:00 639233308387917838
612 ms 220.128.119.173
27 2026-08-26 08:43 639233297961740122
590 ms 220.128.119.173
26 2026-08-26 08:26 639233287487159094
602 ms 220.128.119.173
25 2026-08-26 08:08 639233276995531707
613 ms 220.128.119.173
24 2026-08-26 07:51 639233266521568229
622 ms 220.128.119.173
23 2026-08-26 07:33 639233256081047431
623 ms 220.128.119.173
22 2026-08-26 06:39 639233223620132921
620 ms 220.128.119.173
21 2026-08-26 06:22 639233213287814244
618 ms 220.128.119.173
20 2026-08-26 06:05 639233202925983161
607 ms 220.128.119.173
19 2026-08-26 05:47 639233192644780696
606 ms 220.128.119.173
18 2026-08-26 05:30 639233182401183833
3 ms 220.128.119.173
17 2026-08-26 05:13 639233172074181051
590 ms 220.128.119.173
16 2026-08-26 04:56 639233161808421455
610 ms 220.128.119.173
15 2026-08-26 04:39 639233151357344052
601 ms 220.128.119.173
14 2026-08-26 04:21 639233141034116946
617 ms 220.128.119.173
13 2026-08-26 04:04 639233130828334142
599 ms 220.128.119.173
12 2026-08-26 03:47 639233120373450007
593 ms 220.128.119.173
11 2026-08-26 03:30 639233110066216193
597 ms 220.128.119.173
10 2026-08-26 02:37 639233078065410564
3 ms 220.128.119.173
9 2026-08-26 02:19 639233067787457832
605 ms 220.128.119.173
8 2026-08-26 02:02 639233057501801162
612 ms 220.128.119.173
7 2026-08-26 01:45 639233047089431703
3 ms 220.128.119.173
6 2026-08-26 01:28 639233036754790688
614 ms 220.128.119.173
5 2026-08-26 01:11 639233026412602472
601 ms 220.128.119.173
4 2026-08-26 00:53 639233016064066127
606 ms 220.128.119.173
3 2026-08-26 00:36 639233005922655772
598 ms 220.128.119.173
2 2026-08-26 00:19 639232995672256907
599 ms 220.128.119.173
1 2026-08-26 00:02 639232985300872416
713 ms 220.128.119.173