VirusTotal
1 / 92 engine detections
Open reportfire-fly.network is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (93/100). Registrar: NiceNIC. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 1/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Firefly ✨ Everything App for Web3 Natives”
1 / 92 engine detections
Open reportSuspicious
Open reportDBL_SPAM
2 community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The prior PhishDestroy AI assessment noted that the recorded page title “Firefly ✨ Everything App for Web3 Natives” is generic and does not demonstrate malicious intent. PhishDestroy added fire-fly.network to its internal blocklist on 2026-10-23 after an admin report. An HTTP 200 response was recorded on the same date, confirming the site was reachable at that time.
The listing does not confirm any particular fraud technique; newly registered domains that use vague Web3 branding are often leveraged in phishing or credential‑harvesting campaigns. Such sites may attempt to trick users into submitting private keys, approving wallet transactions, or downloading malicious software, but no such behavior was observed on this page.
VirusTotal scanned the domain on 2026-10-23 and reported one suspicious detection (Fortinet labeling it as spam) with no malicious detections out of 92 engines. Google Safe Browsing checked on 2026-10-23 and did not flag the site. External blocklists MetaMask and SEAL listed the domain on 2026-10-23, and Spamhaus DBL categorized it as spam on the same date. OTX recorded two pulses mentioning fire-fly.network on 2026-10-23. URLScan captured the site on 2026-10-23, showing a 307 redirect to HTTPS and an engine‑generated malicious score of 91, though its overall verdict was not malicious. PhishDestroy’s internal list also contains the domain as of 2026-10-23.
The domain was registered on 2026-10-15 through NICENIC INTERNATIONAL GROUP CO., LIMITED, making it six days old at first observation. Hosting is provided by Cloudflare, with recorded A records 172.67.150.70 and 104.21.96.22 and AAAA records 2606:4700:3030::6815:6016 and 2606:4700:3030::ac43:9646. The TLS certificate issued by Let’s Encrypt is valid until 2027-01-13, and DNSSEC was not enabled.
Visitors should avoid entering any credentials, private keys, or approving wallet transactions on this site; if such data was submitted, change passwords immediately. Organizations should block fire-fly.network at the network perimeter and monitor logs for connections to its recorded IP addresses. Continue to monitor the domain for any changes, as the current assessment is based on reputation and blocklist matches, not on observed malicious activity.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a16690-cd0b-74aa-9206-f9e7df75398b |
|---|---|
| Final url | https://fire-fly.network/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://fire-fly.network/",
"from": "http://fire-fly.network/",
"status": 307
}
] |
| Ip | 104.21.96.22 |
| Contacted domains | [
"static.cloudflareinsights.com"
] |
| Contacted IP addresses | [
"104.16.79.73",
"104.21.96.22"
] |
| Asns | [
"13335"
] |
| Document hash | 1eb42de9daa1d06138707ac5287c1b1f2a0d923da234ffe235435b2a18750077 |
| Script hashes | [
"d6875aabec43b4c2f1d835b16fb0dc479de11dcb6c5a71f862b61f9e0d6d1c50"
] |
| Globals | [
"__cfBeacon"
] |
| Tls | {
"san": [
"*.fire-fly.network",
"fire-fly.network"
],
"cipher": "AES_128_GCM",
"issuer": "YE2",
"subject": "fire-fly.network",
"protocol": "QUIC",
"valid_to": "2027-01-13T17:47:09Z",
"valid_from": "2026-10-15T17:47:10Z"
} |
| Domain age days | 6 |
| Apex age days | 6 |
| Tls age days | 7 |
| Tls valid days | 89 |
| Requests | 11 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 91,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html",
"strict-transport-security": "max-age=63072000; includeSubDomains; preload",
"content-security-policy": "frame-ancestors http: https:",
"x-content-type-options": "nosniff"
} |
Observed: · Retrieved:
| Uuid | 3d5e68d0-3bcb-42c3-83a9-9471790bcdc8 |
|---|---|
| Final url | https://fire-fly.network/ |
| Status | 200 |
| History | [
{
"url": "https://fire-fly.network/",
"status": 200
}
] |
| DOM structure hash | 94632c2c397ab5d6ffa1c5bf0b45d9271f61c3f1ff442643ea120abf99c6163a |
| Document hash | 1eb42de9daa1d06138707ac5287c1b1f2a0d923da234ffe235435b2a18750077 |
| Domain risks | [
"Newly Seen Domains",
"Security Risks",
"New Domains"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "fire-fly.network",
"type": "A",
"value": "104.21.96.22"
},
{
"name": "fire-fly.network",
"type": "A",
"value": "172.67.150.70"
},
{
"name": "fire-fly.network",
"type": "AAAA",
"value": "2606:4700:3030::6815:6016"
},
{
"name": "fire-fly.network",
"type": "AAAA",
"value": "2606:4700:3030::ac43:9646"
}
] |
| Dnssec valid | false |
| Ip | 104.21.96.22 |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 51,
"malicious": 0,
"suspicious": 1,
"undetected": 40
} |
|---|---|
| Vendor labels | {
"Fortinet": "spam"
} |
| Reputation | 0 |
| First seen | 2026-10-17T06:25:15Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "chip.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.96.22"
},
{
"ttl": 21600,
"type": "NS",
"value": "olga.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3030::6815:6016"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.150.70"
},
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "chip.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3030::ac43:9646"
}
] |
| Dns at | 2026-10-23T02:48:16Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.fire-fly.network",
"fire-fly.network"
],
"issuer": "Let's Encrypt / YE2",
"serial": "6dfbac716943a840e260b1fa6d1eb9d4af7",
"sha256": "b12d26755c10f438169555f7b6f9a60b91c5b75d8c064f990589973d19ce0df4",
"subject": "fire-fly.network",
"valid_to": "2027-01-13T17:47:09Z",
"valid_from": "2026-10-15T17:47:10Z"
} |
| Registry data | {
"status": [
"client delete prohibited",
"client transfer prohibited"
],
"events": {
"expiration": "2027-10-15T16:00:00Z",
"registration": "2026-10-15T16:00:00Z",
"registrar expiration": "2027-10-15T16:00:00Z",
"last update of RDAP database": "2026-10-15T16:00:00Z"
},
"registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
"registrar_iana_id": "3765"
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "fire-fly.network"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Web archive observations | {
"last": "2026-10-23T02:25:29Z",
"first": "2026-10-16T03:04:52Z",
"changes": 1,
"days_archived": 2,
"scans_per_day": 0.14,
"avg_page_bytes": 11353
} |
| Page title and metadata | {
"ogUrl": "https://firefly.social/signup",
"title": "Firefly ✨ Everything App for Web3 Natives",
"ogImage": "https://firefly.social/image/og.png",
"ogTitle": "Firefly ✨ Everything App for Web3 Natives",
"ogSiteName": "Firefly ✨ Everything App for Web3 Natives",
"themeColor": "#030303",
"description": "Firefly is a social app for exploring what's happening onchain.",
"twitterCard": "summary_large_image",
"canonicalUrl": "https://firefly.social/signup",
"ogDescription": "Firefly is a social app for exploring what's happening onchain.",
"twitterCreator": "@thefireflyapp"
} |
| Trackers | {
"requests": 8
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 1,
"tls": 38,
"wait": 129,
"connect": 1062,
"download": 1
},
"response_ms": 1231
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_256_GCM_SHA384",
"protocol": "TLSv1.3",
"versions": [
"TLSv1",
"TLSv1.1",
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
80,
443,
8080
]
} |
| Carbon | {
"bytes": 62281,
"co2_grams": 0.0023,
"cleaner_than": 32
} |
| Dns server | {
"ns": [
{
"ip": "173.245.58.137",
"host": "olga.ns.cloudflare.com"
},
{
"ip": "173.245.59.84",
"host": "chip.ns.cloudflare.com"
}
],
"zone": "fire-fly.network"
} |
| Location | {
"ip": "2606:4700:3030::ac43:9646",
"asn": "13335",
"org": "Cloudflare, Inc.",
"city": "Toronto",
"country": "CA"
} |
| Ssl | {
"issuer": "Let's Encrypt / YE2",
"subject": "fire-fly.network"
} |
| DNS records | {
"A": [
"104.21.96.22",
"172.67.150.70"
],
"NS": [
"olga.ns.cloudflare.com",
"chip.ns.cloudflare.com"
],
"SOA": "{\"nsname\": \"chip.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2417865134, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
"AAAA": [
"2606:4700:3030::ac43:9646",
"2606:4700:3030::6815:6016"
]
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"header": "max-age=63072000; includeSubDomains; preload",
"message": "Site is compatible with the HSTS preload list!",
"compatible": true
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": false,
"xXSSProtection": "1; mode=block",
"permissionsPolicy": false,
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": "frame-ancestors http: https:",
"strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Firewall | {
"waf": "Cloudflare",
"has_waf": true
} |
| Get ip | {
"ip": "2606:4700:3030::6815:6016",
"family": 6
} |
| Redirects | {
"chain": [
"https://fire-fly.network"
]
} |
| HTTP headers | {
"headers": {
"server": "cloudflare",
"content-type": "text/html",
"strict-transport-security": "max-age=63072000; includeSubDomains; preload",
"content-security-policy": "frame-ancestors http: https:",
"x-content-type-options": "nosniff"
}
} |
No. PhishDestroy classifies fire-fly.network as a phishing page (risk: critical, 93/100); it was first detected on 2026-10-23. VirusTotal: 1/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on fire-fly.network. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Last checked
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.
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.
Edge-IP reputation is not attributed to this domain.
chip.ns.cloudflare.comolga.ns.cloudflare.comLocation describes the IP network.
b12d26755c10f438169555f7b6f9a60b91c5b75d8c064f990589973d19ce0df4*.fire-fly.networkfire-fly.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 fire-fly.network · checked Oct 23, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://fire-fly.network/https://fire-fly.network/Content-Type: text/htmlServer: cloudflareCF-Cache-Status: DYNAMICContent-Encoding: gzipsummary_large_imageh3=":443"; ma=86400defaultDYNAMICa4ed48c85d535e64-EWRkeep-alivegzipframe-ancestors http: https:text/htmlFri, 23 Oct 2026 02:24:14 GMTThu, 15 Oct 2026 17:39:26 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=jDJkDIMWlS987i0TU1qDknWkpE2VD%2FPTdKue5GVbskp5VovkXZRmDFJJfTw4PqE%2F4GGvgJ3XRu4Ck%2BcJ3JX8t4ORxfhsKRSCBRPfRP1KbcrdQJI6RU%2F5LLiWkwSsjeUp0z3n"}]cloudflarecfCacheStatus;desc="DYNAMIC"max-age=63072000; includeSubDomains; preloadchunkedaccept-encodingnosniff1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
2 community references
View sourceNo threat flag
View source1/92 engine detections
View sourcefire-fly.network
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
fire-fly.network
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fire-fly.network)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.