VirusTotal
3 / 89 engine detections
Відкрити звіт“Suspected Phishing | Cloudflare”
домен у блоклистах: chainguard.digital — Контент недоступний. Зведення доказів: VirusTotal 3/89 (Forcepoint ThreatSeeker, Kaspersky, VIPRE); 2 external…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
3 / 89 engine detections
Відкрити звітchecked — no detections recorded
Відкрити звітno community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
chainguard.digital is an impersonation phishing site that borrows a security-flavoured name to look like a trusted service to crypto users. MetaMask and SEAL both list it, which places its audience squarely among wallet holders. PhishDestroy first flagged it on 2026-09-19. The site has been offline since 2026-09-20 and was still unreachable when last checked on 2026-10-19.
Impersonation pages copy the look and wording of a legitimate brand so that visitors act as they would on the real service. Typical prompts ask the visitor to connect a wallet, sign a transaction, enter a recovery phrase or log in. Each of these hands the operator either direct control of the wallet or the credentials to reach it. The page title reads "Suspected Phishing | Cloudflare", which is Cloudflare's own warning interstitial, while our classification concerns the impersonating content behind it.
Only 3 of 89 VirusTotal engines flagged the domain on 2026-09-19: Forcepoint ThreatSeeker, Kaspersky and VIPRE. That low count means most generic security tools would have let it through. The stronger signal comes from the crypto-specific side, where it appears on the MetaMask and SEAL blocklists alongside PhishDestroy's own.
The domain was registered on 2026-08-30 through Global Domain Group LLC, and we caught it 20 days later. It went dark the day after detection, which fits a short-lived campaign domain rather than an established service. Traffic was routed through Cloudflare, Inc., with the address resolving to Canada, so the true origin server sits behind the proxy.
If you connected a wallet to this site, review your active token approvals with a revocation tool and cancel any you do not recognise. If you typed a seed phrase or private key, treat that wallet as compromised and move any remaining funds to a new wallet created on a clean device. If you entered a password, change it everywhere you reuse it and turn on app-based 2FA. Defenders should block chainguard.digital at DNS and proxy level and search their logs for visits around 2026-09-19 to 2026-09-20.
Last checked
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.
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.
Репутація Edge-IP не пов’язана з цим доменом.
andronicus.ns.cloudflare.comimani.ns.cloudflare.comLocation describes the IP network.
97720e3732179f3f002bcb2f28f4e45ec34b941b7d0e21bc2d51cabdd68f2973Saved 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 chainguard.digital · checked Sep 19, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
chainguard.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Доступний→Недоступно
Доступний
PD-20260919-4808DC
Page captured
View sourceNo threat flag
View source3/89 engine detections
View sourcechainguard.digital
View sourcePD-20260919-4808DC Recipient: abuse@globaldomaingroup.com Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
chainguard.digital)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.