VirusTotal
20 / 92
“Sylvexor”
On 2026-10-09, Google Safe Browsing flagged sylvexortrade.com for social engineering, and a PageSpeed performance score of 100 was also recorded for the domain. The domain was registered through Dynadot Inc on 2026-07-17.
Google Safe Browsing identified sylvexortrade.com as a social engineering threat on 2026-10-09. VirusTotal, on the same date, reported 20 detections out of 92 scanners for the domain. OTX included sylvexortrade.com in one pulse on 2026-10-09. The PhishDestroy internal catalogue listed the domain as of 2026-10-09.
These records show that sylvexortrade.com was observed by several independent sources on 2026-10-09, each providing distinct types of information. The inclusion in OTX, the detection count from VirusTotal, and the Google Safe Browsing flag collectively highlight how the domain was evaluated from different perspectives. The PageSpeed score and registration through Dynadot Inc offer additional context for technical and administrative review.
Preserve the dated records from Google Safe Browsing, VirusTotal, OTX, and PhishDestroy for future reference regarding sylvexortrade.com. Compare these source observations over time to monitor any changes in the domain’s recorded status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
ns1.dyna-ns.netns2.dyna-ns.netparkmail.dynadot.compriority 0Location describes the IP network.
db7838e27dee07d474672642d770ca2834b596894d2027d9d6785b858644371dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of sylvexortrade.com · checked Oct 9, 2026
158.94.210.119. 13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20261009-F5EA52 Recipient: abuse@omegatech.sc Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive