DNS response history for ns1.aimdom.com

ns1.aimdom.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-26. For this date, NameServerHistory found 29 DNS check records, 28 successful responses, 1 failed responses, and 109 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.aimdom.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

109 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

174.143.244.86

Most recently resolved hosting IP on selected date

Successful Responses

28

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

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
29 2026-08-26 09:22 639233329214918079
53 ms 174.143.244.86
28 2026-08-26 09:04 639233318749762337
48 ms 174.143.244.86
27 2026-08-26 08:47 639233308387917838
23 ms 174.143.244.86
26 2026-08-26 08:30 639233297961740122
34 ms 174.143.244.86
25 2026-08-26 08:12 639233287487159094
36 ms 174.143.244.86
24 2026-08-26 07:55 639233276995531707
36 ms 174.143.244.86
23 2026-08-26 07:37 639233266521568229
57 ms 174.143.244.86
22 2026-08-26 07:20 639233256081047431
42 ms 174.143.244.86
21 2026-08-26 06:26 639233223620132921
11 ms 174.143.244.86
20 2026-08-26 06:08 639233213287814244
91 ms 174.143.244.86
19 2026-08-26 05:51 639233202925983161
18 ms 174.143.244.86
18 2026-08-26 05:34 639233192644780696
42 ms 174.143.244.86
17 2026-08-26 05:17 639233182401183833
27 ms 174.143.244.86
16 2026-08-26 05:00 639233172074181051
77 ms 174.143.244.86
15 2026-08-26 04:43 639233161808421455
45 ms 174.143.244.86
14 2026-08-26 04:25 639233151357344052
17 ms 174.143.244.86
13 2026-08-26 04:08 639233141034116946
35 ms 174.143.244.86
12 2026-08-26 03:51 639233130828334142
9 ms 174.143.244.86
11 2026-08-26 03:34 639233120373450007
48 ms 174.143.244.86
10 2026-08-26 03:16 639233110066216193
13 ms 174.143.244.86
9 2026-08-26 02:23 639233078065410564
18 ms 174.143.244.86
8 2026-08-26 02:06 639233067787457832
-
7 2026-08-26 01:49 639233057501801162
106 ms 174.143.244.86
6 2026-08-26 01:31 639233047089431703
2024 ms 174.143.244.86
5 2026-08-26 01:14 639233036754790688
20 ms 174.143.244.86
4 2026-08-26 00:57 639233026412602472
57 ms 174.143.244.86
3 2026-08-26 00:40 639233016064066127
37 ms 174.143.244.86
2 2026-08-26 00:23 639233005922655772
11 ms 174.143.244.86
1 2026-08-26 00:06 639232995672256907
23 ms 174.143.244.86