DNS response history for ns1.ironlock.top

ns1.ironlock.top 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 38 DNS check records, 37 successful responses, 1 failed responses, and 294 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.ironlock.top.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

294 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.32.7.75

Most recently resolved hosting IP on selected date

Successful Responses

37

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.ironlock.top

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
38 2026-08-26 12:33 639233434974187439
286 ms 37.32.7.75
37 2026-08-26 12:15 639233424567558554
262 ms 37.32.7.75
36 2026-08-26 11:58 639233414056832719
274 ms 37.32.7.75
35 2026-08-26 11:41 639233403515141099
252 ms 37.32.7.75
34 2026-08-26 10:46 639233370841350248
252 ms 31.184.171.128
33 2026-08-26 10:29 639233360361507238
109 ms 31.184.171.128
32 2026-08-26 10:11 639233350067824371
2 ms 31.184.171.128
31 2026-08-26 09:54 639233339545274518
247 ms 31.184.171.128
30 2026-08-26 09:36 639233329214918079
243 ms 31.184.171.128
29 2026-08-26 09:19 639233318749762337
232 ms 31.184.171.128
28 2026-08-26 09:02 639233308387917838
2032 ms 31.184.171.128
27 2026-08-26 08:45 639233297961740122
2008 ms 31.184.171.128
26 2026-08-26 08:27 639233287487159094
-
25 2026-08-26 08:10 639233276995531707
35 ms 31.184.171.128
24 2026-08-26 07:52 639233266521568229
238 ms 31.184.171.128
23 2026-08-26 07:35 639233256081047431
201 ms 31.184.171.128
22 2026-08-26 06:41 639233223620132921
126 ms 31.184.171.128
21 2026-08-26 06:23 639233213287814244
126 ms 31.184.171.128
20 2026-08-26 06:06 639233202925983161
176 ms 31.184.171.128
19 2026-08-26 05:49 639233192644780696
156 ms 31.184.171.128
18 2026-08-26 05:32 639233182401183833
219 ms 31.184.171.128
17 2026-08-26 05:15 639233172074181051
257 ms 31.184.171.128
16 2026-08-26 04:57 639233161808421455
243 ms 31.184.171.128
15 2026-08-26 04:40 639233151357344052
106 ms 31.184.171.128
14 2026-08-26 04:23 639233141034116946
112 ms 31.184.171.128
13 2026-08-26 04:06 639233130828334142
3 ms 31.184.171.128
12 2026-08-26 03:49 639233120373450007
129 ms 31.184.171.128
11 2026-08-26 03:31 639233110066216193
259 ms 31.184.171.128
10 2026-08-26 02:38 639233078065410564
230 ms 31.184.171.128
9 2026-08-26 02:21 639233067787457832
233 ms 31.184.171.128
8 2026-08-26 02:04 639233057501801162
245 ms 31.184.171.128
7 2026-08-26 01:46 639233047089431703
252 ms 31.184.171.128
6 2026-08-26 01:29 639233036754790688
218 ms 31.184.171.128
5 2026-08-26 01:12 639233026412602472
246 ms 31.184.171.128
4 2026-08-26 00:55 639233016064066127
127 ms 31.184.171.128
3 2026-08-26 00:37 639233005922655772
219 ms 31.184.171.128
2 2026-08-26 00:20 639232995672256907
258 ms 31.184.171.128
1 2026-08-26 00:03 639232985300872416
254 ms 31.184.171.128