DNS response history for ns03.heznercorp.com

ns03.heznercorp.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-27. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 390 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 ns03.heznercorp.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.168.1.8

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 ns03.heznercorp.com

Showing DNS history for 2026-08-27 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-27 10:23 639234222943951923
243 ms 192.168.1.8
31 2026-08-27 10:06 639234212558002823
238 ms 192.168.1.8
30 2026-08-27 09:49 639234202117531850
685 ms 192.168.1.8
29 2026-08-27 09:31 639234191649612722
350 ms 192.168.1.8
28 2026-08-27 09:14 639234181105879568
237 ms 192.168.1.8
27 2026-08-27 08:56 639234170713214496
692 ms 192.168.1.8
26 2026-08-27 08:39 639234160341037652
239 ms 192.168.1.8
25 2026-08-27 08:22 639234149799404224
363 ms 192.168.1.8
24 2026-08-27 08:04 639234139553286469
240 ms 192.168.1.8
23 2026-08-27 07:10 639234107183588293
241 ms 192.168.1.8
22 2026-08-27 06:53 639234096905435724
237 ms 192.168.1.8
21 2026-08-27 06:36 639234086579410775
241 ms 192.168.1.8
20 2026-08-27 06:19 639234076291157956
236 ms 192.168.1.8
19 2026-08-27 06:02 639234065981939454
238 ms 192.168.1.8
18 2026-08-27 05:45 639234055548642997
357 ms 192.168.1.8
17 2026-08-27 05:27 639234045267979603
240 ms 192.168.1.8
16 2026-08-27 05:10 639234034999717463
232 ms 192.168.1.8
15 2026-08-27 04:53 639234024739225358
234 ms 192.168.1.8
14 2026-08-27 04:36 639234014311170162
244 ms 192.168.1.8
13 2026-08-27 04:18 639234003806017640
235 ms 192.168.1.8
12 2026-08-27 04:01 639233993356203030
688 ms 192.168.1.8
11 2026-08-27 03:07 639233961301716608
219 ms 192.168.1.8
10 2026-08-27 02:50 639233950834200647
354 ms 192.168.1.8
9 2026-08-27 02:33 639233940431849026
688 ms 192.168.1.8
8 2026-08-27 02:15 639233930110596398
2149 ms 192.168.1.8
7 2026-08-27 01:58 639233919705434540
231 ms 192.168.1.8
6 2026-08-27 01:41 639233909452807845
228 ms 192.168.1.8
5 2026-08-27 01:24 639233899096420820
703 ms 192.168.1.8
4 2026-08-27 01:07 639233888707824939
370 ms 192.168.1.8
3 2026-08-27 00:49 639233878461203802
240 ms 192.168.1.8
2 2026-08-27 00:32 639233868060868209
352 ms 192.168.1.8
1 2026-08-27 00:14 639233857450922991
239 ms 192.168.1.8