Skip to main content

Drift Timeline

Posture changes for example.com

Drift Events 1
2 Aug 2026 04:14 UTC Warning
DKIM Status
warning success
Hash: 3119dacc7db4b468 692a1c18a4406fbe
Posture Hash History 50
Date Posture Hash Report
18 Aug 2026 06:50 UTC cb381ae0d57126cc View
17 Aug 2026 20:38 UTC cb381ae0d57126cc View
17 Aug 2026 19:11 UTC 8390411ee8e605ed View
12 Aug 2026 13:24 UTC 692a1c18a4406fbe View
12 Aug 2026 13:24 UTC 692a1c18a4406fbe View
12 Aug 2026 13:23 UTC 692a1c18a4406fbe View
12 Aug 2026 13:13 UTC 692a1c18a4406fbe View
12 Aug 2026 13:13 UTC 692a1c18a4406fbe View
2 Aug 2026 04:14 UTC 692a1c18a4406fbe View
12 Jul 2026 02:24 UTC 3119dacc7db4b468 View
29 Jun 2026 02:56 UTC 3119dacc7db4b468 View
30 Apr 2026 15:38 UTC 3119dacc7db4b468 View
30 Apr 2026 15:38 UTC 3119dacc7db4b468 View
30 Apr 2026 15:19 UTC 3119dacc7db4b468 View
30 Apr 2026 15:19 UTC 3119dacc7db4b468 View
30 Apr 2026 13:47 UTC 3119dacc7db4b468 View
30 Apr 2026 13:46 UTC 3119dacc7db4b468 View
30 Apr 2026 13:46 UTC 3119dacc7db4b468 View
30 Apr 2026 13:40 UTC 3119dacc7db4b468 View
30 Apr 2026 13:20 UTC 3119dacc7db4b468 View
30 Apr 2026 13:20 UTC 3119dacc7db4b468 View
30 Apr 2026 13:09 UTC 3119dacc7db4b468 View
30 Apr 2026 13:08 UTC 3119dacc7db4b468 View
30 Apr 2026 12:23 UTC 3119dacc7db4b468 View
30 Apr 2026 12:23 UTC 3119dacc7db4b468 View
30 Apr 2026 12:23 UTC 3119dacc7db4b468 View
29 Apr 2026 13:20 UTC 3119dacc7db4b468 View
29 Apr 2026 13:19 UTC 3119dacc7db4b468 View
29 Apr 2026 13:16 UTC 3119dacc7db4b468 View
29 Apr 2026 13:16 UTC 3119dacc7db4b468 View
28 Apr 2026 19:21 UTC 3119dacc7db4b468 View
28 Apr 2026 13:34 UTC 3119dacc7db4b468 View
28 Apr 2026 04:01 UTC 3119dacc7db4b468 View
28 Apr 2026 01:55 UTC 3119dacc7db4b468 View
26 Apr 2026 00:01 UTC 3119dacc7db4b468 View
26 Apr 2026 00:00 UTC 3119dacc7db4b468 View
26 Apr 2026 00:00 UTC 3119dacc7db4b468 View
24 Apr 2026 20:55 UTC 3119dacc7db4b468 View
24 Apr 2026 20:55 UTC 3119dacc7db4b468 View
24 Apr 2026 20:54 UTC 3119dacc7db4b468 View
23 Apr 2026 14:23 UTC 3119dacc7db4b468 View
22 Apr 2026 14:10 UTC 3119dacc7db4b468 View
22 Apr 2026 14:10 UTC 3119dacc7db4b468 View
22 Apr 2026 00:21 UTC 3119dacc7db4b468 View
21 Apr 2026 14:23 UTC 3119dacc7db4b468 View
21 Apr 2026 14:23 UTC 3119dacc7db4b468 View
21 Apr 2026 14:23 UTC 3119dacc7db4b468 View
20 Apr 2026 20:36 UTC 3119dacc7db4b468 View
20 Apr 2026 14:35 UTC 3119dacc7db4b468 View
20 Apr 2026 14:34 UTC 3119dacc7db4b468 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.