Time Machine
Indicator → WHOIS/BGP state diff between its two most recent snapshots.
- 36 historical snapshot(s) for google.comwhisper.history
- 2 change(s) between the two latest snapshots: Expiry date, Create datewhisper.history
| field | from | to |
|---|---|---|
| Expiry date | 2026-01-29 | 2028-09-13 |
| Create date | 2006-01-29 | 1997-09-15 |
| queryTime | registrar | registrant | nameServers | expiryDate |
|---|---|---|---|---|
| 2025-01-07 00:39:43 | MarkMonitor, Inc. | Google LLC | ns1.google.com|ns2.google.com|ns3.google.com|ns4.google.com | 2028-09-13 |
| 2024-12-26 18:45:16 | MarkMonitor, Inc. | Google LLC | ns1.google.com|ns2.google.com|ns3.google.com|ns4.google.com | 2026-01-29 |
| 2024-12-21 12:42:01 | MarkMonitor, Inc. | Google LLC | ns1.google.com|ns2.google.com|ns3.google.com|ns4.google.com | 2028-09-13 |
| 2024-12-19 09:45:56 | MarkMonitor, Inc. | Google LLC | ns1.google.com|ns2.google.com|ns3.google.com|ns4.google.com | 2028-09-13 |
| 2024-11-05 21:15:21 | MarkMonitor, Inc. | Google LLC | ns1.google.com|ns2.google.com|ns3.google.com|ns4.google.com | 2028-09-13 |
| 2024-09-13 03:45:03 | MarkMonitor, Inc. | Google LLC | ns1.google.com|ns2.google.com|ns3.google.com|ns4.google.com | 2028-09-13 |
The one query behind this▾
CALL whisper.history($indicator)
Snapshot from a max-depth run on Jun 26, 2026. Run it again for live data. time-machine
Free tier — no credit card. Runs up to 3 hops deep; Pro goes to 5.
What it solves
Knowing that something changed is easy; knowing what changed, and when, usually means digging through history exports. This puts the before and after side by side.
The run pulls the last two recorded states for the indicator and diffs them, so a registrar swap, a new nameserver, or a routing change reads at a glance.
Pull two history exports and eyeball the differences.
- historical WHOIS
- BGP archives
- manual diffing
Dig deeper
Read the how-to
The documentation for this flow — the queries explained, with variants you can adapt.
Open the documentation →Related flows
All use cases →Indicator Investigation
Drop in any domain, IP, ASN, or prefix and get back a verdict you can defend, with the evidence and sources attached.
Route-Health Checker
Hand it a prefix or ASN and get a routing-integrity card: MOAS conflicts, RPKI coverage, prefix status, and footprint.