VirusTotal
5 / 89 engine detections
Buka laporan“Gradient Dashboard”
Domain dalam daftar blokir: my.griedient.network — Terakhir diketahui aktif (HTTP 302). Ringkasan bukti: VirusTotal 5/89 (alphaMountain.ai, CRDF, Forcepoint…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
5 / 89 engine detections
Buka laporanno community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain, my.griedient.network, is currently active and resolves to the IPv4 address 162.244.92.2. The infrastructure is simple; DNS resolution returns a single A record pointing to that host, while the authoritative nameserver information is unavailable (NS_NOT_FOUND). The domain has been added to one public security blocklist and is actively blocked by the PhishDestroy service, indicating that at least one anti‑phishing platform has identified malicious use. A VirusTotal analysis was performed on 91 scanning engines, none of which reported a detection at the time of the scan; the absence of a flag does not imply benign intent, but it does provide a baseline for future comparison.
No additional intelligence such as Safe Browsing, OTX, registrar details, SSL certificate data, HTTP response codes, or page‑title information is present in the current feed. Given the limited observable surface, defenders should treat the domain as a potential phishing vector until further evidence is obtained. Recommendations include adding the domain and its resolved IP address (162.244.92.2) to outbound and inbound deny lists, ensuring that any email‑filtering solutions reference the blocklist entry, and monitoring network traffic for connections to the host. Continuous re‑scanning with multi‑vendor services is advised to capture any changes in detection status.
Organizations should also consider employing DNS‑sinkhole techniques for the domain and reviewing outbound DNS queries for similar sub‑domains that may share the same hosting infrastructure. Incident response teams should be prepared to quarantine any credential submissions that may be directed to this host, as the generic phishing classification suggests credential harvesting attempts. Ongoing intelligence gathering, including periodic WHOIS lookups and passive DNS monitoring, will help refine the risk profile as new data emerges.
Last checked
For the registrable domain griedient.network 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.
6b624ce7d0a73321fa94f9b3753dfefed751a73815b207ef9ec8f4ffef54c9bdwww.my.griedient.networkSaved 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.griedient.networkDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of my.griedient.network · checked Jul 29, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://my.griedient.network/X-Powered-By: PHP/7.4.33Content-Type: text/html; charset=UTF-8Content-Encoding: gzipServer: LiteSpeedKeep-Alivegzip37586text/html; charset=UTF-8Sat, 01 Aug 2026 03:32:38 GMTtimeout=5, max=100LiteSpeedAccept-EncodingPHP/7.4.33Values 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.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://my.griedient.network/cgi-sys/suspendedpage.cgi; server=LiteSpeed
my.griedient.network
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
live_content→redirected
http_redirect
redirected→live_content
content_served
Tidak diketahui→redirected
http_redirect
live_content→redirected
http_redirect
Tidak diketahui→live_content
content_served
redirected→live_content
content_served
Tidak diketahui→redirected
http_redirect
live_content→redirected
http_redirect
redirected→live_content
content_served
Tidak diketahui→redirected
http_redirect
Tidak diketahui→live_content
content_served
Tidak diketahui→redirected
http_redirect
live_content→redirected
http_redirect
redirected→live_content
content_served
Tidak diketahui→redirected
http_redirect
Tidak diketahui→redirected
http_redirect
Tidak diketahui→redirected
http_redirect
protected→redirected
http_redirect
Tidak diketahui→protected
captcha · challenge
Tidak diketahui→protected
captcha · challenge
Tidak diketahui→protected
captcha · challenge
Tidak diketahui→protected
captcha · challenge
Tidak diketahui→protected
captcha · challenge
Tidak diketahui→protected
captcha · challenge
protected
captcha · challenge
Dapat dijangkau
5/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcemy.griedient.network
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
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.griedient.network)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
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
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.