DNS response history for ns2.360safe.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

525 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

106.120.161.6

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.360safe.com

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:08 639235258803654519
174 ms 106.120.161.6
35 2026-08-28 14:50 639235248596087996
2163 ms 106.120.161.6
34 2026-08-28 14:33 639235238225955920
168 ms 106.120.161.6
33 2026-08-28 14:16 639235227727862105
325 ms 106.120.161.6
32 2026-08-28 13:22 639235195230848570
167 ms 106.120.161.6
31 2026-08-28 13:04 639235184840503274
167 ms 106.120.161.6
30 2026-08-28 12:47 639235174453894956
165 ms 106.120.161.6
29 2026-08-28 12:29 639235163898672622
164 ms 106.120.161.6
28 2026-08-28 11:36 639235132147470568
174 ms 106.120.161.6
27 2026-08-28 11:19 639235121907744088
242 ms 106.120.161.6
26 2026-08-28 11:02 639235111428014262
166 ms 106.120.161.6
25 2026-08-28 10:44 639235100921813626
177 ms 106.120.161.6
24 2026-08-28 09:51 639235068670703481
2158 ms 106.120.161.6
23 2026-08-28 09:33 639235058337459445
171 ms 106.120.161.6
22 2026-08-28 09:16 639235047825109146
165 ms 106.120.161.6
21 2026-08-28 08:58 639235037383229033
163 ms 106.120.161.6
20 2026-08-28 08:05 639235005619242711
250 ms 106.120.161.6
19 2026-08-28 07:48 639234995310346584
164 ms 106.120.161.6
18 2026-08-28 07:31 639234984946548933
327 ms 106.120.161.6
17 2026-08-28 07:14 639234974608077290
173 ms 106.120.161.6
16 2026-08-28 06:20 639234942529845595
164 ms 106.120.161.6
15 2026-08-28 06:03 639234932259126627
175 ms 106.120.161.6
14 2026-08-28 05:46 639234921916735988
174 ms 106.120.161.6
13 2026-08-28 05:29 639234911470038027
165 ms 106.120.161.6
12 2026-08-28 04:35 639234879588411654
210 ms 106.120.161.6
11 2026-08-28 04:18 639234869341589104
4296 ms 106.120.161.6
10 2026-08-28 04:01 639234859012216675
172 ms 106.120.161.6
9 2026-08-28 03:44 639234848695364934
2160 ms 106.120.161.6
8 2026-08-28 02:51 639234816952458162
2222 ms 106.120.161.6
7 2026-08-28 02:34 639234806773081598
168 ms 106.120.161.6
6 2026-08-28 02:17 639234796382955255
174 ms 106.120.161.6
5 2026-08-28 01:59 639234786015782563
168 ms 106.120.161.6
4 2026-08-28 01:06 639234753811917646
168 ms 106.120.161.6
3 2026-08-28 00:49 639234743739767811
171 ms 106.120.161.6
2 2026-08-28 00:32 639234733372362811
334 ms 106.120.161.6
1 2026-08-28 00:15 639234723048550337
168 ms 106.120.161.6