DNS response history for ns1.sendsmspro.com

ns1.sendsmspro.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-24. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 393 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.sendsmspro.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

393 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.58.6.202

Most recently resolved hosting IP on selected date

Successful Responses

38

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

Showing DNS history for 2026-08-24 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-24 15:48 639231828211839931
240 ms 69.58.6.202
37 2026-08-24 15:31 639231818080917481
158 ms 69.58.6.202
36 2026-08-24 15:14 639231807961539652
235 ms 69.58.6.202
35 2026-08-24 14:57 639231797631669865
232 ms 69.58.6.202
34 2026-08-24 14:04 639231765923559455
118 ms 69.58.6.202
33 2026-08-24 13:47 639231755868832964
241 ms 69.58.6.202
32 2026-08-24 13:30 639231745628278877
16 ms 69.58.6.202
31 2026-08-24 13:13 639231735407682062
249 ms 69.58.6.202
30 2026-08-24 12:20 639231703815441688
241 ms 69.58.6.202
29 2026-08-24 12:04 639231693747052549
267 ms 69.58.6.202
28 2026-08-24 11:47 639231683712487276
231 ms 69.58.6.202
27 2026-08-24 11:30 639231673513573868
148 ms 69.58.6.202
26 2026-08-24 10:37 639231641791249939
248 ms 69.58.6.202
25 2026-08-24 10:21 639231631866211033
157 ms 69.58.6.202
24 2026-08-24 10:04 639231621644955316
264 ms 69.58.6.202
23 2026-08-24 09:47 639231611478799259
242 ms 69.58.6.202
22 2026-08-24 08:54 639231579923718211
254 ms 69.58.6.202
21 2026-08-24 08:37 639231569810702936
240 ms 69.58.6.202
20 2026-08-24 08:20 639231559762411619
247 ms 69.58.6.202
19 2026-08-24 08:04 639231549663595407
162 ms 69.58.6.202
18 2026-08-24 07:11 639231518076817246
285 ms 69.58.6.202
17 2026-08-24 06:55 639231508078650885
236 ms 69.58.6.202
16 2026-08-24 06:38 639231498210697093
2011 ms 69.58.6.202
15 2026-08-24 06:21 639231488109699360
251 ms 69.58.6.202
14 2026-08-24 05:29 639231456772510692
243 ms 69.58.6.202
13 2026-08-24 05:13 639231447084631185
247 ms 69.58.6.202
12 2026-08-24 04:56 639231437208519473
2121 ms 69.58.6.202
11 2026-08-24 04:40 639231427209627490
240 ms 69.58.6.202
10 2026-08-24 03:47 639231395791246644
12 ms 69.58.6.202
9 2026-08-24 03:31 639231386075551458
3 ms 69.58.6.202
8 2026-08-24 03:15 639231376208713791
2 ms 69.58.6.202
7 2026-08-24 02:58 639231366170589276
6 ms 69.58.6.202
6 2026-08-24 02:06 639231334732159368
138 ms 69.58.6.202
5 2026-08-24 01:49 639231325035670078
186 ms 69.58.6.202
4 2026-08-24 01:33 639231315132253837
266 ms 69.58.6.202
3 2026-08-24 01:16 639231305014280808
2231 ms 69.58.6.202
2 2026-08-24 00:24 639231273779380675
2008 ms 69.58.6.202
1 2026-08-24 00:08 639231264180839154
262 ms 69.58.6.202