Analysis of signalpointjs.online, observed as offline as of July 25 2026, indicates the domain is being used for a crypto‑focused phishing campaign. The site was registered on 26 February 2026 via NameCheap, Inc., and resolves to the Cloudflare address 172.67.196.5, which belongs to AS13335 in the United States. The domain appears on a single security blocklist and has been explicitly blocked by PhishDestroy. No SSL certificate is presented, and the authoritative name servers are craig.ns.cloudflare.com and princess.ns.cloudflare.com, confirming reliance on Cloudflare’s DNS infrastructure.
VirusTotal scans show that one of ninety‑three security vendors flagged the domain, reinforcing the suspicion of malicious intent. The page title retrieved from the live snapshot reads “Signalpointjs: Most Popular Online Crypto Casino Based on Blockchain,” and the campaign has been linked to the Gambler Scam phishing kit, a known template used to lure victims into fake cryptocurrency casino offers. The classification of the threat is a Crypto Scam, consistent with the title and kit association. While the offline status prevents direct interaction, the presence of the domain on a blocklist, the lack of TLS protection, and the vendor detection collectively substantiate a credible phishing risk.
Uncertainties remain regarding the exact payload delivered to victims, the extent of credential harvesting, and whether additional infrastructure (e.g., command‑and‑control servers) is associated with the same IP range. Defenders should immediately add signalpointjs.online to URL filtering and DNS sinkhole policies, block the associated IP 172.67.196.5 at the network perimeter, and monitor for any traffic to Cloudflare name servers that match the observed pattern. Continuous re‑scanning of the domain and its IP is recommended in case the site is re‑hosted, and any observed attempts to mimic the casino branding should be flagged for further forensic analysis.
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='signalpointjs.online', port=80): Max retries exceeded with url: / (Caused by NewConnection
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 26, 2026 (227d)—Expires Feb 17, 2027
Time to First Unavailability4 days
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 27, 2026
DOM Analysisanalyzed Jul 29, 2026score 56/1001 brand signal
Submitted URLhttps://signalpointjs.online/
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-11 01:10:01 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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
signalpointjs.online 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 2, 2026
Time to First Unavailability
93 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 →
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 · signalpointjs.online
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.
(US)
