The domain www.pi-network.org was observed on July 22, 2026 as an elevated‑risk brand‑impersonation site targeting Facebook. Registration data show the domain was created on February 20, 2025 and is registered through HOSTINGER operations, UAB, with authoritative nameservers ns1.dns-parking.com and ns2.dns-parking.com. DNS resolution points to IP address 88.223.84.10, which belongs to AS47583 Hostinger International Limited and is geolocated in the United States. No SSL certificate is presented for the host, and the domain is currently listed as offline.
The page title returned by the server is "Pi Blockchain, Community & Developer Platform | Pi Network," indicating that the site references the Pi cryptocurrency ecosystem rather than directly displaying Facebook branding. VirusTotal analysis recorded a single positive detection out of 95 scanned security vendors. Independent reputation services assign a Gridinsoft trust score of 0 out of 100, and the domain appears on one security blocklist, having been blocked by PhishDestroy.
The available intelligence classifies the activity as a crypto‑scam, but no additional payload or credential‑harvesting details have been disclosed. Defenders should continue to block the domain and its associated IP address at perimeter controls, monitor for re‑hosting attempts, and consider adding the host to internal threat‑intel feeds. Ongoing observation of related Hostinger‑hosted domains is advised, as the low trust score and single vendor flag suggest a nascent campaign that could evolve to incorporate more sophisticated phishing vectors.
Extracted from stored page analysis
Observed indicators
1 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-1919.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Feb 20, 2025 —Expires Feb 20, 2026
Time to First Unavailability257 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 24, 2025
DOM Analysisanalyzed Apr 24, 2026score 25/1004 brand signals
IoC Extractionscanned Aug 3, 20261 wallet · 1 Telegram IoCs
Submitted URLhttps://www.pi-network.org/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
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.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:12:10 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-13 22:18:28 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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-1919.invalid detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Feb 24, 2026
Time to First Unavailability
6170 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(LT)
