DNS response history for newns.25nendo.com

newns.25nendo.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 35 DNS check records, 35 successful responses, 0 failed responses, and 635 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 newns.25nendo.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

635 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.123.9.39

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 newns.25nendo.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
35 2026-08-27 11:17 639234253963286387
544 ms 153.123.9.39
34 2026-08-27 11:00 639234243654907465
791 ms 153.123.9.39
33 2026-08-27 10:43 639234233269654413
784 ms 153.123.9.39
32 2026-08-27 10:25 639234222943951923
809 ms 153.123.9.39
31 2026-08-27 10:08 639234212558002823
551 ms 153.123.9.39
30 2026-08-27 09:51 639234202117531850
529 ms 153.123.9.39
29 2026-08-27 09:33 639234191649612722
823 ms 153.123.9.39
28 2026-08-27 09:16 639234181105879568
544 ms 153.123.9.39
27 2026-08-27 08:58 639234170713214496
532 ms 153.123.9.39
26 2026-08-27 08:41 639234160341037652
533 ms 153.123.9.39
25 2026-08-27 08:24 639234149799404224
794 ms 153.123.9.39
24 2026-08-27 08:06 639234139553286469
825 ms 153.123.9.39
23 2026-08-27 07:12 639234107183588293
530 ms 153.123.9.39
22 2026-08-27 06:55 639234096905435724
546 ms 153.123.9.39
21 2026-08-27 06:38 639234086579410775
535 ms 153.123.9.39
20 2026-08-27 06:21 639234076291157956
543 ms 153.123.9.39
19 2026-08-27 06:04 639234065981939454
542 ms 153.123.9.39
18 2026-08-27 05:47 639234055548642997
778 ms 153.123.9.39
17 2026-08-27 05:29 639234045267979603
691 ms 153.123.9.39
16 2026-08-27 05:12 639234034999717463
536 ms 153.123.9.39
15 2026-08-27 04:55 639234024739225358
522 ms 153.123.9.39
14 2026-08-27 04:38 639234014311170162
521 ms 153.123.9.39
13 2026-08-27 04:20 639234003806017640
700 ms 153.123.9.39
12 2026-08-27 04:03 639233993356203030
786 ms 153.123.9.39
11 2026-08-27 03:09 639233961301716608
527 ms 153.123.9.39
10 2026-08-27 02:52 639233950834200647
535 ms 153.123.9.39
9 2026-08-27 02:35 639233940431849026
809 ms 153.123.9.39
8 2026-08-27 02:17 639233930110596398
774 ms 153.123.9.39
7 2026-08-27 02:00 639233919705434540
535 ms 153.123.9.39
6 2026-08-27 01:43 639233909452807845
538 ms 153.123.9.39
5 2026-08-27 01:26 639233899096420820
793 ms 153.123.9.39
4 2026-08-27 01:08 639233888707824939
806 ms 153.123.9.39
3 2026-08-27 00:51 639233878461203802
532 ms 153.123.9.39
2 2026-08-27 00:34 639233868060868209
539 ms 153.123.9.39
1 2026-08-27 00:17 639233857450922991
549 ms 153.123.9.39