# TreasurySolutions.com historical email date follow up

Prepared 5 November 2026, 11:41 UTC. This follows the supplied claim that an email record was opened on 17 March 2025. Public history providers and their ordinary filter controls were checked without authentication, payment, CAPTCHA bypass, mailbox testing or subject contact.

**Result:** the exact March date is still unverified. A public history provider independently shows the domain’s Microsoft mail-routing record with a **14 April 2025 first-seen date**. Its primary documentation defines the relevant date as appearance in the provider’s index—not creation of an email account.

## New historical observations

| Finding | Provider-visible dates | Public record | Evidential meaning |
| --- | --- | --- | --- |
| HD-F01 · Recorded historical MX observation | First seen 2025-04-14; last seen 2026-08-02 | Priority 0, `treasurysolutions-com.mail.protection.outlook.com.` | A mail-routing rule recorded in this provider’s history; does not identify the user of any mailbox or its creation date |
| HD-F02 · Recorded historical TXT observation | First seen 2025-04-14; last seen 2026-08-02 | `MS=ms19438693` | A Microsoft-style verification token present in the provider’s historical data; does not itself establish a legal operator |
| HD-F03 · Recorded historical SPF observation | First seen 2024-03-10; last seen 2025-01-26 | `v=spf1 -all` | The visible older policy authorized no senders; another SPF history item was gated and was not inspected |
| HD-F04 · Recorded historical NS observation | First seen 2025-04-14; last seen 2025-04-14 | `ns39.domaincontrol.com.` and `ns40.domaincontrol.com.` | A nameserver configuration observed by this provider; not a company or ownership identifier |

Primary links, generated by the site’s actual public controls:

- [MX history](https://whoisfreaks.com/tools/dns/history/lookup/treasurysolutions.com?type=MX&page=1)
- [TXT history](https://whoisfreaks.com/tools/dns/history/lookup/treasurysolutions.com?type=TXT&page=1)
- [SPF history](https://whoisfreaks.com/tools/dns/history/lookup/treasurysolutions.com?type=SPF&page=1)
- [NS history](https://whoisfreaks.com/tools/dns/history/lookup/treasurysolutions.com?type=NS&page=1)

The public MX and TXT results each said one total record. The SPF result said two, and NS said eight. The latter pages masked further entries behind sign-in. The template’s masked rows displayed `1999-12-31` beside generic placeholder values: those are **not findings or usable historical dates**. The site also warned that anonymous results may be stale. No additional records were inferred from the count or read through an authentication boundary.

## What a history date represents

The provider’s [DNS database documentation](https://whoisfreaks.com/documentation/dns-database), retrieved on 5 November 2026 at 11:41 UTC, describes MX `date_created` as the date a routing rule first entered its index, and `last_seen` as its most recent confirmation. Those fields describe the provider’s observation history. They do not certify when an organization ordered hosting, created `ivan@...` or `elena@...`, or first used those addresses.

The April observation therefore neither proves nor disproves a different provider seeing a record on 17 March. Coverage and observation dates vary. It does independently establish an additional historical mail-infrastructure point that can be used in the case chronology with its provider provenance attached.

The default all-record response also exposes SOA serial `2025031410`. It resembles a date-based serial, but it cannot prove a 14 March or 17 March email event. [RFC 1035, section 3.3.13](https://www.rfc-editor.org/rfc/rfc1035#section-3.3.13) specifies the SOA serial as a zone version integer. It is not a mailbox-creation timestamp.

The earlier report’s provider correction remains: current MX points to Microsoft mail protection and SPF includes `secureserver.net`, which official GoDaddy documentation associates with its services. Namecheap Private Email documentation gives different MX/SPF values. A historical Namecheap relationship has not been established or ruled out by these current records. See [the original domain investigation](email-domain-history.md) for preserved DNS and registrar evidence.

## Source capture and access limits

| Capture | Recorded retrieval / observation time UTC | Evidence file |
| --- | --- | --- |
| Default public WhoisFreaks history page | 2026-11-05 11:38:13.898684 | `sources/email-domain-followup/whoisfreaks-history.{html,txt,json}` |
| MX public UI response | 2026-11-05 11:40:20.332; initially inspected about 11:39 | `sources/email-domain-followup/whoisfreaks-mx-visible.txt` |
| Filtered MX raw HTTP response | HTTP server Date 2026-11-05 11:39:58 | `sources/email-domain-followup/whoisfreaks-mx.html`, `whoisfreaks-mx-headers.txt` |
| TXT public UI response | 2026-11-05 11:40:40.677 | `sources/email-domain-followup/whoisfreaks-txt-visible.txt` |
| SPF public UI response | 2026-11-05 11:40:54.219 | `sources/email-domain-followup/whoisfreaks-spf-visible.txt` |
| NS public UI response | 2026-11-05 11:40:56.389 | `sources/email-domain-followup/whoisfreaks-ns-visible.txt` |
| Public MX screenshot | Captured approximately 11:41 UTC | `sources/email-domain-followup/whoisfreaks-mx-public.jpg` |
| SecurityTrails MX-history endpoint | Attempted 2026-11-05 11:38:13.903401 | `sources/email-domain-followup/securitytrails-mx.json`: HTTP 403; no records asserted |

Exact-date searches combining the domain with 2025-03-17 and 17 March 2025 did not produce an independent matching record. This limited negative search result is not evidence that the claimed observation never happened. No account was created, no subscription purchased, and no restricted result was bypassed. The remaining history is unavailable under the public access used here.

The response texts preserve the site’s actual labels and dates; the SHA-256 manifest in the source folder permits later comparison. Domain registration (19 May 1999), DNS observation (14 April 2025), alleged March 2025 email event and actual retrieval (5 November 2026) must remain separate timeline categories.

![Public historical MX response](sources/email-domain-followup/whoisfreaks-mx-public.jpg)