DNS response history for ns1.brandsman.com

ns1.brandsman.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 34 DNS check records, 34 successful responses, 0 failed responses, and 362 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.brandsman.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

362 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.16.220.218

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns1.brandsman.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
34 2026-08-25 12:03 639232556111768563
222 ms 69.16.220.218
33 2026-08-25 11:46 639232545839529039
223 ms 69.16.220.218
32 2026-08-25 11:28 639232535349285207
227 ms 69.16.220.218
31 2026-08-25 11:11 639232524938080723
239 ms 69.16.220.218
30 2026-08-25 10:17 639232492740373468
2166 ms 69.16.220.218
29 2026-08-25 10:00 639232482235303141
5 ms 69.16.220.218
28 2026-08-25 09:42 639232471861770303
219 ms 69.16.220.218
27 2026-08-25 09:25 639232461630217327
227 ms 69.16.220.218
26 2026-08-25 09:08 639232451282965990
118 ms 69.16.220.218
25 2026-08-25 08:51 639232440814614938
237 ms 69.16.220.218
24 2026-08-25 08:33 639232430410720425
228 ms 69.16.220.218
23 2026-08-25 08:16 639232420003096185
236 ms 69.16.220.218
22 2026-08-25 07:59 639232409467287444
228 ms 69.16.220.218
21 2026-08-25 07:41 639232399077195997
228 ms 69.16.220.218
20 2026-08-25 07:24 639232388731528337
130 ms 69.16.220.218
19 2026-08-25 07:06 639232378288598612
233 ms 69.16.220.218
18 2026-08-25 06:13 639232346196373643
153 ms 69.16.220.218
17 2026-08-25 05:56 639232336112370741
240 ms 69.16.220.218
16 2026-08-25 05:39 639232326146508970
227 ms 69.16.220.218
15 2026-08-25 05:23 639232316189381720
128 ms 69.16.220.218
14 2026-08-25 05:06 639232306217998913
3 ms 69.16.220.218
13 2026-08-25 04:50 639232296255744174
224 ms 69.16.220.218
12 2026-08-25 04:33 639232286095760789
233 ms 69.16.220.218
11 2026-08-25 04:16 639232276086186273
4118 ms 69.16.220.218
10 2026-08-25 03:59 639232265900986425
14 ms 69.16.220.218
9 2026-08-25 03:42 639232255723518075
223 ms 69.16.220.218
8 2026-08-25 03:25 639232245484452890
228 ms 69.16.220.218
7 2026-08-25 03:08 639232235157175331
226 ms 69.16.220.218
6 2026-08-25 02:15 639232203197189095
114 ms 69.16.220.218
5 2026-08-25 01:57 639232192844564298
224 ms 69.16.220.218
4 2026-08-25 01:40 639232182496008942
223 ms 69.16.220.218
3 2026-08-25 01:23 639232172197053132
222 ms 69.16.220.218
2 2026-08-25 00:30 639232140250307418
123 ms 69.16.220.218
1 2026-08-25 00:13 639232129927860324
222 ms 69.16.220.218