DNS response history for d.ns.dotmed.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

92 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.204.161.188

Most recently resolved hosting IP on selected date

Successful Responses

30

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 d.ns.dotmed.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
30 2026-08-26 09:42 639233339545274518
32 ms 15.204.161.188
29 2026-08-26 09:25 639233329214918079
7 ms 15.204.161.188
28 2026-08-26 09:08 639233318749762337
37 ms 15.204.161.188
27 2026-08-26 08:50 639233308387917838
12 ms 15.204.161.188
26 2026-08-26 08:33 639233297961740122
2026 ms 15.204.161.188
25 2026-08-26 08:15 639233287487159094
17 ms 15.204.161.188
24 2026-08-26 07:58 639233276995531707
31 ms 15.204.161.188
23 2026-08-26 07:40 639233266521568229
5 ms 15.204.161.188
22 2026-08-26 07:23 639233256081047431
24 ms 15.204.161.188
21 2026-08-26 06:29 639233223620132921
20 ms 15.204.161.188
20 2026-08-26 06:12 639233213287814244
6 ms 15.204.161.188
19 2026-08-26 05:54 639233202925983161
24 ms 15.204.161.188
18 2026-08-26 05:37 639233192644780696
31 ms 15.204.161.188
17 2026-08-26 05:20 639233182401183833
35 ms 15.204.161.188
16 2026-08-26 05:03 639233172074181051
19 ms 15.204.161.188
15 2026-08-26 04:46 639233161808421455
11 ms 15.204.161.188
14 2026-08-26 04:28 639233151357344052
41 ms 15.204.161.188
13 2026-08-26 04:11 639233141034116946
6 ms 15.204.161.188
12 2026-08-26 03:54 639233130828334142
52 ms 15.204.161.188
11 2026-08-26 03:37 639233120373450007
7 ms 15.204.161.188
10 2026-08-26 03:20 639233110066216193
24 ms 15.204.161.188
9 2026-08-26 02:26 639233078065410564
15 ms 15.204.161.188
8 2026-08-26 02:09 639233067787457832
20 ms 15.204.161.188
7 2026-08-26 01:52 639233057501801162
32 ms 15.204.161.188
6 2026-08-26 01:35 639233047089431703
16 ms 15.204.161.188
5 2026-08-26 01:17 639233036754790688
52 ms 15.204.161.188
4 2026-08-26 01:00 639233026412602472
19 ms 15.204.161.188
3 2026-08-26 00:43 639233016064066127
53 ms 15.204.161.188
2 2026-08-26 00:26 639233005922655772
21 ms 15.204.161.188
1 2026-08-26 00:09 639232995672256907
53 ms 15.204.161.188