DNS response history for ns1.onlinemarketingtoday.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

204 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.59.185.119

Most recently resolved hosting IP on selected date

Successful Responses

33

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.onlinemarketingtoday.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
33 2026-08-25 11:46 639232545839529039
130 ms 209.59.185.119
32 2026-08-25 11:28 639232535349285207
222 ms 209.59.185.119
31 2026-08-25 11:11 639232524938080723
231 ms 209.59.185.119
30 2026-08-25 10:17 639232492740373468
223 ms 209.59.185.119
29 2026-08-25 10:00 639232482235303141
217 ms 209.59.185.119
28 2026-08-25 09:42 639232471861770303
155 ms 209.59.185.119
27 2026-08-25 09:25 639232461630217327
227 ms 209.59.185.119
26 2026-08-25 09:08 639232451282965990
229 ms 209.59.185.119
25 2026-08-25 08:51 639232440814614938
136 ms 209.59.185.119
24 2026-08-25 08:33 639232430410720425
221 ms 209.59.185.119
23 2026-08-25 08:16 639232420003096185
233 ms 209.59.185.119
22 2026-08-25 07:59 639232409467287444
246 ms 209.59.185.119
21 2026-08-25 07:41 639232399077195997
233 ms 209.59.185.119
20 2026-08-25 07:24 639232388731528337
223 ms 209.59.185.119
19 2026-08-25 07:06 639232378288598612
220 ms 209.59.185.119
18 2026-08-25 06:13 639232346196373643
228 ms 209.59.185.119
17 2026-08-25 05:56 639232336112370741
123 ms 209.59.185.119
16 2026-08-25 05:39 639232326146508970
247 ms 209.59.185.119
15 2026-08-25 05:23 639232316189381720
229 ms 209.59.185.119
14 2026-08-25 05:06 639232306217998913
221 ms 209.59.185.119
13 2026-08-25 04:50 639232296255744174
231 ms 209.59.185.119
12 2026-08-25 04:33 639232286095760789
235 ms 209.59.185.119
11 2026-08-25 04:16 639232276086186273
223 ms 209.59.185.119
10 2026-08-25 03:59 639232265900986425
226 ms 209.59.185.119
9 2026-08-25 03:42 639232255723518075
234 ms 209.59.185.119
8 2026-08-25 03:25 639232245484452890
229 ms 209.59.185.119
7 2026-08-25 03:08 639232235157175331
134 ms 209.59.185.119
6 2026-08-25 02:15 639232203197189095
221 ms 209.59.185.119
5 2026-08-25 01:58 639232192844564298
130 ms 209.59.185.119
4 2026-08-25 01:40 639232182496008942
112 ms 209.59.185.119
3 2026-08-25 01:23 639232172197053132
122 ms 209.59.185.119
2 2026-08-25 00:30 639232140250307418
225 ms 209.59.185.119
1 2026-08-25 00:13 639232129927860324
224 ms 209.59.185.119