DNS response history for ns2.safeusaonlinegambling.com

ns2.safeusaonlinegambling.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 957 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.safeusaonlinegambling.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

957 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

168.235.79.113

Most recently resolved hosting IP on selected date

Successful Responses

26

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.safeusaonlinegambling.com

Showing DNS history for 2026-08-24 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
26 2026-08-24 10:44 639231641791249939
1537 ms 168.235.79.113
25 2026-08-24 10:28 639231631866211033
963 ms 168.235.79.113
24 2026-08-24 10:11 639231621644955316
1698 ms 168.235.79.113
23 2026-08-24 09:54 639231611478799259
3 ms 168.235.79.113
22 2026-08-24 09:01 639231579923718211
3 ms 168.235.79.113
21 2026-08-24 08:45 639231569810702936
1608 ms 168.235.79.113
20 2026-08-24 08:28 639231559762411619
1705 ms 168.235.79.113
19 2026-08-24 08:11 639231549663595407
6 ms 168.235.79.113
18 2026-08-24 07:18 639231518076817246
1850 ms 168.235.79.113
17 2026-08-24 07:02 639231508078650885
2 ms 168.235.79.113
16 2026-08-24 06:45 639231498210697093
2177 ms 168.235.79.113
15 2026-08-24 06:29 639231488109699360
1910 ms 168.235.79.113
14 2026-08-24 05:36 639231456772510692
3735 ms 168.235.79.113
13 2026-08-24 05:20 639231447084631185
3 ms 168.235.79.113
12 2026-08-24 05:03 639231437208519473
3 ms 168.235.79.113
11 2026-08-24 04:47 639231427209627490
4 ms 168.235.79.113
10 2026-08-24 03:54 639231395791246644
3 ms 168.235.79.113
9 2026-08-24 03:38 639231386075551458
3 ms 168.235.79.113
8 2026-08-24 03:22 639231376208713791
3 ms 168.235.79.113
7 2026-08-24 03:05 639231366170589276
2152 ms 168.235.79.113
6 2026-08-24 02:13 639231334732159368
1753 ms 168.235.79.113
5 2026-08-24 01:56 639231325035670078
1768 ms 168.235.79.113
4 2026-08-24 01:40 639231315132253837
1990 ms 168.235.79.113
3 2026-08-24 01:23 639231305014280808
4 ms 168.235.79.113
2 2026-08-24 00:31 639231273779380675
2 ms 168.235.79.113
1 2026-08-24 00:15 639231264180839154
3 ms 168.235.79.113