DNS response history for ns2.danielorlandophotography.com

ns2.danielorlandophotography.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 35 DNS check records, 35 successful responses, 0 failed responses, and 212 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.danielorlandophotography.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

212 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.121.33.104

Most recently resolved hosting IP on selected date

Successful Responses

35

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.danielorlandophotography.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
35 2026-08-25 12:11 639232566381512620
25 ms 91.121.33.104
34 2026-08-25 11:54 639232556111768563
2054 ms 91.121.33.104
33 2026-08-25 11:37 639232545839529039
33 ms 91.121.33.104
32 2026-08-25 11:20 639232535349285207
65 ms 91.121.33.104
31 2026-08-25 11:02 639232524938080723
36 ms 91.121.33.104
30 2026-08-25 10:09 639232492740373468
44 ms 91.121.33.104
29 2026-08-25 09:51 639232482235303141
47 ms 91.121.33.104
28 2026-08-25 09:34 639232471861770303
46 ms 91.121.33.104
27 2026-08-25 09:17 639232461630217327
32 ms 91.121.33.104
26 2026-08-25 09:00 639232451282965990
42 ms 91.121.33.104
25 2026-08-25 08:42 639232440814614938
62 ms 91.121.33.104
24 2026-08-25 08:25 639232430410720425
64 ms 91.121.33.104
23 2026-08-25 08:08 639232420003096185
94 ms 91.121.33.104
22 2026-08-25 07:50 639232409467287444
24 ms 91.121.33.104
21 2026-08-25 07:33 639232399077195997
52 ms 91.121.33.104
20 2026-08-25 07:15 639232388731528337
29 ms 91.121.33.104
19 2026-08-25 06:58 639232378288598612
44 ms 91.121.33.104
18 2026-08-25 06:04 639232346196373643
25 ms 91.121.33.104
17 2026-08-25 05:48 639232336112370741
34 ms 91.121.33.104
16 2026-08-25 05:31 639232326146508970
55 ms 91.121.33.104
15 2026-08-25 05:15 639232316189381720
45 ms 91.121.33.104
14 2026-08-25 04:58 639232306217998913
35 ms 91.121.33.104
13 2026-08-25 04:41 639232296255744174
32 ms 91.121.33.104
12 2026-08-25 04:24 639232286095760789
38 ms 91.121.33.104
11 2026-08-25 04:08 639232276086186273
16 ms 91.121.33.104
10 2026-08-25 03:51 639232265900986425
39 ms 91.121.33.104
9 2026-08-25 03:34 639232255723518075
25 ms 91.121.33.104
8 2026-08-25 03:17 639232245484452890
36 ms 91.121.33.104
7 2026-08-25 02:59 639232235157175331
2073 ms 91.121.33.104
6 2026-08-25 02:06 639232203197189095
34 ms 91.121.33.104
5 2026-08-25 01:49 639232192844564298
65 ms 91.121.33.104
4 2026-08-25 01:32 639232182496008942
12 ms 91.121.33.104
3 2026-08-25 01:14 639232172197053132
9 ms 91.121.33.104
2 2026-08-25 00:21 639232140250307418
2032 ms 91.121.33.104
1 2026-08-25 00:04 639232129927860324
29 ms 91.121.33.104