Skip to main content

Drift Timeline

Posture changes for pq2.resolutionscope.com

No Drift Events

No posture changes have been detected for pq2.resolutionscope.com. Drift events are recorded when the security posture hash changes between analyses.

Posture Hash History 50
Date Posture Hash Report
22 Nov 2026 17:03 UTC 5664401de3c204df View
21 Nov 2026 17:02 UTC 5664401de3c204df View
20 Nov 2026 17:03 UTC 5664401de3c204df View
18 Nov 2026 17:03 UTC 5664401de3c204df View
17 Nov 2026 17:02 UTC 5664401de3c204df View
16 Nov 2026 17:02 UTC 5664401de3c204df View
15 Nov 2026 17:03 UTC 5664401de3c204df View
14 Nov 2026 17:02 UTC 5664401de3c204df View
13 Nov 2026 17:01 UTC 5664401de3c204df View
12 Nov 2026 17:03 UTC 5664401de3c204df View
11 Nov 2026 17:02 UTC 5664401de3c204df View
10 Nov 2026 17:02 UTC 5664401de3c204df View
9 Nov 2026 17:04 UTC 5664401de3c204df View
8 Nov 2026 17:02 UTC 5664401de3c204df View
7 Nov 2026 17:02 UTC 5664401de3c204df View
6 Nov 2026 17:02 UTC 5664401de3c204df View
5 Nov 2026 17:35 UTC 5664401de3c204df View
4 Nov 2026 17:03 UTC 5664401de3c204df View
30 Oct 2026 16:03 UTC 5664401de3c204df View
29 Oct 2026 16:19 UTC 5664401de3c204df View
29 Oct 2026 16:06 UTC 5664401de3c204df View
29 Oct 2026 16:01 UTC 5664401de3c204df View
28 Oct 2026 16:02 UTC 5664401de3c204df View
27 Oct 2026 16:01 UTC 5664401de3c204df View
26 Oct 2026 16:02 UTC 5664401de3c204df View
25 Oct 2026 16:43 UTC 5664401de3c204df View
24 Oct 2026 16:03 UTC 5664401de3c204df View
23 Oct 2026 16:48 UTC 5664401de3c204df View
23 Oct 2026 16:11 UTC 5664401de3c204df View
23 Oct 2026 16:02 UTC 5664401de3c204df View
22 Oct 2026 16:19 UTC 5664401de3c204df View
22 Oct 2026 16:02 UTC 5664401de3c204df View
21 Oct 2026 16:02 UTC 5664401de3c204df View
14 Oct 2026 16:02 UTC 5664401de3c204df View
13 Oct 2026 16:11 UTC 5664401de3c204df View
12 Oct 2026 16:01 UTC 5664401de3c204df View
11 Oct 2026 16:02 UTC 5664401de3c204df View
9 Oct 2026 16:10 UTC 5664401de3c204df View
8 Oct 2026 16:03 UTC 5664401de3c204df View
6 Oct 2026 16:07 UTC 5664401de3c204df View
5 Oct 2026 16:04 UTC 5664401de3c204df View
4 Oct 2026 21:07 UTC 5664401de3c204df View
4 Oct 2026 16:03 UTC 5664401de3c204df View
2 Oct 2026 16:03 UTC 5664401de3c204df View
1 Oct 2026 16:04 UTC 5664401de3c204df View
30 Sep 2026 16:04 UTC 5664401de3c204df View
29 Sep 2026 17:15 UTC 5664401de3c204df View
28 Sep 2026 16:03 UTC 5664401de3c204df View
27 Sep 2026 16:02 UTC 5664401de3c204df View
26 Sep 2026 16:03 UTC 5664401de3c204df View
Straight talk about your data.

We use two cookies, both essential:

  • _csrf — Prevents cross-site request forgery. Required for form submissions. Security-only.
  • _dns_session — Only exists if you choose to sign in. No account required to use DNS Tool.

We log your IP address for two reasons: rate limiting (so nobody abuses the service) and security (identifying malicious actors and complying with legal obligations). We check source geography for analysis accuracy — DNS responses vary by region, and knowing which resolver answered from where makes the science better.

No tracking cookies. No analytics cookies. No ad networks. No data brokers. Our code is open-core — the application framework is publicly available under BUSL-1.1 with timed Apache-2.0 conversion. Verify it yourself.

Public analyses are archived by a third party. When a scan is not marked private or run as /dev/null, its report URL is submitted to the Internet Archive, which creates a permanent public record outside our control. That is deliberate — it gives every published analysis tamper-evident provenance independent of us — but it is not reversible, so it is stated here before you scan rather than after.

If you create an account and want out, account deletion removes your login and scan history. Public domain analyses remain available because they contain only public DNS records, already hashed. Full details: Privacy Policy.