DNS response history for ns2.harbingermarketing.com

ns2.harbingermarketing.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-26. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 308 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 ns2.harbingermarketing.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

308 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.225.152.101

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns2.harbingermarketing.com

Showing DNS history for 2026-08-26 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
28 2026-08-26 09:13 639233318749762337
115 ms 67.225.152.101
27 2026-08-26 08:56 639233308387917838
231 ms 67.225.152.101
26 2026-08-26 08:38 639233297961740122
2132 ms 67.225.152.101
25 2026-08-26 08:21 639233287487159094
118 ms 67.225.152.101
24 2026-08-26 08:03 639233276995531707
222 ms 67.225.152.101
23 2026-08-26 07:46 639233266521568229
134 ms 67.225.152.101
22 2026-08-26 07:28 639233256081047431
128 ms 67.225.152.101
21 2026-08-26 06:34 639233223620132921
240 ms 67.225.152.101
20 2026-08-26 06:17 639233213287814244
227 ms 67.225.152.101
19 2026-08-26 06:00 639233202925983161
226 ms 67.225.152.101
18 2026-08-26 05:42 639233192644780696
127 ms 67.225.152.101
17 2026-08-26 05:25 639233182401183833
122 ms 67.225.152.101
16 2026-08-26 05:08 639233172074181051
136 ms 67.225.152.101
15 2026-08-26 04:51 639233161808421455
115 ms 67.225.152.101
14 2026-08-26 04:34 639233151357344052
233 ms 67.225.152.101
13 2026-08-26 04:16 639233141034116946
131 ms 67.225.152.101
12 2026-08-26 03:59 639233130828334142
133 ms 67.225.152.101
11 2026-08-26 03:42 639233120373450007
219 ms 67.225.152.101
10 2026-08-26 03:25 639233110066216193
227 ms 67.225.152.101
9 2026-08-26 02:32 639233078065410564
2170 ms 67.225.152.101
8 2026-08-26 02:14 639233067787457832
124 ms 67.225.152.101
7 2026-08-26 01:57 639233057501801162
228 ms 67.225.152.101
6 2026-08-26 01:40 639233047089431703
126 ms 67.225.152.101
5 2026-08-26 01:23 639233036754790688
219 ms 67.225.152.101
4 2026-08-26 01:06 639233026412602472
115 ms 67.225.152.101
3 2026-08-26 00:48 639233016064066127
110 ms 67.225.152.101
2 2026-08-26 00:31 639233005922655772
156 ms 67.225.152.101
1 2026-08-26 00:14 639232995672256907
167 ms 67.225.152.101