DNS response history for ns1.hezareh3.com

ns1.hezareh3.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 26 DNS check records, 26 successful responses, 0 failed responses, and 289 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.hezareh3.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

289 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.110.161.200

Most recently resolved hosting IP on selected date

Successful Responses

26

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.hezareh3.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
26 2026-08-26 08:37 639233297961740122
46 ms 78.110.161.200
25 2026-08-26 08:20 639233287487159094
79 ms 78.110.161.200
24 2026-08-26 08:03 639233276995531707
79 ms 78.110.161.200
23 2026-08-26 07:45 639233266521568229
61 ms 78.110.161.200
22 2026-08-26 07:28 639233256081047431
28 ms 78.110.161.200
21 2026-08-26 06:34 639233223620132921
49 ms 78.110.161.200
20 2026-08-26 06:16 639233213287814244
78 ms 78.110.161.200
19 2026-08-26 05:59 639233202925983161
47 ms 78.110.161.200
18 2026-08-26 05:42 639233192644780696
4124 ms 78.110.161.200
17 2026-08-26 05:25 639233182401183833
45 ms 78.110.161.200
16 2026-08-26 05:08 639233172074181051
45 ms 78.110.161.200
15 2026-08-26 04:50 639233161808421455
62 ms 78.110.161.200
14 2026-08-26 04:33 639233151357344052
27 ms 78.110.161.200
13 2026-08-26 04:16 639233141034116946
46 ms 78.110.161.200
12 2026-08-26 03:59 639233130828334142
46 ms 78.110.161.200
11 2026-08-26 03:42 639233120373450007
2030 ms 78.110.161.200
10 2026-08-26 03:24 639233110066216193
53 ms 78.110.161.200
9 2026-08-26 02:31 639233078065410564
46 ms 78.110.161.200
8 2026-08-26 02:14 639233067787457832
47 ms 78.110.161.200
7 2026-08-26 01:57 639233057501801162
48 ms 78.110.161.200
6 2026-08-26 01:39 639233047089431703
169 ms 78.110.161.200
5 2026-08-26 01:22 639233036754790688
44 ms 78.110.161.200
4 2026-08-26 01:05 639233026412602472
70 ms 78.110.161.200
3 2026-08-26 00:48 639233016064066127
56 ms 78.110.161.200
2 2026-08-26 00:31 639233005922655772
49 ms 78.110.161.200
1 2026-08-26 00:14 639232995672256907
36 ms 78.110.161.200