The domain mx-strendus.com was included on both the MetaMask and SEAL blocklists as of 2026-10-07, reflecting its status with these external monitoring sources. Additionally, a PageSpeed performance score of 89 was recorded for the domain on the same date, indicating a relatively efficient web response at that time.
Recorded Evidence
On 2026-10-07, mx-strendus.com appeared on the MetaMask and SEAL blocklists. VirusTotal checked the domain on this date, reporting zero detections out of 92 scanners. OTX recorded four pulses for this domain on 2026-10-07. The domain was registered with Dynadot Inc on 2026-02-26. PhishDestroy included mx-strendus.com in its internal listing.
Interpretation
These records show that mx-strendus.com was noted by several monitoring and security sources, including MetaMask, SEAL, OTX, and PhishDestroy. VirusTotal did not report any detections during its scan, and a PageSpeed score was documented. The presence on multiple blocklists and internal listings highlights the domain's visibility in various security and performance monitoring contexts.
Recommended Actions
It is advisable to review mx-strendus.com based on its inclusion in the MetaMask and SEAL blocklists, as well as its listing in PhishDestroy records. Preserve the VirusTotal scan results and OTX pulse records for comparison with future observations. Monitoring these source records over time can help track any changes in the domain's recorded status.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-07 08:10:51 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-07 08:10:51 UTC
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.
Google PageSpeed Insights — mobile performance audit of mx-strendus.com· checked Oct 7, 2026
89
Needs Work
Performance
FCP
2.33s
First Contentful Paint
LCP
3.2s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.73s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Threat First Observed2026-10-07 08:10:51 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
mx-strendus.com 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.
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 7, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 7, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
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.
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 · mx-strendus.com
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)
