VirusTotal
5 / 89
“Gradient Dashboard”
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
LiteSpeedLocal archived 2026-08-01 05:32:39 UTCScanner note: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://my.griedient.network/cgi-sys/suspendedpage.cgi; server=LiteSpeed
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.
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.
162.244.92.2. 10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive