VirusTotal
11 / 91 engine detections
Відкрити звіткрадіжка облікових даних: velomenius.digital — Контент недоступний. Зведення доказів: VirusTotal 11/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
11 / 91 engine detections
Відкрити звітDBL_SPAM
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
The domain velomenius.digital was registered on 19 June 2026 through Global Domain Group LLC and resolved to the IPv4 address 193.187.110.3. The authoritative name servers listed are a.dnspod.com, b.dnspod.com and c.dnspod.com, indicating use of the DNSPod hosting platform. VirusTotal scans show that 2 of 91 security vendors flagged the domain, confirming that at least a minority of detection engines consider it malicious.
The domain is currently listed on a single external blocklist and is actively blocked by the PhishDestroy mitigation service, suggesting that threat‑intelligence feeds have identified it as a phishing‑related resource. No additional metadata such as SSL certificate details, HTTP response codes, page titles, or Safe Browsing verdicts are available in the supplied intelligence, leaving the exact content of the site unverified. The classification as a generic phishing campaign derives from the combination of the short registration age, the presence on a phishing‑specific blocklist, and the modest detection rate on VirusTotal.
Defenders should continue to deny any outbound connections to 193.187.110.3, enforce DNS filtering for velomenius.digital, and monitor the three DNSPod name servers for any rapid changes that could indicate a fast‑flux or domain‑generation technique. Because the domain remains active, security teams should add it to internal blocklists, correlate any user‑reported credential submissions with this indicator, and regularly review updates from PhishDestroy and other threat‑feed providers for potential escalation.
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.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
95fe9eebca8ce40fe5e9dac409505595ef8709f58a52b0d94b6d2193458b1cb6Saved 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 velomenius.digital · checked Jul 31, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://velomenius.digital/Content-Type: text/html; charset=utf-8Cache-Control: no-storeContent-Encoding: gzipclearno-storegzip687583text/html; charset=utf-8Fri, 31 Jul 2026 18:02:48 GMTAccept-EncodingcaptchaValues retained by the collector; long values may be shortened during collection.
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.
velomenius.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Доступний→Недоступно
Доступний
11/91 engine detections
View sourcePD-20260731-979FC6
No threat flag
View sourcePage captured
View sourcevelomenius.digital
View sourcePD-20260731-979FC6 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 ↗
velomenius.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.