Analysis of xrpmints.online, registered on February 21, 2026 through Network Solutions LLC, shows an active infrastructure used for a crypto‑draining scam. The domain resolves to IP 208.91.197.27, which is assigned to Confluence Networks Inc (AS40034) in the United States. Hosting is provided via Google Cloud, with Nginx and OpenResty serving the site behind Google Cloud CDN. The site presents a valid SSL certificate issued by ZeroSSL ECC Domain Secure Site CA, and HTTP requests return a 200 status code, indicating a fully operational web service.
Reputation services flag the domain as malicious: it appears on one security blocklist and is specifically blocked by PhishDestroy. VirusTotal scans report that 2 of 93 security vendors have flagged the domain, reinforcing the suspicion. Independent trust scoring from Gridinsoft assigns a score of 0 out of 100, the lowest possible rating. The page title returned by the server is simply "xrpmints.online," providing no additional context about the content.
While the exact phishing landing page has not been captured, the aggregate evidence—blocklist presence, vendor detections, low trust score, and the classification as a crypto scam—suggests the domain is being leveraged to lure victims into transferring cryptocurrency to attacker‑controlled wallets. Defenders should block network traffic to 208.91.197.27, add xrpmints.online to internal blacklists, and monitor for any outbound connections from internal hosts to this domain. Security teams should also update URL filtering rules in web gateways and endpoint protection solutions to reflect the current detections. Continuous monitoring of VirusTotal and other threat‑intel feeds is recommended to capture any new vendor assessments or changes in the domain's reputation.
Detection-evasion evidence
Cloaking confirmed: scanners and visitors see different content
ObservedDifferent content was served to scanners and to visitors
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
Stored cloaking flag
Observed
Cloaking type
content_divergence
Cloaking score
2/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='xrpmints.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='xrpmints.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
checked Oct 11, 2026
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 26, 2026
DOM Analysisanalyzed Jul 9, 2026score 93/100
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:13:00 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-11 22:46:14 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-11 22:46:14 UTC → 2026-09-30 16:14:55 UTC · 1,193.48hmidpoint estimate ≈ 2026-09-05 19:30:34 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.
Technologies · 4 identified
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
Google Cloud
PaaSIaaS
Suite of cloud computing services running on Google infrastructure.
O
OpenResty
Web servers
Web platform based on Nginx with LuaJIT for scalable web apps.
Google Cloud CDN
CDN
Content delivery network built on Google global edge infrastructure.
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
Chong Lua Dao
Fortinet
Gridinsoft
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
xrpmints.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.
Sep 10, 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 · xrpmints.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)
