Skip to security report
claim-xrpl.org favicon
Domain security and threat intelligence

claim-xrpl.org

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The site claim-xrpl.org uses Xaman branding to present an XRP Ledger notice about evolving keys and asks visitors to click continue. Anyone who followed prompts on this page should immediately review wallet permissions and disconnect any linked sessions.

Page title: “Your keys, evolving. | Xaman”

More about the sources
Recorded security signals

Stored VirusTotal result: 3/92 engines flagged. Malicious: 2. Suspicious: 1. Analysis time (as stored): 2026-11-21 02:16 UTC. Retrieved (as stored): 2026-11-21 18:14 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

VirusTotal detections: 3/92 Stored blocklist matches: 2 Young domain: 3 days old
Registrar
GermanyKey-Systems
Resolved IP
Canada188.114.96.3CloudFlare, Inc. · CDN
Registered
2026-11-19
First seen by PhishDestroy
2026-11-21
Page captures
open gallery
Domain age
registered 2026-11-19 according to WHOIS
2026-11-21 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded claim-xrpl.org on 2026-11-21. Stored VirusTotal result: 3/92 engines flagged. Malicious: 2. Suspicious: 1. Analysis time (as stored): 2026-11-21 02:16 UTC. Retrieved (as stored): 2026-11-21 18:14 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 76/100). Registrar: Key-Systems. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
3 / 92
Blocklist matches
2 external + PhishDestroy list
Hosting
Canada188.114.96.3CloudFlare, Inc. · CDN
Registrar
GermanyKey-Systems
Registered
2026-11-19
Page captures
2

URLScan capture · 2026-11-21 17:40 UTC · SHA-256 2d1a6956…ae04515

PhishDestroy analysis, reviewed version

Xaman branding and XRP Ledger page layout

The page at claim-xrpl.org displays a clean, minimalist interface centered around Xaman and XRP Ledger branding. At the top, it features the text "Xaman" accompanied by a blue dot and a small "XRPL" badge. A white card in the center holds the prominent headline "Your keys, evolving." Below this, secondary text reads, "We're preparing the next Xaman experience for the XRP Ledger. Check back soon." A bright blue button labeled "Continue" sits centrally inside the card, while the bottom of the page displays a copyright notice reading "© 2026 Xaman." The overall layout mimics a maintenance or preparation portal for the Xaman wallet ecosystem, inviting users to click through the primary button.

Registration timeline and independent vendor detections

Because it was registered on 19 Nov 2026, 2 days before it was first reported, the timeline sharply contrasts with the polished appearance of an established ecosystem update. Furthermore, 3 of 92 VirusTotal engines flagged it on 21 Nov 2026, and MetaMask and SEAL block it, with Kaspersky, Forcepoint ThreatSeeker and Gridinsoft among the scanners flagging the URL, proving that independent security teams recognize the page as suspicious. PhishDestroy's evidence score for it is 60/100 (high).

Where this page leads and expected next steps

Pages utilizing prominent wallet branding alongside generic continuation prompts typically lead visitors toward malicious connection requests or signature prompts designed to drain assets. When users click the primary button, subsequent scripts often request permissions to access connected accounts or sign transactions under the guise of an upgrade. Since official updates from wallet providers occur directly through verified applications rather than unverified web portals, engaging with such prompts risks unauthorized wallet access.

Recommended precautions and wallet review

Visitors who have already interacted with the page or clicked continue should immediately inspect their connected wallet sessions and revoke any unfamiliar token allowances. Legitimate wallet migrations never require users to connect their accounts through unexpected third-party links found online. Always verify announcements through official communication channels before approving any external connections.

Source evidenceVirusTotal 3 / 92 5 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 16 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
3
Denominator
92
Vendors
Forcepoint ThreatSeeker, Gridinsoft, Kaspersky
Observed at
2026-11-21 02:16:03
Checked at
2026-11-21 19:14:10
Fetched at
2026-11-21 18:14:11

URLScan

Page capture

SHA-256 9958ea4b…8e6985a

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record · 2026-11-22 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1ff32-1bc3-71f7-9bcc-b51c0affb21d
Score
0
Malicious
✗
Result at
2026-11-22T04:30:19Z
Enriched at
2026-11-22T09:13:10Z
Source timestamps
Urlscan result at: 2026-11-22 05:30:19; Urlscan enriched at: 2026-11-22 10:13:10

PhishDestroy DOM

10 / 100 · heuristic score · 1 brand reference · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-21 19:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
10
Analyzed at
2026-11-21T19:20:10Z
Source timestamp
2026-11-21 20:20:10
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
claim-xrpl.org — XRP Ledger notice with Xaman layout
AI description
claim-xrpl.org presents a Xaman brand page about evolving keys on the XRP Ledger, is flagged by 3 VirusTotal engines, and should be avoided.
AI summary
Xaman branding and XRP Ledger page layout The page at claim-xrpl.org displays a clean, minimalist interface centered around Xaman and XRP Ledger branding. At the top, it features the text "Xaman" accompanied by a blue dot and a small "XRPL" badge. A white card in the center holds the prominent headline "Your keys, evolving." Below this, secondary text reads, "We're preparing the next Xaman experience for the XRP Ledger. Check back soon." A bright blue button labeled "Continue" sits centrally inside the card, while the bottom of the page displays a copyright notice reading "© 2026 Xaman." The overall layout mimics a maintenance or preparation portal for the Xaman wallet ecosystem, inviting users to click through the primary button. Registration timeline and independent vendor detections Because it was registered on 19 Nov 2026, 2 days before it was first reported, the timeline sharply contrasts with the polished appearance of an established ecosystem update. Furthermore, 3 of 92 VirusTotal engines flagged it on 21 Nov 2026, and MetaMask and SEAL block it, with Kaspersky, Forcepoint ThreatSeeker and Gridinsoft among the scanners flagging the URL, proving that independent security teams recognize the page as suspicious. PhishDestroy's evidence score for it is 60/100 (high). Where this page leads and expected next steps Pages utilizing prominent wallet branding alongside generic continuation prompts typically lead visitors toward malicious connection requests or signature prompts designed to drain assets. When users click the primary button, subsequent scripts often request permissions to access connected accounts or sign transactions under the guise of an upgrade. Since official updates from wallet providers occur directly through verified applications rather than unverified web portals, engaging with such prompts risks unauthorized wallet access. Recommended precautions and wallet review Visitors who have already interacted with the page or clicked continue should immediately inspect their connected wallet sessions and revoke any unfamiliar token allowances. Legitimate wallet migrations never require users to connect their accounts through unexpected third-party links found online. Always verify announcements through official communication channels before approving any external connections.
AI generated by
threat-v10-gemini
AI generated at
2026-11-21T18:18:58Z
Revision
5624d7287261a379735b70411db357f04cd979edd52175f084253fd05148cf1d
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 25 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
2051

Page title and metadata

Page title
Your keys, evolving. | Xaman
Indexing directives
noindex,nofollow
Description
We're preparing the next Xaman experience for the XRP Ledger. Check back soon.

Trackers

Requests
2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
97
Download
0
Response time, ms
158

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
1063
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    108.162.193.174
    Host
    hal.ns.cloudflare.com
  • IP address
    108.162.194.102
    Host
    sydney.ns.cloudflare.com
DNS zone
claim-xrpl.org

Page quality

Layout shift (CLS)
0
SEO score
54
Speed Index, s
2.24
First Contentful Paint (FCP), s
0.76
Largest Contentful Paint (LCP), s
0.76
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
100
Best practices score
100

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
Cloudflare, Inc.
City
Washington
Country
US

TLS certificate

Subject alternative names
  • *.claim-xrpl.org
  • claim-xrpl.org
Key size, bits
256
Certificate chain
  • claim-xrpl.org
  • YE2
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE2
Serial
064C728062677132B5B1ECCAA9C4D0C8A719
SHA-256
3a72eac9a3ec7dd8917c212566399df40b49282591e23e163f0948eaafddab42
Subject
claim-xrpl.org
Valid until
Valid from

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
NS
  • hal.ns.cloudflare.com
  • sydney.ns.cloudflare.com
SOA
Primary nameserver
hal.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2420571560
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
1; mode=block
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
frame-ancestors http: https:
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://claim-xrpl.org

Technology stack

Technologies
  • HSTS
  • Cloudflare
  • HTTP/3

Page links

Internal link addresses
  • https://claim-xrpl.org/home/
Internal links
1

Registration record

Registrar
Key-Systems GmbH
Registrar IANA ID
269
Registrar URL
http://www.key-systems.net
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • hal.ns.cloudflare.com
  • sydney.ns.cloudflare.com
DNSSEC
unsigned

HTTP headers

Response 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
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-21T17:45:21Z; First: 2026-11-21T17:45:21Z; Changes: 0; Days archived: 1; Avg page bytes: 2051
Page title and metadata
Title: Your keys, evolving. | Xaman; Robots: noindex,nofollow; Description: We're preparing the next Xaman experience for the XRP Ledger. Check back soon.
Trackers
Requests: 2
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 97; Download: 0; Response ms: 158
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 1063; Co2 grams: 0; Cleaner than: 95
DNS server
NS: (IP: 108.162.193.174; Host: hal.ns.cloudflare.com), (IP: 108.162.194.102; Host: sydney.ns.cloudflare.com); Zone: claim-xrpl.org
Quality
Cls: 0; Seo: 54; Si s: 2.24; Fcp s: 0.76; Lcp s: 0.76; Tbt ms: 0; Performance: 100; Accessibility: 100; Best practices: 100
Location
IP: 2a06:98c1:3121::3; ASN: 13335; Org: Cloudflare, Inc.; City: Washington; Country: US
SSL
San: *.claim-xrpl.org, claim-xrpl.org; Bits: 256; Chain: claim-xrpl.org, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 064C728062677132B5B1ECCAA9C4D0C8A719; SHA256: 3a72eac9a3ec7dd8917c212566399df40b49282591e23e163f0948eaafddab42; Subject: claim-xrpl.org; Valid to: 2027-02-17T09:57:46Z; Valid from: 2026-11-19T09:57:47Z
DNS records
A: 188.114.96.3, 188.114.97.3; NS: hal.ns.cloudflare.com, sydney.ns.cloudflare.com; Soa: Nsname: hal.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2420571560; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3121::3, 2a06:98c1:3120::3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=63072000; includeSubDomains; preload; Message: Site is compatible with the HSTS preload list!; Compatible: ✓
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: 1; mode=block; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: frame-ancestors http: https:; Stricttransportpolicy: max-age=63072000; includeSubDomains; preload; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2a06:98c1:3120::3; Family: 6
Redirects
Chain: https://claim-xrpl.org
Tech stack
Technologies: HSTS, Cloudflare, HTTP/3
Page links
Internal: https://claim-xrpl.org/home/; Internal count: 1
Registration record
Registrar: Key-Systems GmbH; Registrar iana ID: 269; Registrar URL: http://www.key-systems.net; Created: 2026-11-19T10:46:47Z; Updated: 2026-11-19T10:47:08Z; Expires: 2027-11-19T10:46:47Z; Status: clientDeleteProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: hal.ns.cloudflare.com, sydney.ns.cloudflare.com; Dnssec: unsigned
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

Questions about claim-xrpl.org

Is claim-xrpl.org the official Xaman site?

No, the domain was registered recently on 19 Nov 2026, whereas legitimate Xaman services operate through their verified channels. Visitors should always rely on official application links rather than unfamiliar web addresses.

What happens if I clicked Continue on claim-xrpl.org?

Clicking continue on unfamiliar links can lead to malicious connection prompts or requests for wallet approvals. If you interacted with the page, check your wallet for unauthorized token allowances and revoke them immediately.

Why are security vendors flagging this domain?

The domain triggered security alerts because 3 of 92 VirusTotal engines flagged it on 21 Nov 2026, and MetaMask and SEAL block it. Reviewing these telemetry signals helps protect users from potential wallet drainers.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (2)

All capture links and hashes (2)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 86 report ↗
IP Context Canada188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Key-Systems DE(DE)
RegistrationCreated 2026-11-19 (3d · Brand New!) — Expires 2027-11-19
Registrant countryCyprus VirusTotal WHOIS
Registrant1f8f4166599d23ee4babf6fcc6f7794as@domain-contact.org VirusTotal WHOIS
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-21
DOM Analysisanalyzed 2026-11-21score 10/1001 brand signal
Submitted URLhttp://claim-xrpl.org/
Favicon Hash
Observed page title
Your keys, evolving. | Xaman
Automated brand references
Ledger
TLS Certificate
Issued by YE2 · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
CloudFlare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • hal.ns.cloudflare.com
  • sydney.ns.cloudflare.com

SOA

  • nsname: hal.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2420571560
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-11-19 09:57:47
Valid until
2027-02-17 09:57:46
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3a72eac9a3ec7dd8917c212566399df40b49282591e23e163f0948eaafddab42
Certificate names · 2 SANs
  • *.claim-xrpl.org
  • claim-xrpl.org

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-22 11:59 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-22 11:59 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:59 UTC last content: 2026-11-22 11:59 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 · 4 identified
Open complete records

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
Kaspersky
Gridinsoft
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of claim-xrpl.org ·

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.81 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://claim-xrpl.org/
Final URL: https://claim-xrpl.org/
Your keys, evolving. | Xaman
We're preparing the next Xaman experience for the XRP Ledger. Check back soon.
Response
HTTP 200
HTML body
1.4 KB
Compressed
804 B
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Content-Type-OptionsX-XSS-Protection
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 24
Access-Control-Allow-Headers
Content-Type, Authorization, Content-Length, X-Requested-With, Accept, Origin
Access-Control-Allow-Methods
GET, POST, PUT, DELETE, PATCH, OPTIONS
Access-Control-Allow-Origin
*
Access-Control-Max-Age
86400
Alt-Svc
h3=":443"; ma=86400
CasT-Mode
default
cf-cache-status
DYNAMIC
CF-RAY
a5e17efc5a0a751f-AMS
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors http: https:
Content-Type
text/html
Date
Sat, 21 Nov 2026 17:43:19 GMT
Last-Modified
Wed, 18 Nov 2026 20:54:52 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=iB2ZYHEAM1hIVKaRoXMjtjgoblNKZDFDxO51fkCDkpbAfdHgAr3EN4PMbxyFwZRC3vdHp3XByePGpZyuxlIG6aheS6XvXunfyVtQk%2FKbf5gj7%2FdcZnaAsVxddQGxcJhODQ%3D%3D"}]
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Timing-Allow-Origin
*
Transfer-Encoding
chunked
Vary
accept-encoding
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data111
Open complete records

Captured network requests

Network requests: 5 SHA-256 hashes: 5 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-21 17:46 UTC.

Open this scan on URLScan 01a1ff32-1bc3-71f7-9bcc-b51c0affb21d ↗

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Domain monitor · First collection record

    Reachable

All retained availability observations4
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    claim-xrpl.org detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · Automated brand label: XRP · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+39 h 29 min
  3. Added to PhishDestroy+15 h 25 min
  1. Wayback Machine

    Page archived

    +3 min
  2. Added to PhishDestroy

    claim-xrpl.org

    same minute
  3. URLScan

    Page captured

    +15 h 25 min
  4. VirusTotal

    3/92 engine detections

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

claim-xrpl.org

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including claim-xrpl.org)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/claim-xrpl.org"
  title="PhishDestroy threat report for claim-xrpl.org"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>