Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
The domain flaress.network poses a high-risk phishing threat, potentially targeting users interested in blockchain technology under the guise of "Flare: The blockchain for data". The site has been identified as a generic phishing platform, designed to deceive users into divulging sensitive information. Although currently offline, the infrastructure employed by this domain suggests a sophisticated attempt to exploit blockchain enthusiasts.
Upon examination, flaress.network was registered through NameSilo, LLC, with its domain creation date recorded as May 14, 2026. This domain has been flagged by 18 out of 95 security vendors on VirusTotal, indicating a significant consensus among security experts regarding its malicious intent. The domain resolves to the IP address 37.49.229.75 and is blocked by prominent security entities including MetaMask, PhishDestroy, and SEAL. Furthermore, flaress.network appears on three distinct security blocklists, underscoring its high-risk status.
Users who may have visited flaress.network are advised to take immediate precautions. It is critical to change passwords associated with any accounts that may have been compromised. Additionally, users should monitor their financial accounts for any unauthorized transactions. Implementing two-factor authentication (2FA) on all sensitive accounts can provide an extra layer of security. Users should also consider running a full security scan on their devices to ensure no malware has been inadvertently installed. Remaining vigilant and informed about such threats is crucial in safeguarding personal and financial information.
Extracted from stored page analysis
Observed indicators
0 wallet · 10 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='flaress.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
DOM Analysisanalyzed 2026年6月11日score 80/1001 brand signal
IoC Extractionscanned 2026年8月1日0 wallet · 10 Telegram IoCs
Submitted URLhttps://flaress.network/
ICANN OVERSIGHT
认证和 RAA 背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-19 22:03:27 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-19 22:03:27 UTC → 2026-09-30 16:14:55 UTC · 2,466.19hmidpoint estimate ≈ 2026-08-10 07:09:11 UTC · precision very low · basis bounded
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.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Google PageSpeed Insights — mobile performance audit of flaress.network· checked Jun 26, 2026
60
Needs Work
Performance
FCP
1.8s
First Contentful Paint
LCP
15.58s
Largest Contentful Paint
CLS
0.219
Cumulative Layout Shift
TBT
148ms
Total Blocking Time
SI
3.96s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
VirusTotal Detections Update2026-06-26 01:49:32 UTC
15 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.
(US)
PhishDestroy Investigation
