DNS response history for ns3.cybersecurity.my

ns3.cybersecurity.my 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 37 DNS check records, 37 successful responses, 0 failed responses, and 414 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 ns3.cybersecurity.my.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

414 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.19.129.110

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns3.cybersecurity.my

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
37 2026-08-26 12:12 639233424567558554
333 ms 210.19.129.110
36 2026-08-26 11:55 639233414056832719
350 ms 210.19.129.110
35 2026-08-26 11:37 639233403515141099
328 ms 210.19.129.110
34 2026-08-26 10:42 639233370841350248
330 ms 210.19.129.110
33 2026-08-26 10:25 639233360361507238
329 ms 210.19.129.110
32 2026-08-26 10:08 639233350067824371
165 ms 210.19.129.110
31 2026-08-26 09:51 639233339545274518
170 ms 210.19.129.110
30 2026-08-26 09:33 639233329214918079
334 ms 210.19.129.110
29 2026-08-26 09:16 639233318749762337
173 ms 210.19.129.110
28 2026-08-26 08:58 639233308387917838
348 ms 210.19.129.110
27 2026-08-26 08:41 639233297961740122
330 ms 210.19.129.110
26 2026-08-26 08:24 639233287487159094
343 ms 210.19.129.110
25 2026-08-26 08:06 639233276995531707
344 ms 210.19.129.110
24 2026-08-26 07:49 639233266521568229
509 ms 210.19.129.110
23 2026-08-26 07:31 639233256081047431
339 ms 210.19.129.110
22 2026-08-26 06:37 639233223620132921
179 ms 210.19.129.110
21 2026-08-26 06:20 639233213287814244
162 ms 210.19.129.110
20 2026-08-26 06:03 639233202925983161
342 ms 210.19.129.110
19 2026-08-26 05:45 639233192644780696
330 ms 210.19.129.110
18 2026-08-26 05:28 639233182401183833
336 ms 210.19.129.110
17 2026-08-26 05:11 639233172074181051
172 ms 210.19.129.110
16 2026-08-26 04:54 639233161808421455
337 ms 210.19.129.110
15 2026-08-26 04:37 639233151357344052
328 ms 210.19.129.110
14 2026-08-26 04:19 639233141034116946
2183 ms 210.19.129.110
13 2026-08-26 04:02 639233130828334142
343 ms 210.19.129.110
12 2026-08-26 03:45 639233120373450007
2341 ms 210.19.129.110
11 2026-08-26 03:28 639233110066216193
320 ms 210.19.129.110
10 2026-08-26 02:35 639233078065410564
349 ms 210.19.129.110
9 2026-08-26 02:17 639233067787457832
343 ms 210.19.129.110
8 2026-08-26 02:00 639233057501801162
335 ms 210.19.129.110
7 2026-08-26 01:43 639233047089431703
335 ms 210.19.129.110
6 2026-08-26 01:26 639233036754790688
334 ms 210.19.129.110
5 2026-08-26 01:09 639233026412602472
348 ms 210.19.129.110
4 2026-08-26 00:51 639233016064066127
332 ms 210.19.129.110
3 2026-08-26 00:34 639233005922655772
161 ms 210.19.129.110
2 2026-08-26 00:17 639232995672256907
324 ms 210.19.129.110
1 2026-08-26 00:00 639232985300872416
350 ms 210.19.129.110