DNS response history for ns2.domtech.org

ns2.domtech.org 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-28. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 470 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.domtech.org.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

470 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.210.121.116

Most recently resolved hosting IP on selected date

Successful Responses

36

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.domtech.org

Showing DNS history for 2026-08-28 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
36 2026-08-28 15:07 639235258803654519
14 ms 54.210.121.116
35 2026-08-28 14:49 639235248596087996
3 ms 54.210.121.116
34 2026-08-28 14:32 639235238225955920
4 ms 54.210.121.116
33 2026-08-28 14:15 639235227727862105
346 ms 54.210.121.116
32 2026-08-28 13:21 639235195230848570
4357 ms 54.210.121.116
31 2026-08-28 13:03 639235184840503274
239 ms 54.210.121.116
30 2026-08-28 12:46 639235174453894956
464 ms 54.210.121.116
29 2026-08-28 12:28 639235163898672622
348 ms 54.210.121.116
28 2026-08-28 11:36 639235132147470568
196 ms 54.210.121.116
27 2026-08-28 11:18 639235121907744088
4 ms 54.210.121.116
26 2026-08-28 11:01 639235111428014262
4 ms 54.210.121.116
25 2026-08-28 10:43 639235100921813626
314 ms 54.210.121.116
24 2026-08-28 09:50 639235068670703481
392 ms 54.210.121.116
23 2026-08-28 09:33 639235058337459445
273 ms 54.210.121.116
22 2026-08-28 09:15 639235047825109146
100 ms 54.210.121.116
21 2026-08-28 08:57 639235037383229033
248 ms 54.210.121.116
20 2026-08-28 08:05 639235005619242711
470 ms 54.210.121.116
19 2026-08-28 07:48 639234995310346584
201 ms 54.210.121.116
18 2026-08-28 07:30 639234984946548933
218 ms 54.210.121.116
17 2026-08-28 07:13 639234974608077290
443 ms 54.210.121.116
16 2026-08-28 06:19 639234942529845595
6 ms 54.210.121.116
15 2026-08-28 06:02 639234932259126627
199 ms 54.210.121.116
14 2026-08-28 05:45 639234921916735988
573 ms 54.210.121.116
13 2026-08-28 05:28 639234911470038027
343 ms 54.210.121.116
12 2026-08-28 04:35 639234879588411654
112 ms 54.210.121.116
11 2026-08-28 04:18 639234869341589104
241 ms 54.210.121.116
10 2026-08-28 04:00 639234859012216675
802 ms 54.210.121.116
9 2026-08-28 03:43 639234848695364934
2032 ms 54.210.121.116
8 2026-08-28 02:50 639234816952458162
7 ms 54.210.121.116
7 2026-08-28 02:33 639234806773081598
220 ms 54.210.121.116
6 2026-08-28 02:16 639234796382955255
119 ms 54.210.121.116
5 2026-08-28 01:59 639234786015782563
452 ms 54.210.121.116
4 2026-08-28 01:05 639234753811917646
242 ms 54.210.121.116
3 2026-08-28 00:48 639234743739767811
104 ms 54.210.121.116
2 2026-08-28 00:31 639234733372362811
351 ms 54.210.121.116
1 2026-08-28 00:14 639234723048550337
2484 ms 54.210.121.116