The domain www.bitfiz.net was registered on February 21, 2026 through Porkbun LLC and is currently offline. Infrastructure analysis shows the domain resolves to the IP address 216.198.79.65, which belongs to the Amazon.com, Inc. network (AS16509) and is geolocated in the United States. DNS resolution uses three Porkbun name servers (curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com). The site was served over HTTPS using a Let’s Encrypt R12 certificate and advertised HTTP Strict Transport Security (HSTS), indicating an attempt to present a legitimate‑looking encrypted session.
The page title returned by the server, "Bitfiz - Boost Your Decisions | Crypto Exchange," suggests a cryptocurrency‑related lure, but the actual page content has not been captured, so the visual or functional characteristics remain unknown. Security telemetry indicates the domain received a single positive detection out of 93 scanning engines on VirusTotal, and it appears on one public blocklist. PhishDestroy has also taken the domain offline, confirming that it was identified as a phishing resource. Reputation scoring from Gridinsoft assigned a trust score of 0 out of 100, reinforcing the malicious assessment.
The hosting platform identified as Vercel aligns with the rapid deployment model often used by threat actors. Defenders should add the domain and its associated IP address to outbound filtering rules, ensure DNS‑based blocklists include the observed nameservers, and monitor for any re‑registration attempts. Because the site is already offline, a sinkhole or redirect of traffic to a safe landing page can be employed to capture any lingering victim attempts. Continuous re‑scanning of the domain, especially if it reappears, is advised to capture any changes in payload or hosting infrastructure.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-51590.invalid', port=80): Max retries exceeded with url: / (Caused by N
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 DetectedJan 24, 2026
DOM Analysisanalyzed Jul 29, 2026score 56/1001 brand signal
Submitted URLhttps://www.bitfiz.net/
Case ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:10:59 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-03-15 23:05:12 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.
Technologies · 2 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
Security
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-51590.invalid· checked Mar 2, 2026
70
Needs Work
Performance
FCP
4.11s
First Contentful Paint
LCP
5.13s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
16ms
Total Blocking Time
SI
4.84s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 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-51590.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.
Mar 16, 2026
Time to First Unavailability
1202 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 matches1
Same favicon hash or the same page title as this host.
(US)
