DNS response history for ns3.inseecomm.com

ns3.inseecomm.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 432 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.inseecomm.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

432 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

116.126.143.225

Most recently resolved hosting IP on selected date

Successful Responses

30

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

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
30 2026-08-25 10:21 639232492740373468
591 ms 116.126.143.225
29 2026-08-25 10:04 639232482235303141
580 ms 116.126.143.225
28 2026-08-25 09:47 639232471861770303
583 ms 116.126.143.225
27 2026-08-25 09:29 639232461630217327
286 ms 116.126.143.225
26 2026-08-25 09:12 639232451282965990
295 ms 116.126.143.225
25 2026-08-25 08:55 639232440814614938
293 ms 116.126.143.225
24 2026-08-25 08:38 639232430410720425
284 ms 116.126.143.225
23 2026-08-25 08:20 639232420003096185
309 ms 116.126.143.225
22 2026-08-25 08:03 639232409467287444
587 ms 116.126.143.225
21 2026-08-25 07:45 639232399077195997
283 ms 116.126.143.225
20 2026-08-25 07:28 639232388731528337
568 ms 116.126.143.225
19 2026-08-25 07:11 639232378288598612
609 ms 116.126.143.225
18 2026-08-25 06:17 639232346196373643
298 ms 116.126.143.225
17 2026-08-25 06:00 639232336112370741
293 ms 116.126.143.225
16 2026-08-25 05:43 639232326146508970
288 ms 116.126.143.225
15 2026-08-25 05:27 639232316189381720
571 ms 116.126.143.225
14 2026-08-25 05:10 639232306217998913
599 ms 116.126.143.225
13 2026-08-25 04:54 639232296255744174
308 ms 116.126.143.225
12 2026-08-25 04:37 639232286095760789
590 ms 116.126.143.225
11 2026-08-25 04:20 639232276086186273
305 ms 116.126.143.225
10 2026-08-25 04:03 639232265900986425
600 ms 116.126.143.225
9 2026-08-25 03:46 639232255723518075
304 ms 116.126.143.225
8 2026-08-25 03:29 639232245484452890
285 ms 116.126.143.225
7 2026-08-25 03:12 639232235157175331
580 ms 116.126.143.225
6 2026-08-25 02:19 639232203197189095
302 ms 116.126.143.225
5 2026-08-25 02:02 639232192844564298
295 ms 116.126.143.225
4 2026-08-25 01:44 639232182496008942
588 ms 116.126.143.225
3 2026-08-25 01:27 639232172197053132
600 ms 116.126.143.225
2 2026-08-25 00:34 639232140250307418
587 ms 116.126.143.225
1 2026-08-25 00:17 639232129927860324
294 ms 116.126.143.225