DNS response history for blog2.mordns.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

465 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

151.106.3.205

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 blog2.mordns.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
37 2026-08-25 12:50 639232587225721862
64 ms 151.106.3.205
36 2026-08-25 12:32 639232576780683689
29 ms 151.106.3.205
35 2026-08-25 12:15 639232566381512620
534 ms 151.106.3.205
34 2026-08-25 11:58 639232556111768563
52 ms 151.106.3.205
33 2026-08-25 11:41 639232545839529039
60 ms 151.106.3.205
32 2026-08-25 11:23 639232535349285207
28 ms 151.106.3.205
31 2026-08-25 11:06 639232524938080723
44 ms 151.106.3.205
30 2026-08-25 10:12 639232492740373468
19 ms 151.106.3.205
29 2026-08-25 09:55 639232482235303141
40 ms 151.106.3.205
28 2026-08-25 09:37 639232471861770303
2043 ms 151.106.3.205
27 2026-08-25 09:20 639232461630217327
44 ms 151.106.3.205
26 2026-08-25 09:03 639232451282965990
37 ms 151.106.3.205
25 2026-08-25 08:46 639232440814614938
2008 ms 151.106.3.205
24 2026-08-25 08:28 639232430410720425
81 ms 151.106.3.205
23 2026-08-25 08:11 639232420003096185
608 ms 151.106.3.205
22 2026-08-25 07:54 639232409467287444
2057 ms 151.106.3.205
21 2026-08-25 07:36 639232399077195997
24 ms 151.106.3.205
20 2026-08-25 07:19 639232388731528337
54 ms 151.106.3.205
19 2026-08-25 07:02 639232378288598612
16 ms 151.106.3.205
18 2026-08-25 06:08 639232346196373643
50 ms 151.106.3.205
17 2026-08-25 05:51 639232336112370741
22 ms 151.106.3.205
16 2026-08-25 05:35 639232326146508970
2026 ms 151.106.3.205
15 2026-08-25 05:18 639232316189381720
62 ms 151.106.3.205
14 2026-08-25 05:01 639232306217998913
2023 ms 151.106.3.205
13 2026-08-25 04:45 639232296255744174
16 ms 151.106.3.205
12 2026-08-25 04:28 639232286095760789
28 ms 151.106.3.205
11 2026-08-25 04:11 639232276086186273
2026 ms 151.106.3.205
10 2026-08-25 03:54 639232265900986425
2054 ms 151.106.3.205
9 2026-08-25 03:37 639232255723518075
32 ms 151.106.3.205
8 2026-08-25 03:20 639232245484452890
546 ms 151.106.3.205
7 2026-08-25 03:03 639232235157175331
73 ms 151.106.3.205
6 2026-08-25 02:10 639232203197189095
24 ms 151.106.3.205
5 2026-08-25 01:52 639232192844564298
69 ms 151.106.3.205
4 2026-08-25 01:35 639232182496008942
23 ms 151.106.3.205
3 2026-08-25 01:18 639232172197053132
54 ms 151.106.3.205
2 2026-08-25 00:25 639232140250307418
80 ms 151.106.3.205
1 2026-08-25 00:08 639232129927860324
170 ms 151.106.3.205