The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank High number of suspicious websites on this server According to the SSL check, the certificate is not valid This website is (very) young. We tried to analyze the content of the site but failed This website appears to be hosted by a company with a bad reputation.
This website is safe according to DNSFilter
证据摘要
关键
VirusTotal
9/93
URLScan
Stored capture
The site flarechainnetwork.online, titled "My website," is a generic placeholder page, indicating no legitimate brand or service is presented. Based on low trust scores and blocklist presence, it poses a threat as a potential phishing or malware distribution domain, likely used for credential theft or system compromise.
Technical evidence: VirusTotal flagged 9/95 vendors, including ADMINUSLabs, ChainPatrol, and alphaMountain.ai. The domain is registered with NameCheap, Inc. (Registrar) and hosted on IP 198.54.125.47 (US, AS22612 Namecheap, Inc.). Created on 2025-09-12, it lacks SSL encryption. Nameservers are dns1.namecheaphosting.com and dns2.namecheaphosting.com.
Current status: The site is down/offline. Risk level is high, evidenced by 3 blocklists, GridinSoft trust 0/100, and ScamAdviser trust 29/100. Its recent creation, low trust, and detection by multiple vendors indicate a malicious domain.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='flarechainnetwork.online', port=80): Max retries exceeded with url: / (Caused by NewConnec
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.
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-03 10:24:21 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-03 10:24:21 UTC → 2026-09-30 16:14:55 UTC · 2,861.84hmidpoint estimate ≈ 2026-08-02 01:19:38 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.
技术 · 13 identified
W
WordPress
CMS
Open-source CMS powering over 40% of websites worldwide.
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.
12 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)
