VirusTotal
12 / 89 engine detections
Відкрити звіт“Gradient Network”
фішинг: my.gradient.directory — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 12/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
12 / 89 engine detections
Відкрити звітDBL_PHISH
no community references
Відкрити звітprovider verdict: clean
Відкрити звіт69/100
80/100
Відкрити звіт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
Analysis of the domain my.gradient.directory indicates that it is currently active and associated with a generic phishing operation. The domain resolves to the IPv4 address 162.244.92.2, providing a single point of contact for the malicious infrastructure. Independent threat‑intel feeds have flagged the host: PhishDestroy and ScamSniffer list it, and it appears on two additional security blocklists, confirming that multiple security vendors have observed abusive activity tied to the domain. A VirusTotal submission routed the domain to 91 antivirus and sandbox engines; none reported a detection at the time of analysis.
While the lack of detections may reflect a low‑profile payload or evasion techniques, it does not constitute evidence of safety. No publicly disclosed Safe Browsing, Open Threat Exchange (OTX), registrar, TLS certificate, HTTP status code, page title, or trust‑score data is available in the current intelligence set, leaving many infrastructure attributes unknown. The risk level is marked as “under investigation,” and the status remains active, suggesting continued operation. Defenders should therefore treat any email, URL, or login prompt that references my.gradient.directory as potentially malicious.
Recommended mitigations include adding the domain and its resolved IP address (162.244.92.2) to network deny lists, enforcing DNS‑sinkhole policies, and monitoring outbound connections for attempts to reach the host. Continuous re‑evaluation is advised: periodic rescans with VirusTotal or alternative sandbox platforms, correlation with newly observed phishing campaigns, and updating of blocklist entries as fresh indicators emerge. Until forensic analysis provides a definitive attribution or confirms cessation of activity, the domain should be regarded as hostile.
Last checked
For the registrable domain gradient.directory behind this subdomain, 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.
ns4.private-nameserver.netLocation describes the IP network.
f806da786b987029331812aa1de2b7f7fc76d8d9330d597da4374cd60b30111egradient.directory.ethdenvers.comwhm.gradient.directorywww.gradient.directory.ethdenvers.comwww.my.gradient.directorySaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.my.gradient.directoryDomain recordThe original observation time is not recorded for these hostnames.
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.
alive_content: raw=ok; http=200; via=https_proxy; server=openresty/1.31.1.1
my.gradient.directory
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
redirected→live_content
content_served
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
live_content→redirected
http_redirect
redirected→live_content
content_served
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
redirected→live_content
content_served
Невідомо→redirected
http_redirect
live_content→redirected
http_redirect
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
live_content
content_served
Доступний
12/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcemy.gradient.directory
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
my.gradient.directory)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.