Security engines reporting a detection: 1. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Analysis of checker-billions.network, created on 25 February 2026 and currently taken offline, indicates a confirmed phishing operation. The site resolved to 188.114.97.3, an IP owned by Cloudflare (AS13335) located in the United States, and used Cloudflare's DNS infrastructure (melody.ns.cloudflare.com, plato.ns.cloudflare.com). No SSL certificate was presented, meaning the site did not support HTTPS. The page title returned by the server was "Billions Checker," suggesting a possible financial‑verification lure, though the exact content of the page has not been captured.
The domain appears on four independent security blocklists and is actively blocked by PhishDestroy, MetaMask, ScamSniffer, and SEAL, reinforcing the malicious classification. VirusTotal recorded a single positive detection out of 93 scanning engines, providing a minimal but corroborating signal. Registration was performed through PDR Ltd. d/b/a PublicDomainRegistry.com, a registrar commonly observed in malicious registrations. While the limited detection count and the absence of SSL could be interpreted as low technical sophistication, the convergence of blocklist listings, the dedicated blocking by multiple anti‑phishing services, and the presence of a financially‑oriented page title collectively substantiate the phishing verdict.
Uncertainty remains regarding the exact payload, target audience, and any credential‑harvesting mechanisms, as no page capture is available. Defenders should continue to block the domain at network perimeters, monitor the associated IP for any re‑hosting activity, and add the domain to internal threat intelligence feeds. Periodic re‑query of VirusTotal and blocklist sources is recommended to capture any future changes in detection status.
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='checker-billions.network', port=80): Max retries exceeded with url: / (Caused by NewConnec
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 25, 2026 (231d)—Expires Feb 24, 2027
Time to First Unavailability31h
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 DetectedFeb 25, 2026
DOM Analysisanalyzed Jul 29, 2026score 61/100
Submitted URLhttp://checker-billions.network/
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:09:14 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
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-02-27 02:03:41 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: Gridinsoft.
Domain Status Transition2026-02-27 02:03:41 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
checker-billions.network 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 27, 2026
Time to First Unavailability
31 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.
5 evidence signal groups linked1 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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · checker-billions.network
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.
(IN)
