DNS response history for ns2.webcore.top

ns2.webcore.top 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 32 DNS check records, 32 successful responses, 0 failed responses, and 358 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 ns2.webcore.top.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

358 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.248.240.23

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 ns2.webcore.top

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
32 2026-08-25 11:29 639232535349285207
158 ms 66.248.240.23
31 2026-08-25 11:11 639232524938080723
176 ms 66.248.240.23
30 2026-08-25 10:18 639232492740373468
4 ms 66.248.240.23
29 2026-08-25 10:01 639232482235303141
483 ms 66.248.240.23
28 2026-08-25 09:43 639232471861770303
141 ms 66.248.240.23
27 2026-08-25 09:26 639232461630217327
301 ms 66.248.240.23
26 2026-08-25 09:09 639232451282965990
2162 ms 66.248.240.23
25 2026-08-25 08:51 639232440814614938
304 ms 66.248.240.23
24 2026-08-25 08:34 639232430410720425
296 ms 66.248.240.23
23 2026-08-25 08:17 639232420003096185
300 ms 66.248.240.23
22 2026-08-25 07:59 639232409467287444
226 ms 66.248.240.23
21 2026-08-25 07:42 639232399077195997
21 ms 66.248.240.23
20 2026-08-25 07:24 639232388731528337
311 ms 66.248.240.23
19 2026-08-25 07:07 639232378288598612
229 ms 66.248.240.23
18 2026-08-25 06:13 639232346196373643
294 ms 66.248.240.23
17 2026-08-25 05:56 639232336112370741
143 ms 66.248.240.23
16 2026-08-25 05:40 639232326146508970
2141 ms 66.248.240.23
15 2026-08-25 05:23 639232316189381720
213 ms 66.248.240.23
14 2026-08-25 05:07 639232306217998913
291 ms 66.248.240.23
13 2026-08-25 04:50 639232296255744174
152 ms 66.248.240.23
12 2026-08-25 04:33 639232286095760789
468 ms 66.248.240.23
11 2026-08-25 04:16 639232276086186273
173 ms 66.248.240.23
10 2026-08-25 04:00 639232265900986425
296 ms 66.248.240.23
9 2026-08-25 03:43 639232255723518075
147 ms 66.248.240.23
8 2026-08-25 03:26 639232245484452890
286 ms 66.248.240.23
7 2026-08-25 03:08 639232235157175331
291 ms 66.248.240.23
6 2026-08-25 02:15 639232203197189095
290 ms 66.248.240.23
5 2026-08-25 01:58 639232192844564298
155 ms 66.248.240.23
4 2026-08-25 01:41 639232182496008942
286 ms 66.248.240.23
3 2026-08-25 01:23 639232172197053132
290 ms 66.248.240.23
2 2026-08-25 00:30 639232140250307418
293 ms 66.248.240.23
1 2026-08-25 00:13 639232129927860324
144 ms 66.248.240.23