The domain safesyncinvest.online was registered on December 4, 2025 and is currently active. It resolves to IP 64.29.17.65, an Amazon.com, Inc. address (AS16509) located in the United States. HTTP requests receive a 307 redirect and the site presents a valid Let’s Encrypt certificate (R13). Infrastructure analysis shows the domain is hosted on Vercel DNS (ns1.vercel-dns.com, ns2.vercel-dns.com) and employs the Smartsupp widget and HTTP Strict Transport Security. Threat intelligence indicates the page title "SafeSyncInvest - The Future of Crypto Investment" and classifies the operation as an investment scam. The domain is listed on a single security blocklist, has been referenced in one AlienVault OTX pulse, and was blocked by PhishDestroy. VirusTotal scans report three detections out of ninety‑five scanners, and Gridinsoft assigns a trust score of 0/100. Defenders should treat the domain as high‑risk, enforce network‑level blocking of both the domain and its resolving IP, and monitor for additional Vercel‑hosted domains exhibiting similar redirects or credential‑harvesting patterns. Continued observation of any changes to the SSL certificate, DNS records, or HTTP response codes is recommended to detect potential re‑use or shift in malicious activity.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:29:58 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:58 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.
技术 · 3 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
S
Smartsupp
Live chat
Live chat and visitor recording tool for customer support.
H
HSTS
安全
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of safesyncinvest.online· checked Mar 2, 2026
61
Needs Work
Performance
FCP
1.69s
First Contentful Paint
LCP
16.82s
Largest Contentful Paint
CLS
0.014
Cumulative Layout Shift
TBT
272ms
Total Blocking Time
SI
7.96s
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.
10 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(LT)
