The domain mcc-account-sync.com was recorded with a CryptoFirewall blocklist entry as of 2026-10-13, providing a dated external observation. Additionally, this domain was observed with a PageSpeed performance score of 80 on the same date, offering a technical measurement of its web performance.
Recorded Evidence
On 2026-10-13, mcc-account-sync.com appeared on the CryptoFirewall external blocklist. OTX recorded six pulses for this domain on the same date. VirusTotal, as of 2026-10-10, documented 17 detections out of 92 total scanners. The domain was registered through Name.com, Inc. on 2026-08-12. A PageSpeed check on 2026-10-13 measured its performance score as 80. PhishDestroy internally listed this domain as of 2026-10-13.
Interpretation
The PhishDestroy internal listing contains a record that tracks the domain's appearance in internal monitoring systems. VirusTotal provides a measurement of how many security scanners detected the domain, which can be compared to other sources for a broader context. The presence of multiple source records across different dates and platforms allows for a multi-faceted review of the domain's recorded network and security status.
Recommended Actions
For mcc-account-sync.com, preserve the CryptoFirewall blocklist entry and the VirusTotal detection record for ongoing reference. Compare these records with the OTX pulse count and the PhishDestroy internal listing to monitor changes or new observations. Retain the PageSpeed performance measurement for technical context in future assessments.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-13 10:00:14 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:00:14 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.
使用技術 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of mcc-account-sync.com· checked Oct 13, 2026
80
Needs Work
Performance
FCP
3.22s
First Contentful Paint
LCP
4.18s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.22s
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 23:52:41 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 216.198.79.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
(US)
