DNS response history for ns1.crackmes.blog

ns1.crackmes.blog 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-24. For this date, NameServerHistory found 37 DNS check records, 35 successful responses, 2 failed responses, and 519 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.crackmes.blog.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

519 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

40.233.88.84

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.crackmes.blog

Showing DNS history for 2026-08-24 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
37 2026-08-24 15:37 639231818080917481
114 ms 40.233.88.84
36 2026-08-24 15:20 639231807961539652
235 ms 40.233.88.84
35 2026-08-24 15:03 639231797631669865
239 ms 40.233.88.84
34 2026-08-24 14:10 639231765923559455
814 ms 40.233.88.84
33 2026-08-24 13:53 639231755868832964
120 ms 40.233.88.84
32 2026-08-24 13:36 639231745628278877
1789 ms 40.233.88.84
31 2026-08-24 13:19 639231735407682062
233 ms 40.233.88.84
30 2026-08-24 12:26 639231703815441688
112 ms 40.233.88.84
29 2026-08-24 12:09 639231693747052549
119 ms 40.233.88.84
28 2026-08-24 11:53 639231683712487276
2192 ms 40.233.88.84
27 2026-08-24 11:36 639231673513573868
233 ms 40.233.88.84
26 2026-08-24 10:42 639231641791249939
114 ms 40.233.88.84
25 2026-08-24 10:26 639231631866211033
113 ms 40.233.88.84
24 2026-08-24 10:09 639231621644955316
1512 ms 40.233.88.84
23 2026-08-24 09:52 639231611478799259
232 ms 40.233.88.84
22 2026-08-24 09:00 639231579923718211
3510 ms 40.233.88.84
21 2026-08-24 08:43 639231569810702936
350 ms 40.233.88.84
20 2026-08-24 08:26 639231559762411619
109 ms 40.233.88.84
19 2026-08-24 08:09 639231549663595407
-
18 2026-08-24 07:16 639231518076817246
117 ms 40.233.88.84
17 2026-08-24 07:00 639231508078650885
232 ms 40.233.88.84
16 2026-08-24 06:43 639231498210697093
112 ms 40.233.88.84
15 2026-08-24 06:27 639231488109699360
225 ms 40.233.88.84
14 2026-08-24 05:34 639231456772510692
114 ms 40.233.88.84
13 2026-08-24 05:18 639231447084631185
117 ms 40.233.88.84
12 2026-08-24 05:01 639231437208519473
224 ms 40.233.88.84
11 2026-08-24 04:45 639231427209627490
116 ms 40.233.88.84
10 2026-08-24 03:52 639231395791246644
235 ms 40.233.88.84
9 2026-08-24 03:36 639231386075551458
1711 ms 40.233.88.84
8 2026-08-24 03:20 639231376208713791
231 ms 40.233.88.84
7 2026-08-24 03:03 639231366170589276
234 ms 40.233.88.84
6 2026-08-24 02:11 639231334732159368
1608 ms 40.233.88.84
5 2026-08-24 01:55 639231325035670078
231 ms 40.233.88.84
4 2026-08-24 01:38 639231315132253837
180 ms 40.233.88.84
3 2026-08-24 01:22 639231305014280808
224 ms 40.233.88.84
2 2026-08-24 00:29 639231273779380675
-
1 2026-08-24 00:13 639231264180839154
115 ms 40.233.88.84