Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
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.
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.
Accreditation is a contract, not a safety certification.
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.
Certificate fingerprint6b624ce7d0a73321fa94f9b3753dfefed751a73815b207ef9ec8f4ffef54c9bdCertificate names · 1 SANs
www.my.griedient.network
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Active
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-12 02:45:33 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-07-18 05:14:06 UTCchecked 2026-08-07 04:42:26 UTC
Observed timelinelast reachable: 2026-10-12 02:45:33 UTClast content: 2026-10-12 02:45:33 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 3 identified
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
Google PageSpeed Insights — mobile performance audit of my.griedient.network· checked Jul 29, 2026
100
Good
Performance
FCP
1.19s
First Contentful Paint
LCP
1.2s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.95s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://my.griedient.network/
Gradient Dashboard
响应 HTTP 200
HTML body 80.7 KB
Compressed 35.1 KB
Links 0 internal · 1 external
Selected response headers
X-Powered-By: PHP/7.4.33
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Server: LiteSpeed
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Saved response-header values · 9
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
37586
Content-Type
text/html; charset=UTF-8
Date
Sat, 01 Aug 2026 03:32:38 GMT
Keep-Alive
timeout=5, max=100
Server
LiteSpeed
Vary
Accept-Encoding
X-Powered-By
PHP/7.4.33
Values retained by the collector; long values may be shortened during collection.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-07-29 06:09:52 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.244.92.2.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(RU)
PhishDestroy Investigation
