DNS response history for ns2.domain-expiry-notice.com

ns2.domain-expiry-notice.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 32 DNS check records, 31 successful responses, 1 failed responses, and 182 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.domain-expiry-notice.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

182 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.206.161.3

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.domain-expiry-notice.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
32 2026-08-26 10:14 639233360361507238
47 ms 195.206.161.3
31 2026-08-26 09:57 639233350067824371
44 ms 195.206.161.3
30 2026-08-26 09:40 639233339545274518
173 ms 195.206.161.3
29 2026-08-26 09:22 639233329214918079
47 ms 195.206.161.3
28 2026-08-26 09:05 639233318749762337
24 ms 195.206.161.3
27 2026-08-26 08:48 639233308387917838
2044 ms 195.206.161.3
26 2026-08-26 08:30 639233297961740122
49 ms 195.206.161.3
25 2026-08-26 08:13 639233287487159094
-
24 2026-08-26 07:55 639233276995531707
2032 ms 195.206.161.3
23 2026-08-26 07:38 639233266521568229
130 ms 195.206.161.3
22 2026-08-26 07:21 639233256081047431
54 ms 195.206.161.3
21 2026-08-26 06:26 639233223620132921
60 ms 195.206.161.3
20 2026-08-26 06:09 639233213287814244
25 ms 195.206.161.3
19 2026-08-26 05:52 639233202925983161
24 ms 195.206.161.3
18 2026-08-26 05:35 639233192644780696
66 ms 195.206.161.3
17 2026-08-26 05:18 639233182401183833
49 ms 195.206.161.3
16 2026-08-26 05:00 639233172074181051
49 ms 195.206.161.3
15 2026-08-26 04:43 639233161808421455
5 ms 195.206.161.3
14 2026-08-26 04:26 639233151357344052
25 ms 195.206.161.3
13 2026-08-26 04:09 639233141034116946
49 ms 195.206.161.3
12 2026-08-26 03:52 639233130828334142
47 ms 195.206.161.3
11 2026-08-26 03:34 639233120373450007
52 ms 195.206.161.3
10 2026-08-26 03:17 639233110066216193
48 ms 195.206.161.3
9 2026-08-26 02:24 639233078065410564
82 ms 195.206.161.3
8 2026-08-26 02:07 639233067787457832
47 ms 195.206.161.3
7 2026-08-26 01:50 639233057501801162
55 ms 195.206.161.3
6 2026-08-26 01:32 639233047089431703
31 ms 195.206.161.3
5 2026-08-26 01:15 639233036754790688
44 ms 195.206.161.3
4 2026-08-26 00:58 639233026412602472
82 ms 195.206.161.3
3 2026-08-26 00:40 639233016064066127
50 ms 195.206.161.3
2 2026-08-26 00:24 639233005922655772
49 ms 195.206.161.3
1 2026-08-26 00:06 639232995672256907
45 ms 195.206.161.3