DNS response history for no2.nameserver.com

no2.nameserver.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 37 DNS check records, 37 successful responses, 0 failed responses, and 383 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 no2.nameserver.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

383 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.40.34.41

Most recently resolved hosting IP on selected date

Successful Responses

37

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 no2.nameserver.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
37 2026-08-27 12:26 639234296664302575
127 ms 216.40.34.41
36 2026-08-27 12:09 639234286253196126
114 ms 216.40.34.41
35 2026-08-27 11:15 639234253963286387
120 ms 216.40.34.41
34 2026-08-27 10:58 639234243654907465
116 ms 216.40.34.41
33 2026-08-27 10:41 639234233269654413
399 ms 216.40.34.41
32 2026-08-27 10:24 639234222943951923
115 ms 216.40.34.41
31 2026-08-27 10:06 639234212558002823
108 ms 216.40.34.41
30 2026-08-27 09:49 639234202117531850
112 ms 216.40.34.41
29 2026-08-27 09:32 639234191649612722
4118 ms 216.40.34.41
28 2026-08-27 09:14 639234181105879568
125 ms 216.40.34.41
27 2026-08-27 08:56 639234170713214496
119 ms 216.40.34.41
26 2026-08-27 08:39 639234160341037652
123 ms 216.40.34.41
25 2026-08-27 08:22 639234149799404224
114 ms 216.40.34.41
24 2026-08-27 08:04 639234139553286469
113 ms 216.40.34.41
23 2026-08-27 07:11 639234107183588293
112 ms 216.40.34.41
22 2026-08-27 06:53 639234096905435724
112 ms 216.40.34.41
21 2026-08-27 06:36 639234086579410775
129 ms 216.40.34.41
20 2026-08-27 06:19 639234076291157956
111 ms 216.40.34.41
19 2026-08-27 06:02 639234065981939454
3613 ms 216.40.34.41
18 2026-08-27 05:45 639234055548642997
112 ms 216.40.34.41
17 2026-08-27 05:27 639234045267979603
218 ms 216.40.34.41
16 2026-08-27 05:10 639234034999717463
135 ms 216.40.34.41
15 2026-08-27 04:53 639234024739225358
109 ms 216.40.34.41
14 2026-08-27 04:36 639234014311170162
110 ms 216.40.34.41
13 2026-08-27 04:18 639234003806017640
111 ms 216.40.34.41
12 2026-08-27 04:01 639233993356203030
110 ms 216.40.34.41
11 2026-08-27 03:08 639233961301716608
124 ms 216.40.34.41
10 2026-08-27 02:50 639233950834200647
112 ms 216.40.34.41
9 2026-08-27 02:33 639233940431849026
119 ms 216.40.34.41
8 2026-08-27 02:16 639233930110596398
2110 ms 216.40.34.41
7 2026-08-27 01:58 639233919705434540
111 ms 216.40.34.41
6 2026-08-27 01:41 639233909452807845
110 ms 216.40.34.41
5 2026-08-27 01:24 639233899096420820
111 ms 216.40.34.41
4 2026-08-27 01:07 639233888707824939
111 ms 216.40.34.41
3 2026-08-27 00:49 639233878461203802
129 ms 216.40.34.41
2 2026-08-27 00:32 639233868060868209
111 ms 216.40.34.41
1 2026-08-27 00:15 639233857450922991
122 ms 216.40.34.41