DNS response history for ns3.imds.mx

ns3.imds.mx 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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 3181 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.imds.mx.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

3181 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.36.150.43

Most recently resolved hosting IP on selected date

Successful Responses

31

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.imds.mx

Showing DNS history for 2026-08-25 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
31 2026-08-25 10:24 639232492740373468
3984 ms 52.36.150.43
30 2026-08-25 10:07 639232482235303141
3509 ms 52.36.150.43
29 2026-08-25 09:49 639232471861770303
3966 ms 52.36.150.43
28 2026-08-25 09:32 639232461630217327
4314 ms 52.36.150.43
27 2026-08-25 09:15 639232451282965990
2208 ms 52.36.150.43
26 2026-08-25 08:58 639232440814614938
3808 ms 52.36.150.43
25 2026-08-25 08:40 639232430410720425
2300 ms 52.36.150.43
24 2026-08-25 08:23 639232420003096185
2178 ms 52.36.150.43
23 2026-08-25 08:06 639232409467287444
3964 ms 52.36.150.43
22 2026-08-25 07:48 639232399077195997
3532 ms 52.36.150.43
21 2026-08-25 07:31 639232388731528337
3702 ms 52.36.150.43
20 2026-08-25 07:14 639232378288598612
3532 ms 52.36.150.43
19 2026-08-25 06:19 639232346196373643
4158 ms 52.36.150.43
18 2026-08-25 06:03 639232336112370741
2178 ms 52.36.150.43
17 2026-08-25 05:46 639232326146508970
3512 ms 52.36.150.43
16 2026-08-25 05:29 639232316189381720
2166 ms 52.36.150.43
15 2026-08-25 05:13 639232306217998913
2313 ms 52.36.150.43
14 2026-08-25 04:56 639232296255744174
3869 ms 52.36.150.43
13 2026-08-25 04:39 639232286095760789
3980 ms 52.36.150.43
12 2026-08-25 04:23 639232276086186273
2173 ms 52.36.150.43
11 2026-08-25 04:06 639232265900986425
3878 ms 52.36.150.43
10 2026-08-25 03:49 639232255723518075
2290 ms 52.36.150.43
9 2026-08-25 03:32 639232245484452890
3510 ms 52.36.150.43
8 2026-08-25 03:15 639232235157175331
1846 ms 52.36.150.43
7 2026-08-25 02:21 639232203197189095
3836 ms 52.36.150.43
6 2026-08-25 02:04 639232192844564298
3676 ms 52.36.150.43
5 2026-08-25 01:47 639232182496008942
2361 ms 52.36.150.43
4 2026-08-25 01:30 639232172197053132
3833 ms 52.36.150.43
3 2026-08-25 00:36 639232140250307418
2177 ms 52.36.150.43
2 2026-08-25 00:20 639232129927860324
3669 ms 52.36.150.43
1 2026-08-25 00:02 639232119551972438
2200 ms 52.36.150.43