DNS response history for ns2.exnweb.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

341 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.79.104.50

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.exnweb.com

Showing DNS history for 2026-08-28 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-28 11:39 639235132147470568
231 ms 51.79.104.50
27 2026-08-28 11:22 639235121907744088
352 ms 51.79.104.50
26 2026-08-28 11:05 639235111428014262
353 ms 51.79.104.50
25 2026-08-28 10:47 639235100921813626
237 ms 51.79.104.50
24 2026-08-28 09:54 639235068670703481
347 ms 51.79.104.50
23 2026-08-28 09:36 639235058337459445
358 ms 51.79.104.50
22 2026-08-28 09:19 639235047825109146
348 ms 51.79.104.50
21 2026-08-28 09:02 639235037383229033
356 ms 51.79.104.50
20 2026-08-28 08:08 639235005619242711
350 ms 51.79.104.50
19 2026-08-28 07:51 639234995310346584
358 ms 51.79.104.50
18 2026-08-28 07:34 639234984946548933
351 ms 51.79.104.50
17 2026-08-28 07:17 639234974608077290
233 ms 51.79.104.50
16 2026-08-28 06:23 639234942529845595
230 ms 51.79.104.50
15 2026-08-28 06:06 639234932259126627
343 ms 51.79.104.50
14 2026-08-28 05:49 639234921916735988
228 ms 51.79.104.50
13 2026-08-28 05:32 639234911470038027
353 ms 51.79.104.50
12 2026-08-28 04:39 639234879588411654
231 ms 51.79.104.50
11 2026-08-28 04:21 639234869341589104
213 ms 51.79.104.50
10 2026-08-28 04:04 639234859012216675
2218 ms 51.79.104.50
9 2026-08-28 03:47 639234848695364934
231 ms 51.79.104.50
8 2026-08-28 02:54 639234816952458162
2 ms 51.79.104.50
7 2026-08-28 02:37 639234806773081598
2 ms 51.79.104.50
6 2026-08-28 02:20 639234796382955255
349 ms 51.79.104.50
5 2026-08-28 02:03 639234786015782563
351 ms 51.79.104.50
4 2026-08-28 01:09 639234753811917646
348 ms 51.79.104.50
3 2026-08-28 00:52 639234743739767811
2 ms 51.79.104.50
2 2026-08-28 00:35 639234733372362811
227 ms 51.79.104.50
1 2026-08-28 00:18 639234723048550337
350 ms 51.79.104.50