DNS response history for ns1.gohearst.com

ns1.gohearst.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-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 230 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.gohearst.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

230 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.220.199.6

Most recently resolved hosting IP on selected date

Successful Responses

38

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.gohearst.com

Showing DNS history for 2026-08-25 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
38 2026-08-25 13:11 639232597643611557
130 ms 74.220.199.6
37 2026-08-25 12:54 639232587225721862
33 ms 74.220.199.6
36 2026-08-25 12:37 639232576780683689
271 ms 74.220.199.6
35 2026-08-25 12:19 639232566381512620
253 ms 74.220.199.6
34 2026-08-25 12:02 639232556111768563
138 ms 74.220.199.6
33 2026-08-25 11:45 639232545839529039
275 ms 74.220.199.6
32 2026-08-25 11:28 639232535349285207
255 ms 74.220.199.6
31 2026-08-25 11:10 639232524938080723
147 ms 74.220.199.6
30 2026-08-25 10:16 639232492740373468
243 ms 74.220.199.6
29 2026-08-25 09:59 639232482235303141
129 ms 74.220.199.6
28 2026-08-25 09:42 639232471861770303
139 ms 74.220.199.6
27 2026-08-25 09:25 639232461630217327
133 ms 74.220.199.6
26 2026-08-25 09:07 639232451282965990
124 ms 74.220.199.6
25 2026-08-25 08:50 639232440814614938
262 ms 74.220.199.6
24 2026-08-25 08:33 639232430410720425
276 ms 74.220.199.6
23 2026-08-25 08:15 639232420003096185
132 ms 74.220.199.6
22 2026-08-25 07:58 639232409467287444
147 ms 74.220.199.6
21 2026-08-25 07:40 639232399077195997
125 ms 74.220.199.6
20 2026-08-25 07:23 639232388731528337
129 ms 74.220.199.6
19 2026-08-25 07:06 639232378288598612
301 ms 74.220.199.6
18 2026-08-25 06:12 639232346196373643
151 ms 74.220.199.6
17 2026-08-25 05:55 639232336112370741
243 ms 74.220.199.6
16 2026-08-25 05:39 639232326146508970
128 ms 74.220.199.6
15 2026-08-25 05:22 639232316189381720
4 ms 74.220.199.6
14 2026-08-25 05:06 639232306217998913
133 ms 74.220.199.6
13 2026-08-25 04:49 639232296255744174
260 ms 74.220.199.6
12 2026-08-25 04:32 639232286095760789
251 ms 74.220.199.6
11 2026-08-25 04:15 639232276086186273
246 ms 74.220.199.6
10 2026-08-25 03:58 639232265900986425
123 ms 74.220.199.6
9 2026-08-25 03:42 639232255723518075
5 ms 74.220.199.6
8 2026-08-25 03:24 639232245484452890
125 ms 74.220.199.6
7 2026-08-25 03:07 639232235157175331
252 ms 74.220.199.6
6 2026-08-25 02:14 639232203197189095
124 ms 74.220.199.6
5 2026-08-25 01:57 639232192844564298
246 ms 74.220.199.6
4 2026-08-25 01:40 639232182496008942
2138 ms 74.220.199.6
3 2026-08-25 01:22 639232172197053132
159 ms 74.220.199.6
2 2026-08-25 00:29 639232140250307418
251 ms 74.220.199.6
1 2026-08-25 00:12 639232129927860324
246 ms 74.220.199.6