DNS response history for ns1.seocommandos.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

481 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

148.72.152.180

Most recently resolved hosting IP on selected date

Successful Responses

32

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.seocommandos.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
32 2026-08-24 13:30 639231745628278877
236 ms 148.72.152.180
31 2026-08-24 13:13 639231735407682062
237 ms 148.72.152.180
30 2026-08-24 12:20 639231703815441688
230 ms 148.72.152.180
29 2026-08-24 12:03 639231693747052549
37 ms 148.72.152.180
28 2026-08-24 11:47 639231683712487276
17 ms 148.72.152.180
27 2026-08-24 11:30 639231673513573868
187 ms 148.72.152.180
26 2026-08-24 10:37 639231641791249939
233 ms 148.72.152.180
25 2026-08-24 10:20 639231631866211033
240 ms 148.72.152.180
24 2026-08-24 10:03 639231621644955316
233 ms 148.72.152.180
23 2026-08-24 09:46 639231611478799259
172 ms 148.72.152.180
22 2026-08-24 08:54 639231579923718211
2125 ms 148.72.152.180
21 2026-08-24 08:37 639231569810702936
243 ms 148.72.152.180
20 2026-08-24 08:20 639231559762411619
118 ms 148.72.152.180
19 2026-08-24 08:03 639231549663595407
138 ms 148.72.152.180
18 2026-08-24 07:11 639231518076817246
240 ms 148.72.152.180
17 2026-08-24 06:54 639231508078650885
260 ms 148.72.152.180
16 2026-08-24 06:38 639231498210697093
33 ms 148.72.152.180
15 2026-08-24 06:21 639231488109699360
2136 ms 148.72.152.180
14 2026-08-24 05:29 639231456772510692
126 ms 148.72.152.180
13 2026-08-24 05:13 639231447084631185
9 ms 148.72.152.180
12 2026-08-24 04:56 639231437208519473
232 ms 148.72.152.180
11 2026-08-24 04:39 639231427209627490
141 ms 148.72.152.180
10 2026-08-24 03:47 639231395791246644
233 ms 148.72.152.180
9 2026-08-24 03:31 639231386075551458
139 ms 148.72.152.180
8 2026-08-24 03:14 639231376208713791
3 ms 148.72.152.180
7 2026-08-24 02:58 639231366170589276
257 ms 148.72.152.180
6 2026-08-24 02:05 639231334732159368
231 ms 148.72.152.180
5 2026-08-24 01:49 639231325035670078
232 ms 148.72.152.180
4 2026-08-24 01:32 639231315132253837
4161 ms 148.72.152.180
3 2026-08-24 01:16 639231305014280808
2131 ms 148.72.152.180
2 2026-08-24 00:24 639231273779380675
238 ms 148.72.152.180
1 2026-08-24 00:08 639231264180839154
130 ms 148.72.152.180