fracons.com was first observed on 2026-10-13, with a recorded entry in the CryptoFirewall blocklist on that date. The domain also contains a listing in PhishDestroy, offering additional evidence for analysis.
Recorded Evidence
VirusTotal checked fracons.com on 2026-10-12, documenting 14 detections out of 92 scanners. OTX reviewed the domain on 2026-10-13 and found 12 pulses. The CryptoFirewall blocklist recorded an entry for the domain on 2026-10-13. Registration records show fracons.com was registered with NAMECHEAP INC on 2026-08-26.
Interpretation
PhishDestroy contains a listing for fracons.com, which documents its presence in an internal database. VirusTotal provides a technical measurement of detections from multiple scanners, capturing how the domain was analyzed across a broad range of security tools. The evidence from these sources covers a timeline from registration to blocklist entries, offering context for the domain's recorded security profile.
Recommended Actions
For fracons.com, it is advisable to preserve the VirusTotal, OTX, and CryptoFirewall blocklist records for ongoing comparison. Future checks should reference these source records to monitor for any new or updated observations. Keeping a record of these dated entries will support continued review of the domain's evidence profile.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 01:00:33 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:00:33 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.
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:43:22 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 192.64.119.40.
威胁响应 Pipeline
发现
Analysis
Monitoring
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.
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.
(SE)
