Drift Timeline
Posture changes for fredduval.com
No Drift Events
No posture changes have been detected for fredduval.com. Drift events are recorded when the security posture hash changes between analyses.
| Date | Posture Hash | Report |
|---|---|---|
| 10 Mar 2026 14:27 UTC | d2180e726f3340c1 | View |
| 9 Mar 2026 21:42 UTC | d2180e726f3340c1 | View |
| 26 Feb 2026 14:38 UTC | d2180e726f3340c1 | View |
| 26 Feb 2026 14:37 UTC | d2180e726f3340c1 | View |
| 26 Feb 2026 14:37 UTC | d2180e726f3340c1 | View |
| 26 Feb 2026 08:36 UTC | d2180e726f3340c1 | View |
| 25 Feb 2026 14:55 UTC | d2180e726f3340c1 | View |
| 24 Feb 2026 22:56 UTC | d2180e726f3340c1 | View |
| 23 Feb 2026 14:28 UTC | d2180e726f3340c1 | View |
| 22 Feb 2026 14:41 UTC | d2180e726f3340c1 | View |
| 22 Feb 2026 14:40 UTC | d2180e726f3340c1 | View |
| 22 Feb 2026 14:39 UTC | d2180e726f3340c1 | View |
| 22 Feb 2026 03:35 UTC | d2180e726f3340c1 | View |
| 22 Feb 2026 03:35 UTC | d2180e726f3340c1 | View |
| 22 Feb 2026 03:34 UTC | d2180e726f3340c1 | View |
| 21 Feb 2026 22:19 UTC | d2180e726f3340c1 | View |
| 21 Feb 2026 18:46 UTC | d2180e726f3340c1 | View |
| 21 Feb 2026 15:03 UTC | d2180e726f3340c1 | View |
| 21 Feb 2026 15:03 UTC | d2180e726f3340c1 | View |
| 21 Feb 2026 15:02 UTC | d2180e726f3340c1 | View |
| 20 Feb 2026 14:23 UTC | 66d957945ded8070 | View |
| 19 Feb 2026 14:16 UTC | b2b5c2e74b4b7d56 | View |
| 19 Feb 2026 14:16 UTC | b2b5c2e74b4b7d56 | View |
| 19 Feb 2026 14:15 UTC | b2b5c2e74b4b7d56 | View |
| 18 Feb 2026 14:22 UTC | b2b5c2e74b4b7d56 | View |
| 18 Feb 2026 07:46 UTC | b2b5c2e74b4b7d56 | View |
| 18 Feb 2026 06:19 UTC | b2b5c2e74b4b7d56 | View |
| 17 Feb 2026 23:57 UTC | b2b5c2e74b4b7d56 | View |
| 17 Feb 2026 23:12 UTC | b2b5c2e74b4b7d56 | View |
| 17 Feb 2026 14:24 UTC | b2b5c2e74b4b7d56 | View |
| 17 Feb 2026 14:24 UTC | b2b5c2e74b4b7d56 | View |
| 17 Feb 2026 10:30 UTC | b2b5c2e74b4b7d56 | View |
| 14 Feb 2026 18:29 UTC | (none) | View |
| 14 Feb 2026 17:39 UTC | (none) | View |
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.
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 Pledge.