DNS response history for ns1.cdkm.com

ns1.cdkm.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 299 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.cdkm.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

299 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.202.185.193

Most recently resolved hosting IP on selected date

Successful Responses

30

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

Showing DNS history for 2026-08-26 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
30 2026-08-26 09:50 639233339545274518
344 ms 64.202.185.193
29 2026-08-26 09:32 639233329214918079
382 ms 64.202.185.193
28 2026-08-26 09:15 639233318749762337
353 ms 64.202.185.193
27 2026-08-26 08:58 639233308387917838
358 ms 64.202.185.193
26 2026-08-26 08:40 639233297961740122
394 ms 64.202.185.193
25 2026-08-26 08:23 639233287487159094
340 ms 64.202.185.193
24 2026-08-26 08:05 639233276995531707
333 ms 64.202.185.193
23 2026-08-26 07:48 639233266521568229
162 ms 64.202.185.193
22 2026-08-26 07:30 639233256081047431
343 ms 64.202.185.193
21 2026-08-26 06:36 639233223620132921
351 ms 64.202.185.193
20 2026-08-26 06:19 639233213287814244
9 ms 64.202.185.193
19 2026-08-26 06:02 639233202925983161
199 ms 64.202.185.193
18 2026-08-26 05:45 639233192644780696
17 ms 64.202.185.193
17 2026-08-26 05:27 639233182401183833
376 ms 64.202.185.193
16 2026-08-26 05:10 639233172074181051
346 ms 64.202.185.193
15 2026-08-26 04:53 639233161808421455
370 ms 64.202.185.193
14 2026-08-26 04:36 639233151357344052
353 ms 64.202.185.193
13 2026-08-26 04:19 639233141034116946
344 ms 64.202.185.193
12 2026-08-26 04:02 639233130828334142
332 ms 64.202.185.193
11 2026-08-26 03:44 639233120373450007
337 ms 64.202.185.193
10 2026-08-26 03:27 639233110066216193
354 ms 64.202.185.193
9 2026-08-26 02:34 639233078065410564
334 ms 64.202.185.193
8 2026-08-26 02:17 639233067787457832
168 ms 64.202.185.193
7 2026-08-26 01:59 639233057501801162
175 ms 64.202.185.193
6 2026-08-26 01:42 639233047089431703
344 ms 64.202.185.193
5 2026-08-26 01:25 639233036754790688
334 ms 64.202.185.193
4 2026-08-26 01:08 639233026412602472
169 ms 64.202.185.193
3 2026-08-26 00:50 639233016064066127
343 ms 64.202.185.193
2 2026-08-26 00:33 639233005922655772
341 ms 64.202.185.193
1 2026-08-26 00:16 639232995672256907
352 ms 64.202.185.193