DNS response history for ns2.hdsexmov.net

ns2.hdsexmov.net 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 35 DNS check records, 35 successful responses, 0 failed responses, and 500 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.hdsexmov.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

500 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.214.250.125

Most recently resolved hosting IP on selected date

Successful Responses

35

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.hdsexmov.net

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
35 2026-08-24 15:00 639231797631669865
359 ms 173.214.250.125
34 2026-08-24 14:07 639231765923559455
339 ms 173.214.250.125
33 2026-08-24 13:50 639231755868832964
2009 ms 173.214.250.125
32 2026-08-24 13:33 639231745628278877
358 ms 173.214.250.125
31 2026-08-24 13:16 639231735407682062
189 ms 173.214.250.125
30 2026-08-24 12:23 639231703815441688
2151 ms 173.214.250.125
29 2026-08-24 12:07 639231693747052549
2149 ms 173.214.250.125
28 2026-08-24 11:50 639231683712487276
183 ms 173.214.250.125
27 2026-08-24 11:33 639231673513573868
200 ms 173.214.250.125
26 2026-08-24 10:40 639231641791249939
339 ms 173.214.250.125
25 2026-08-24 10:23 639231631866211033
172 ms 173.214.250.125
24 2026-08-24 10:07 639231621644955316
219 ms 173.214.250.125
23 2026-08-24 09:50 639231611478799259
341 ms 173.214.250.125
22 2026-08-24 08:57 639231579923718211
8 ms 173.214.250.125
21 2026-08-24 08:40 639231569810702936
324 ms 173.214.250.125
20 2026-08-24 08:23 639231559762411619
2194 ms 173.214.250.125
19 2026-08-24 08:06 639231549663595407
370 ms 173.214.250.125
18 2026-08-24 07:14 639231518076817246
349 ms 173.214.250.125
17 2026-08-24 06:57 639231508078650885
197 ms 173.214.250.125
16 2026-08-24 06:41 639231498210697093
233 ms 173.214.250.125
15 2026-08-24 06:24 639231488109699360
358 ms 173.214.250.125
14 2026-08-24 05:32 639231456772510692
228 ms 173.214.250.125
13 2026-08-24 05:15 639231447084631185
2 ms 173.214.250.125
12 2026-08-24 04:59 639231437208519473
2167 ms 173.214.250.125
11 2026-08-24 04:42 639231427209627490
163 ms 173.214.250.125
10 2026-08-24 03:50 639231395791246644
187 ms 173.214.250.125
9 2026-08-24 03:34 639231386075551458
12 ms 173.214.250.125
8 2026-08-24 03:17 639231376208713791
359 ms 173.214.250.125
7 2026-08-24 03:01 639231366170589276
202 ms 173.214.250.125
6 2026-08-24 02:08 639231334732159368
160 ms 173.214.250.125
5 2026-08-24 01:52 639231325035670078
322 ms 173.214.250.125
4 2026-08-24 01:36 639231315132253837
194 ms 173.214.250.125
3 2026-08-24 01:19 639231305014280808
257 ms 173.214.250.125
2 2026-08-24 00:27 639231273779380675
197 ms 173.214.250.125
1 2026-08-24 00:11 639231264180839154
7 ms 173.214.250.125