DNS response history for ns.sdm-d.com

ns.sdm-d.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 29 DNS check records, 29 successful responses, 0 failed responses, and 448 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 ns.sdm-d.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

448 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.137.113.150

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns.sdm-d.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
29 2026-08-26 09:18 639233318749762337
285 ms 203.137.113.150
28 2026-08-26 09:00 639233308387917838
500 ms 203.137.113.150
27 2026-08-26 08:43 639233297961740122
479 ms 203.137.113.150
26 2026-08-26 08:26 639233287487159094
493 ms 203.137.113.150
25 2026-08-26 08:08 639233276995531707
485 ms 203.137.113.150
24 2026-08-26 07:51 639233266521568229
500 ms 203.137.113.150
23 2026-08-26 07:33 639233256081047431
487 ms 203.137.113.150
22 2026-08-26 06:39 639233223620132921
491 ms 203.137.113.150
21 2026-08-26 06:22 639233213287814244
484 ms 203.137.113.150
20 2026-08-26 06:05 639233202925983161
503 ms 203.137.113.150
19 2026-08-26 05:47 639233192644780696
490 ms 203.137.113.150
18 2026-08-26 05:30 639233182401183833
488 ms 203.137.113.150
17 2026-08-26 05:13 639233172074181051
497 ms 203.137.113.150
16 2026-08-26 04:56 639233161808421455
493 ms 203.137.113.150
15 2026-08-26 04:39 639233151357344052
492 ms 203.137.113.150
14 2026-08-26 04:21 639233141034116946
494 ms 203.137.113.150
13 2026-08-26 04:04 639233130828334142
492 ms 203.137.113.150
12 2026-08-26 03:47 639233120373450007
486 ms 203.137.113.150
11 2026-08-26 03:30 639233110066216193
508 ms 203.137.113.150
10 2026-08-26 02:37 639233078065410564
487 ms 203.137.113.150
9 2026-08-26 02:19 639233067787457832
7 ms 203.137.113.150
8 2026-08-26 02:02 639233057501801162
495 ms 203.137.113.150
7 2026-08-26 01:45 639233047089431703
9 ms 203.137.113.150
6 2026-08-26 01:28 639233036754790688
311 ms 203.137.113.150
5 2026-08-26 01:11 639233026412602472
485 ms 203.137.113.150
4 2026-08-26 00:53 639233016064066127
491 ms 203.137.113.150
3 2026-08-26 00:36 639233005922655772
599 ms 203.137.113.150
2 2026-08-26 00:19 639232995672256907
488 ms 203.137.113.150
1 2026-08-26 00:02 639232985300872416
485 ms 203.137.113.150