DNS response history for ns2.cddomain.com

ns2.cddomain.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 476 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.cddomain.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

476 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.50.126.55

Most recently resolved hosting IP on selected date

Successful Responses

36

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

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
36 2026-08-24 15:17 639231807961539652
310 ms 74.50.126.55
35 2026-08-24 15:00 639231797631669865
303 ms 74.50.126.55
34 2026-08-24 14:07 639231765923559455
308 ms 74.50.126.55
33 2026-08-24 13:50 639231755868832964
320 ms 74.50.126.55
32 2026-08-24 13:33 639231745628278877
160 ms 74.50.126.55
31 2026-08-24 13:16 639231735407682062
196 ms 74.50.126.55
30 2026-08-24 12:23 639231703815441688
196 ms 74.50.126.55
29 2026-08-24 12:07 639231693747052549
2165 ms 74.50.126.55
28 2026-08-24 11:50 639231683712487276
313 ms 74.50.126.55
27 2026-08-24 11:33 639231673513573868
302 ms 74.50.126.55
26 2026-08-24 10:40 639231641791249939
301 ms 74.50.126.55
25 2026-08-24 10:23 639231631866211033
300 ms 74.50.126.55
24 2026-08-24 10:07 639231621644955316
303 ms 74.50.126.55
23 2026-08-24 09:50 639231611478799259
302 ms 74.50.126.55
22 2026-08-24 08:57 639231579923718211
323 ms 74.50.126.55
21 2026-08-24 08:40 639231569810702936
295 ms 74.50.126.55
20 2026-08-24 08:23 639231559762411619
2200 ms 74.50.126.55
19 2026-08-24 08:06 639231549663595407
161 ms 74.50.126.55
18 2026-08-24 07:14 639231518076817246
310 ms 74.50.126.55
17 2026-08-24 06:57 639231508078650885
187 ms 74.50.126.55
16 2026-08-24 06:41 639231498210697093
256 ms 74.50.126.55
15 2026-08-24 06:24 639231488109699360
305 ms 74.50.126.55
14 2026-08-24 05:32 639231456772510692
3 ms 74.50.126.55
13 2026-08-24 05:15 639231447084631185
302 ms 74.50.126.55
12 2026-08-24 04:59 639231437208519473
298 ms 74.50.126.55
11 2026-08-24 04:42 639231427209627490
290 ms 74.50.126.55
10 2026-08-24 03:50 639231395791246644
296 ms 74.50.126.55
9 2026-08-24 03:34 639231386075551458
2254 ms 74.50.126.55
8 2026-08-24 03:17 639231376208713791
298 ms 74.50.126.55
7 2026-08-24 03:01 639231366170589276
3 ms 74.50.126.55
6 2026-08-24 02:08 639231334732159368
304 ms 74.50.126.55
5 2026-08-24 01:52 639231325035670078
303 ms 74.50.126.55
4 2026-08-24 01:36 639231315132253837
301 ms 74.50.126.55
3 2026-08-24 01:19 639231305014280808
320 ms 74.50.126.55
2 2026-08-24 00:26 639231273779380675
2178 ms 74.50.126.55
1 2026-08-24 00:11 639231264180839154
160 ms 74.50.126.55