DNS response history for ns2.xmlasecure.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

177 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.28.99.225

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 ns2.xmlasecure.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
33 2026-08-24 13:50 639231755868832964
303 ms 50.28.99.225
32 2026-08-24 13:33 639231745628278877
159 ms 50.28.99.225
31 2026-08-24 13:16 639231735407682062
161 ms 50.28.99.225
30 2026-08-24 12:23 639231703815441688
7 ms 50.28.99.225
29 2026-08-24 12:07 639231693747052549
297 ms 50.28.99.225
28 2026-08-24 11:50 639231683712487276
306 ms 50.28.99.225
27 2026-08-24 11:33 639231673513573868
312 ms 50.28.99.225
26 2026-08-24 10:40 639231641791249939
307 ms 50.28.99.225
25 2026-08-24 10:23 639231631866211033
190 ms 50.28.99.225
24 2026-08-24 10:07 639231621644955316
301 ms 50.28.99.225
23 2026-08-24 09:50 639231611478799259
310 ms 50.28.99.225
22 2026-08-24 08:57 639231579923718211
4 ms 50.28.99.225
21 2026-08-24 08:40 639231569810702936
293 ms 50.28.99.225
20 2026-08-24 08:23 639231559762411619
153 ms 50.28.99.225
19 2026-08-24 08:06 639231549663595407
276 ms 50.28.99.225
18 2026-08-24 07:14 639231518076817246
318 ms 50.28.99.225
17 2026-08-24 06:57 639231508078650885
306 ms 50.28.99.225
16 2026-08-24 06:41 639231498210697093
261 ms 50.28.99.225
15 2026-08-24 06:24 639231488109699360
155 ms 50.28.99.225
14 2026-08-24 05:32 639231456772510692
5 ms 50.28.99.225
13 2026-08-24 05:15 639231447084631185
4 ms 50.28.99.225
12 2026-08-24 04:59 639231437208519473
301 ms 50.28.99.225
11 2026-08-24 04:42 639231427209627490
12 ms 50.28.99.225
10 2026-08-24 03:50 639231395791246644
163 ms 50.28.99.225
9 2026-08-24 03:34 639231386075551458
295 ms 50.28.99.225
8 2026-08-24 03:17 639231376208713791
7 ms 50.28.99.225
7 2026-08-24 03:01 639231366170589276
2 ms 50.28.99.225
6 2026-08-24 02:08 639231334732159368
7 ms 50.28.99.225
5 2026-08-24 01:52 639231325035670078
303 ms 50.28.99.225
4 2026-08-24 01:36 639231315132253837
3 ms 50.28.99.225
3 2026-08-24 01:19 639231305014280808
3 ms 50.28.99.225
2 2026-08-24 00:26 639231273779380675
5 ms 50.28.99.225
1 2026-08-24 00:11 639231264180839154
302 ms 50.28.99.225