Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Analysis of tnsr.foundation, created on 2025-11-20 and currently taken offline, reveals infrastructure consistent with a brand-impersonation campaign targeting the foundation brand. The domain is registered through NameSilo, LLC and uses Cloudflare’s authoritative name servers ligia.ns.cloudflare.com and steven.ns.cloudflare.com. DNS resolution points to IP address 104.21.46.123, which belongs to Cloudflare, Inc. (AS13335) and is geolocated in the United States. No TLS certificate is presented; HTTP requests return the page title “Just a moment…”, indicating that the site likely served a Cloudflare challenge page rather than bespoke content. The domain appears on a single security blocklist and has been actively blocked by the PhishDestroy feed.
VirusTotal scans show that 2 of 95 antivirus engines flagged the domain, suggesting at least limited malicious behavior detected by a minority of vendors. Gridinsoft assigns a trust score of 0 out of 100, reinforcing the low credibility assessment. The documented scam type is “Brand Impersonation”, and the threat actor explicitly claims to impersonate the foundation brand. While the offline status limits immediate exposure, the underlying hosting through a shared Cloudflare IP space implies that future replicas could be launched with minimal configuration changes. Defenders should continue to deny network traffic to 104.21.46.123, add tnsr.foundation to local blocklists, and monitor for new domains that resolve to the same Cloudflare IP range or reuse the same name-server pair.
Continuous observation of VirusTotal, PhishDestroy, and other threat-intel feeds is recommended to capture any resurgence of the campaign. Because the site does not present a valid SSL certificate, any attempt to establish HTTPS connections will fail, providing an additional barrier for automated retrieval.
RegistrationCreated Nov 20, 2025 (327d)—Expires Nov 20, 2026
Time to First Unavailability94 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedNov 20, 2025
DOM Analysisanalyzed Apr 11, 2026score 25/1001 brand signal
Submitted URLhttps://tnsr.foundation/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:11:37 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-04-21 22:27:10 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 22:27:10 UTC → 2026-09-30 16:14:55 UTC · 3,881.80hmidpoint estimate ≈ 2026-07-11 19:21:02 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
tnsr.foundation detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 23, 2026
Time to First Unavailability
2266 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · tnsr.foundation
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
PhishDestroy Investigation
