DNS response history for ns2.copesites.com.directideleteddomain.info

ns2.copesites.com.directideleteddomain.info 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 31 DNS check records, 31 successful responses, 0 failed responses, and 1787 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.copesites.com.directideleteddomain.info.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

1787 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.91.197.66

Most recently resolved hosting IP on selected date

Successful Responses

31

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.copesites.com.directideleteddomain.info

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
31 2026-08-25 10:23 639232492740373468
733 ms 208.91.197.66
30 2026-08-25 10:06 639232482235303141
2251 ms 208.91.197.66
29 2026-08-25 09:48 639232471861770303
2146 ms 208.91.197.66
28 2026-08-25 09:31 639232461630217327
148 ms 208.91.197.66
27 2026-08-25 09:14 639232451282965990
3994 ms 208.91.197.66
26 2026-08-25 08:57 639232440814614938
2139 ms 208.91.197.66
25 2026-08-25 08:39 639232430410720425
135 ms 208.91.197.66
24 2026-08-25 08:22 639232420003096185
129 ms 208.91.197.66
23 2026-08-25 08:05 639232409467287444
4137 ms 208.91.197.66
22 2026-08-25 07:47 639232399077195997
137 ms 208.91.197.66
21 2026-08-25 07:30 639232388731528337
2245 ms 208.91.197.66
20 2026-08-25 07:13 639232378288598612
2131 ms 208.91.197.66
19 2026-08-25 06:19 639232346196373643
2447 ms 208.91.197.66
18 2026-08-25 06:02 639232336112370741
2139 ms 208.91.197.66
17 2026-08-25 05:45 639232326146508970
161 ms 208.91.197.66
16 2026-08-25 05:28 639232316189381720
728 ms 208.91.197.66
15 2026-08-25 05:12 639232306217998913
2252 ms 208.91.197.66
14 2026-08-25 04:55 639232296255744174
140 ms 208.91.197.66
13 2026-08-25 04:38 639232286095760789
723 ms 208.91.197.66
12 2026-08-25 04:22 639232276086186273
2323 ms 208.91.197.66
11 2026-08-25 04:05 639232265900986425
2308 ms 208.91.197.66
10 2026-08-25 03:48 639232255723518075
2246 ms 208.91.197.66
9 2026-08-25 03:31 639232245484452890
136 ms 208.91.197.66
8 2026-08-25 03:14 639232235157175331
2138 ms 208.91.197.66
7 2026-08-25 02:20 639232203197189095
2244 ms 208.91.197.66
6 2026-08-25 02:03 639232192844564298
2258 ms 208.91.197.66
5 2026-08-25 01:46 639232182496008942
2246 ms 208.91.197.66
4 2026-08-25 01:29 639232172197053132
2310 ms 208.91.197.66
3 2026-08-25 00:35 639232140250307418
4189 ms 208.91.197.66
2 2026-08-25 00:19 639232129927860324
173 ms 208.91.197.66
1 2026-08-25 00:01 639232119551972438
3902 ms 208.91.197.66