PhishDestroy added fuzzy-credit.com to its blocklist on 2026-10-27 after VirusTotal reported 14 malicious detections. The page fetch performed on that date returned HTTP 403. An earlier urlscan capture from 2026-07-02 showed the site reachable over HTTPS with HTTP 200. Google Safe Browsing checked on 2026-10-27 did not flag the domain.
诈骗手法解析
The listing reflects multiple anti-malware detections of phishing or malicious content, a category that typically aims to steal credentials or deliver unwanted software. No specific malicious payload or credential-harvesting form was observed on the captured page, so the exact technique cannot be confirmed.
证据
VirusTotal analysis on 2026-10-20 (retrieved 2026-10-27) recorded 14 malicious and 3 suspicious detections from 92 engines, including BitDefender, Fortinet and Kaspersky. Google Safe Browsing on 2026-10-27 reported no flag. Urlscan.io captured the site on 2026-07-02 and its engine score marked it malicious (score 93) despite an overall clean verdict. OTX listed three pulses referencing the domain, and PhishDestroy’s internal blocklist marks it as malicious while external blocklists showed no entries on the check date. Cloudflare Radar also flagged the domain as malware-related on 2026-10-27.
基础设施
The domain was registered on 2025-12-26 through Porkbun LLC. A urlscan capture on 2026-07-02 recorded the apex resolving to 104.21.15.194 and 172.67.163.205. The certificate check found a Google Trust Services certificate valid from 2026-08-29 to 2026-11-28. DNSSEC was not enabled and the authoritative nameservers were journey.ns.cloudflare.com and rudy.ns.cloudflare.com.
What to do
Visitors should avoid entering any credentials or downloading files from fuzzy-credit.com; if credentials were submitted, change them immediately and monitor associated accounts. Defenders can block the domain and review logs for any connections, applying policy to this exact address.
PhishDestroy lists fuzzy-credit.com after 14 security vendors flagged it as malicious, while Google Safe Browsing returned no flag on 2026-10-27.
AI摘要
Overview PhishDestroy added fuzzy-credit.com to its blocklist on 2026-10-27 after VirusTotal reported 14 malicious detections. The page fetch performed on that date returned HTTP 403. An earlier urlscan capture from 2026-07-02 showed the site reachable over HTTPS with HTTP 200. Google Safe Browsing checked on 2026-10-27 did not flag the domain. How the scam works The listing reflects multiple anti-malware detections of phishing or malicious content, a category that typically aims to steal credentials or deliver unwanted software. No specific malicious payload or credential-harvesting form was observed on the captured page, so the exact technique cannot be confirmed. Evidence VirusTotal analysis on 2026-10-20 (retrieved 2026-10-27) recorded 14 malicious and 3 suspicious detections from 92 engines, including BitDefender, Fortinet and Kaspersky. Google Safe Browsing on 2026-10-27 reported no flag. Urlscan.io captured the site on 2026-07-02 and its engine score marked it malicious (score 93) despite an overall clean verdict. OTX listed three pulses referencing the domain, and PhishDestroy’s internal blocklist marks it as malicious while external blocklists showed no entries on the check date. Cloudflare Radar also flagged the domain as malware-related on 2026-10-27. Infrastructure The domain was registered on 2025-12-26 through Porkbun LLC. A urlscan capture on 2026-07-02 recorded the apex resolving to 104.21.15.194 and 172.67.163.205. The certificate check found a Google Trust Services certificate valid from 2026-08-29 to 2026-11-28. DNSSEC was not enabled and the authoritative nameservers were journey.ns.cloudflare.com and rudy.ns.cloudflare.com. What to do Visitors should avoid entering any credentials or downloading files from fuzzy-credit.com; if credentials were submitted, change them immediately and monitor associated accounts. Defenders can block the domain and review logs for any connections, applying policy to this exact address. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/019f2020-550d-74bf-b8ec-4002c47d1833/ Cloudflare Radar report: https://radar.cloudflare.com/scan/8ca99100-c84e-4c41-a29d-c104e6847039 Stored capture screenshot: https://urlscan.io/screenshots/019f2020-550d-74bf-b8ec-4002c47d1833.png Cloudflare Radar screenshot (2026-10-27T19:58:22Z): https://screenshots.phishdestroy.io/cf/8ca99100-c84e-4c41-a29d-c104e6847039.png URLScan screenshot (2025-12-26T02:04:18Z): https://screenshots.phishdestroy.io/us/019b5866-32d9-71ce-b400-e0f0927695df.png URLScan capture report: https://urlscan.io/result/019b5866-32d9-71ce-b400-e0f0927695df/ URLScan screenshot (2026-05-19T18:45:46Z): https://screenshots.phishdestroy.io/us/019e418e-d599-73b5-b779-9310c425be0a.png URLScan capture report: https://urlscan.io/result/019e418e-d599-73b5-b779-9310c425be0a/ URLScan screenshot (2026-05-20T08:40:27Z): https://screenshots.phishdestroy.io/us/019e448b-006a-71e9-8b22-3f8f26460e6c.png URLScan capture report: https://urlscan.io/result/019e448b-006a-71e9-8b22-3f8f26460e6c/ URLScan screenshot (2026-10-27T19:46:49Z): https://screenshots.phishdestroy.io/us/01a17ee6-0633-7028-be95-1475974caa70.png URLScan capture report: https://urlscan.io/result/01a17ee6-0633-7028-be95-1475974caa70/ VirusTotal report: https://www.virustotal.com/gui/domain/fuzzy-credit.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=fuzzy-credit.com Archived copy: https://web.archive.org/web/20261027194528/https://fuzzy-credit.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
证据层Availability: Content servingContent: Content served at rootDNS: Resolved
最新的 HTTP 观察结果内容在线提供普通 HTTP 内容90%2026-11-22 11:16 UTC
RDAP注册
观测时间线last reachable: 2026-11-22 11:16 UTClast content: 2026-11-22 11:16 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.