DNS response history for ns1.ginzadijital.com

ns1.ginzadijital.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 164 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 ns1.ginzadijital.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

164 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.125.28.108

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns1.ginzadijital.com

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:34 639231745628278877
4 ms 135.125.28.108
31 2026-08-24 13:17 639231735407682062
5 ms 135.125.28.108
30 2026-08-24 12:24 639231703815441688
16 ms 135.125.28.108
29 2026-08-24 12:07 639231693747052549
34 ms 135.125.28.108
28 2026-08-24 11:51 639231683712487276
65 ms 135.125.28.108
27 2026-08-24 11:34 639231673513573868
48 ms 135.125.28.108
26 2026-08-24 10:41 639231641791249939
49 ms 135.125.28.108
25 2026-08-24 10:24 639231631866211033
33 ms 135.125.28.108
24 2026-08-24 10:07 639231621644955316
38 ms 135.125.28.108
23 2026-08-24 09:50 639231611478799259
58 ms 135.125.28.108
22 2026-08-24 08:58 639231579923718211
39 ms 135.125.28.108
21 2026-08-24 08:41 639231569810702936
20 ms 135.125.28.108
20 2026-08-24 08:24 639231559762411619
13 ms 135.125.28.108
19 2026-08-24 08:07 639231549663595407
7 ms 135.125.28.108
18 2026-08-24 07:15 639231518076817246
4 ms 135.125.28.108
17 2026-08-24 06:58 639231508078650885
73 ms 135.125.28.108
16 2026-08-24 06:41 639231498210697093
51 ms 135.125.28.108
15 2026-08-24 06:25 639231488109699360
2076 ms 135.125.28.108
14 2026-08-24 05:33 639231456772510692
4 ms 135.125.28.108
13 2026-08-24 05:16 639231447084631185
199 ms 135.125.28.108
12 2026-08-24 05:00 639231437208519473
63 ms 135.125.28.108
11 2026-08-24 04:43 639231427209627490
16 ms 135.125.28.108
10 2026-08-24 03:51 639231395791246644
38 ms 135.125.28.108
9 2026-08-24 03:35 639231386075551458
2062 ms 135.125.28.108
8 2026-08-24 03:18 639231376208713791
71 ms 135.125.28.108
7 2026-08-24 03:01 639231366170589276
3 ms 135.125.28.108
6 2026-08-24 02:09 639231334732159368
33 ms 135.125.28.108
5 2026-08-24 01:53 639231325035670078
3 ms 135.125.28.108
4 2026-08-24 01:36 639231315132253837
52 ms 135.125.28.108
3 2026-08-24 01:20 639231305014280808
60 ms 135.125.28.108
2 2026-08-24 00:27 639231273779380675
7 ms 135.125.28.108
1 2026-08-24 00:11 639231264180839154
5 ms 135.125.28.108