DNS response history for ns1.claimcybercrime.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

458 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.133

Most recently resolved hosting IP on selected date

Successful Responses

33

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.claimcybercrime.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
33 2026-08-25 11:48 639232545839529039
365 ms 162.240.160.133
32 2026-08-25 11:31 639232535349285207
349 ms 162.240.160.133
31 2026-08-25 11:14 639232524938080723
356 ms 162.240.160.133
30 2026-08-25 10:20 639232492740373468
353 ms 162.240.160.133
29 2026-08-25 10:03 639232482235303141
352 ms 162.240.160.133
28 2026-08-25 09:45 639232471861770303
355 ms 162.240.160.133
27 2026-08-25 09:28 639232461630217327
346 ms 162.240.160.133
26 2026-08-25 09:11 639232451282965990
345 ms 162.240.160.133
25 2026-08-25 08:54 639232440814614938
360 ms 162.240.160.133
24 2026-08-25 08:36 639232430410720425
351 ms 162.240.160.133
23 2026-08-25 08:19 639232420003096185
2178 ms 162.240.160.133
22 2026-08-25 08:01 639232409467287444
359 ms 162.240.160.133
21 2026-08-25 07:44 639232399077195997
358 ms 162.240.160.133
20 2026-08-25 07:27 639232388731528337
352 ms 162.240.160.133
19 2026-08-25 07:09 639232378288598612
346 ms 162.240.160.133
18 2026-08-25 06:16 639232346196373643
352 ms 162.240.160.133
17 2026-08-25 05:59 639232336112370741
339 ms 162.240.160.133
16 2026-08-25 05:42 639232326146508970
342 ms 162.240.160.133
15 2026-08-25 05:25 639232316189381720
342 ms 162.240.160.133
14 2026-08-25 05:09 639232306217998913
175 ms 162.240.160.133
13 2026-08-25 04:52 639232296255744174
2173 ms 162.240.160.133
12 2026-08-25 04:35 639232286095760789
342 ms 162.240.160.133
11 2026-08-25 04:19 639232276086186273
342 ms 162.240.160.133
10 2026-08-25 04:02 639232265900986425
342 ms 162.240.160.133
9 2026-08-25 03:45 639232255723518075
337 ms 162.240.160.133
8 2026-08-25 03:28 639232245484452890
342 ms 162.240.160.133
7 2026-08-25 03:11 639232235157175331
290 ms 162.240.160.133
6 2026-08-25 02:17 639232203197189095
566 ms 162.240.160.133
5 2026-08-25 02:00 639232192844564298
336 ms 162.240.160.133
4 2026-08-25 01:43 639232182496008942
338 ms 162.240.160.133
3 2026-08-25 01:26 639232172197053132
340 ms 162.240.160.133
2 2026-08-25 00:32 639232140250307418
338 ms 162.240.160.133
1 2026-08-25 00:15 639232129927860324
342 ms 162.240.160.133