DNS response history for n1.multi-cms.com.directideleteddomain.com

n1.multi-cms.com.directideleteddomain.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 2386 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 n1.multi-cms.com.directideleteddomain.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

2386 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.91.197.7

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 n1.multi-cms.com.directideleteddomain.com

Showing DNS history for 2026-08-27 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-27 10:45 639234233269654413
2141 ms 208.91.197.7
33 2026-08-27 10:27 639234222943951923
2371 ms 208.91.197.7
32 2026-08-27 10:10 639234212558002823
4137 ms 208.91.197.7
31 2026-08-27 09:53 639234202117531850
1214 ms 208.91.197.7
30 2026-08-27 09:35 639234191649612722
711 ms 208.91.197.7
29 2026-08-27 09:18 639234181105879568
710 ms 208.91.197.7
28 2026-08-27 09:00 639234170713214496
4144 ms 208.91.197.7
27 2026-08-27 08:43 639234160341037652
2137 ms 208.91.197.7
26 2026-08-27 08:26 639234149799404224
2249 ms 208.91.197.7
25 2026-08-27 08:08 639234139553286469
2365 ms 208.91.197.7
24 2026-08-27 07:15 639234107183588293
3758 ms 208.91.197.7
23 2026-08-27 06:57 639234096905435724
3666 ms 208.91.197.7
22 2026-08-27 06:40 639234086579410775
2614 ms 208.91.197.7
21 2026-08-27 06:23 639234076291157956
2244 ms 208.91.197.7
20 2026-08-27 06:06 639234065981939454
1814 ms 208.91.197.7
19 2026-08-27 05:49 639234055548642997
2356 ms 208.91.197.7
18 2026-08-27 05:31 639234045267979603
705 ms 208.91.197.7
17 2026-08-27 05:14 639234034999717463
4131 ms 208.91.197.7
16 2026-08-27 04:57 639234024739225358
2356 ms 208.91.197.7
15 2026-08-27 04:40 639234014311170162
4144 ms 208.91.197.7
14 2026-08-27 04:22 639234003806017640
2357 ms 208.91.197.7
13 2026-08-27 04:05 639233993356203030
2429 ms 208.91.197.7
12 2026-08-27 03:11 639233961301716608
2139 ms 208.91.197.7
11 2026-08-27 02:54 639233950834200647
1917 ms 208.91.197.7
10 2026-08-27 02:37 639233940431849026
2137 ms 208.91.197.7
9 2026-08-27 02:19 639233930110596398
4135 ms 208.91.197.7
8 2026-08-27 02:02 639233919705434540
4141 ms 208.91.197.7
7 2026-08-27 01:45 639233909452807845
2272 ms 208.91.197.7
6 2026-08-27 01:28 639233899096420820
1222 ms 208.91.197.7
5 2026-08-27 01:11 639233888707824939
2139 ms 208.91.197.7
4 2026-08-27 00:53 639233878461203802
2384 ms 208.91.197.7
3 2026-08-27 00:36 639233868060868209
2139 ms 208.91.197.7
2 2026-08-27 00:19 639233857450922991
1228 ms 208.91.197.7
1 2026-08-27 00:01 639233846871926285
513 ms 208.91.197.7