PhishDestroy first observed motiondev.com.br on Oct 12, 2026. Current evidence score: 80/100 (critical).
One source contains a positive finding: VirusTotal. VirusTotal recorded 10 detections among 92 engines: ADMINUSLabs, alphaMountain.ai, Chong Lua Dao, Dr.Web, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Lionic, SOCRadar, Webroot on Oct 12, 2026 at 22:09 UTC. Additional recorded evidence: AlienVault OTX listed 32 community pulse references (not vendor detections) on Oct 12, 2026 at 22:09 UTC.
An access-restricted HTTP 403 response was recorded on Oct 12, 2026 at 22:00 UTC. Latest classified outcome: unknown; cause stale current evidence on Oct 12, 2026 at 19:38 UTC. The recorded creation date for the domain is Feb 28, 2026. At collection time, the hostname resolved to 216.198.79.1 on AS16509 (Amazon.com, Inc.). The recorded endpoint location is Atlanta, US. DOM analysis on Oct 12, 2026 at 22:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 1 visual capture from PhishDestroy; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YR1 as the certificate issuer with validity through Dec 8, 2026; checked Oct 12, 2026 at 22:02 UTC.
The source finding supports the recorded classification.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Last analyzed Previous stored snapshot: 10 detections
ADMINUSLabs
alphaMountain.ai
Chong Lua Dao
Dr.Web
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
Lionic
SOCRadar
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of motiondev.com.br· checked Oct 12, 2026
99
Good
Performance
FCP
0.9s
First Contentful Paint
LCP
2.26s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
7ms
Total Blocking Time
SI
1.8s
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-12 21:38:36 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 216.198.79.1.
威胁响应 Pipeline
发现
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
