Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-10-30T20:56:59Z. Retrieved (as stored): 2026-10-31T22:22:10Z. Listed by external blocklists: MetaMask, SEAL. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
reward-xaman.pages.dev favicon

reward-xaman.pages.dev

In short

The captured page at reward-xaman.pages.dev carries the headline "The Xaman Airdrop Is Activated" above text addressed to XRP holders, XRPL participants and Xaman Wallet users, inviting them to check whether they qualify for an allocation. The page states that eligible distributions go directly to the user's wallet on the XRP Ledger, and its main interaction is a prominent blue "Claim Airdrop" button beneath that copy. The page also shows Xaman-branded navigation and product imagery.

“Xaman Airdrop | XRP Qualify”

Review the evidence
Registrar
United StatesCloudflare
Resolved IP
Canada172.66.47.195Cloudflare, Inc. · CDN
First observed
Oct 31, 2026
PhishDestroy assessment Critical
85/100
Evidence score
Availability Reachable · access restricted Reachable response; page content was not verified Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Stored blocklist matches: 2 Last known active
VirusTotal
4 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
Page captures
6
open gallery
Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded reward-xaman.pages.dev on 2026-10-31. Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-10-30T20:56:59Z. Retrieved (as stored): 2026-10-31T22:22:10Z. Listed by external blocklists: MetaMask, SEAL. Risk: critical (85/100). Registrar: Cloudflare. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
4 / 92
Blocklist matches
2
Scam type (automated label)
Fake Airdrop
Hosting
Canada172.66.47.195Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Page captures
6
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-31T22:22:39Z
SHA-256: 6d224380f6f841326e2974e20549ce9a714e686bb1827c6ec4e5795338041b87

PhishDestroy analysis, reviewed version

The captured page at reward-xaman.pages.dev carries the headline "The Xaman Airdrop Is Activated" above text addressed to XRP holders, XRPL participants and Xaman Wallet users, inviting them to check whether they qualify for an allocation. The page states that eligible distributions go directly to the user's wallet on the XRP Ledger, and its main interaction is a prominent blue "Claim Airdrop" button beneath that copy. The page also shows Xaman-branded navigation and product imagery.

The stored VirusTotal domain result reports 4 detections out of 92 engines. ESET reported "phishing"; SOCRadar reported "phishing".

Source evidenceVirusTotal 4 / 92 8 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
4
Suspicious
0
Undetected
33

Vendor labels

ESET
phishing
SOCRadar
phishing
Kaspersky
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

CloudFlare, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.66.44.61
  • TTL, seconds
    300
    Type
    A
    Value
    172.66.47.195
  • TTL, seconds
    21600
    Type
    NS
    Value
    brett.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2c3d
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2fc3
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    brett.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    summer.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • *.reward-xaman.pages.dev
  • reward-xaman.pages.dev
Issuer
Let's Encrypt / YE2
Serial
6c0037a92e4c6de616eee6907cd2dc3e03
SHA-256
beb4ae307f10cd08708feec125b6d35e3d8a78c0c7531bcd3f8079925f6d0e9f
Subject
reward-xaman.pages.dev
Valid until
Valid from

Registration record

Registrar
CloudFlare, Inc.
Registrar IANA ID
1910
Registrar URL
None
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
  • clientdeleteprohibited
  • clienttransferprohibited
  • clientupdateprohibited
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 4,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
CloudFlare, Inc.
Created
2020-09-02T02:33:29Z
Expires
2026-09-02T02:33:29Z
Updated
2025-03-17T14:56:22Z
First seen
2026-10-29T23:10:54Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.44.61"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.66.47.195"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "brett.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2c3d"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2fc3"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "brett.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "summer.ns.cloudflare.com"
    }
]
Dns at
2026-10-30T21:00:10Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "*.reward-xaman.pages.dev",
        "reward-xaman.pages.dev"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "6c0037a92e4c6de616eee6907cd2dc3e03",
    "sha256": "beb4ae307f10cd08708feec125b6d35e3d8a78c0c7531bcd3f8079925f6d0e9f",
    "subject": "reward-xaman.pages.dev",
    "valid_to": "2027-01-27T20:59:06Z",
    "valid_from": "2026-10-29T20:59:07Z"
}
Registration record
{
    "registrar": "CloudFlare, Inc.",
    "registrar_iana_id": "1910",
    "registrar_url": "None",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2023-09-04T18:15:07Z",
    "expires": "2026-09-02T02:33:29Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "clientdeleteprohibited",
        "clienttransferprohibited",
        "clientupdateprohibited"
    ],
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
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
scope
unknown
result_state
observed
numerator
4
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","ESET","Kaspersky","SOCRadar"]
observed_at
2026-10-30 20:56:59
checked_at
2026-10-31 23:22:11
fetched_at
2026-10-31 22:22:11
time_basis
as stored; legacy timezone not established

URLScan

Malicious

SHA-256 fbc6eb9910e08f2e8bce20f3cd31cc8618ffac02c2d5077722d1a11997fa71c7

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1940a-bf50-769a-a794-4c02d6b9b8c0

Final URL

https://reward-xaman.pages.dev/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://reward-xaman.pages.dev/
    From
    http://reward-xaman.pages.dev/
    Status
    307

IP address

172.66.44.61

Contacted domains

  • xrpl-scaner.com
  • crossmark.io
  • play-lh.googleusercontent.com
  • pbs.twimg.com
  • api.ipify.org

Contacted IP addresses

  • 172.67.162.171
  • 76.76.21.21
  • 2a00:1450:4001:c25::77
  • 2a04:4e42:8d::159
  • 104.26.13.205
  • 172.66.44.61

Autonomous systems (ASN)

  • 13335
  • 16509
  • 15169
  • 54113

Server countries

  • US
  • DE

Linked domains

  • xaman.app
  • help.xaman.app
  • play.google.com
  • apps.apple.com
  • webflow-proxy-cdn.xaman.app
  • xrpl-labs.com
  • github.com
  • xumm.app
  • x.com
  • www.youtube.com
  • www.linkedin.com

Social media links

  • https://github.com/XRPL-Labs/Xaman-Issue-Tracker/blob/master/RESPONSIBLE-DISCLOSURE.md
  • https://x.com/xrpllabs
  • https://x.com/XamanWallet
  • https://x.com/xamanwallet
  • https://www.youtube.com/@XamanApp

Document hash

c32fccd0124576154253752ddae0e4c14079305dcf4fd508a96d00545350cda1

Script hashes

  • 696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15
  • c32fccd0124576154253752ddae0e4c14079305dcf4fd508a96d00545350cda1
  • f43ae3a4555fa565144ce3214e6aabc8db42fe2916f131146c9682fcb8e84950

JavaScript globals

  • _0x1c9d
  • _0x3699
  • _0x42b876
  • __ledgerLogsListen
  • XRPLWalletConnect
  • __xamanSeedP
  • subscribeButton
  • emailInput
  • subscription

TLS session and certificate

Subject alternative names
  • *.reward-xaman.pages.dev
  • reward-xaman.pages.dev
Cipher
AES_128_GCM
Issuer
YE2
Subject
reward-xaman.pages.dev
Protocol
QUIC
Valid until
Valid from

Domain age, days

2

Registered domain age, days

2

Certificate age, days

2

Certificate validity, days

89

Page requests

32

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • genericcrypto
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Generic Crypto
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Priority
u=0,i
Original source fields · JSON
Uuid
01a1940a-bf50-769a-a794-4c02d6b9b8c0
Final url
https://reward-xaman.pages.dev/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://reward-xaman.pages.dev/",
        "from": "http://reward-xaman.pages.dev/",
        "status": 307
    }
]
Ip
172.66.44.61
Contacted domains
[
    "xrpl-scaner.com",
    "crossmark.io",
    "play-lh.googleusercontent.com",
    "pbs.twimg.com",
    "api.ipify.org"
]
Contacted IP addresses
[
    "172.67.162.171",
    "76.76.21.21",
    "2a00:1450:4001:c25::77",
    "2a04:4e42:8d::159",
    "104.26.13.205",
    "172.66.44.61"
]
Asns
[
    "13335",
    "16509",
    "15169",
    "54113"
]
Countries
[
    "US",
    "DE"
]
Linked domains
[
    "xaman.app",
    "help.xaman.app",
    "play.google.com",
    "apps.apple.com",
    "webflow-proxy-cdn.xaman.app",
    "xrpl-labs.com",
    "github.com",
    "xumm.app",
    "x.com",
    "www.youtube.com",
    "www.linkedin.com"
]
Social
[
    "https://github.com/XRPL-Labs/Xaman-Issue-Tracker/blob/master/RESPONSIBLE-DISCLOSURE.md",
    "https://x.com/xrpllabs",
    "https://x.com/XamanWallet",
    "https://x.com/xamanwallet",
    "https://www.youtube.com/@XamanApp"
]
Document hash
c32fccd0124576154253752ddae0e4c14079305dcf4fd508a96d00545350cda1
Script hashes
[
    "696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15",
    "c32fccd0124576154253752ddae0e4c14079305dcf4fd508a96d00545350cda1",
    "f43ae3a4555fa565144ce3214e6aabc8db42fe2916f131146c9682fcb8e84950"
]
Globals
[
    "_0x1c9d",
    "_0x3699",
    "_0x42b876",
    "__ledgerLogsListen",
    "XRPLWalletConnect",
    "__xamanSeedP",
    "subscribeButton",
    "emailInput",
    "subscription"
]
Tls
{
    "san": [
        "*.reward-xaman.pages.dev",
        "reward-xaman.pages.dev"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "reward-xaman.pages.dev",
    "protocol": "QUIC",
    "valid_to": "2027-01-27T20:59:06Z",
    "valid_from": "2026-10-29T20:59:07Z"
}
Domain age days
2
Apex age days
2
Tls age days
2
Tls valid days
89
Requests
32
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "genericcrypto"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Generic Crypto"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "priority": "u=0,i"
}
Separate monitor record · 2026-11-01 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1940a-bf50-769a-a794-4c02d6b9b8c0
score
100
malicious
true
result_at
2026-11-01T04:30:20Z
enriched_at
2026-11-01T09:14:41Z
source_timestamps
{"urlscan_result_at":"2026-11-01 05:30:20","urlscan_enriched_at":"2026-11-01 10:14:41"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

30599427-e3d2-428e-a98b-6081e29b87c3

Final URL

https://reward-xaman.pages.dev/

HTTP response

200

Navigation history

  • URL
    https://reward-xaman.pages.dev/
    Status
    200

DOM structure hash

ae26fc46fa08dfffe392daa5f6e86ababd7dd3073b4e57b915f77969aec793bd

Document hash

c32fccd0124576154253752ddae0e4c14079305dcf4fd508a96d00545350cda1

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    reward-xaman.pages.dev
    Type
    A
    Value
    172.66.47.195
  • Name
    reward-xaman.pages.dev
    Type
    A
    Value
    172.66.44.61
  • Name
    reward-xaman.pages.dev
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2fc3
  • Name
    reward-xaman.pages.dev
    Type
    AAAA
    Value
    2606:4700:310c::ac42:2c3d

DNSSEC valid

No

IP address

127.0.1.13

127.0.1.13 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
CloudFlare, Inc.
Registered
Updated
Expires
Nameservers
  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com
Original source fields · JSON
Uuid
30599427-e3d2-428e-a98b-6081e29b87c3
Final url
https://reward-xaman.pages.dev/
Status
200
History
[
    {
        "url": "https://reward-xaman.pages.dev/",
        "status": 200
    }
]
DOM structure hash
ae26fc46fa08dfffe392daa5f6e86ababd7dd3073b4e57b915f77969aec793bd
Document hash
c32fccd0124576154253752ddae0e4c14079305dcf4fd508a96d00545350cda1
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "reward-xaman.pages.dev",
        "type": "A",
        "value": "172.66.47.195"
    },
    {
        "name": "reward-xaman.pages.dev",
        "type": "A",
        "value": "172.66.44.61"
    },
    {
        "name": "reward-xaman.pages.dev",
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2fc3"
    },
    {
        "name": "reward-xaman.pages.dev",
        "type": "AAAA",
        "value": "2606:4700:310c::ac42:2c3d"
    }
]
Dnssec valid
false
Ip
127.0.1.13

127.0.1.13 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "CloudFlare, Inc.",
    "created": "2020-09-02T02:33:29Z",
    "updated": "2026-06-09T12:00:52Z",
    "expires": "2027-09-02T02:33:29Z",
    "nameservers": [
        "adi.ns.cloudflare.com",
        "karl.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 100 · heuristic score · 1 brand reference · 1 classification

Open report
Separate monitor score · 15 / 100 · 2026-10-31T22:36:38Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
15
analyzed_at
2026-10-31T22:36:38Z
source_timestamp
2026-10-31 23:36:38
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
reward-xaman.pages.dev Xaman Airdrop Claim Page
ai_description
PhishDestroy records reward-xaman.pages.dev, a page presenting an activated Xaman Airdrop with a claim button for XRP holders.
ai_summary
The captured page at reward-xaman.pages.dev carries the headline "The Xaman Airdrop Is Activated" above text addressed to XRP holders, XRPL participants and Xaman Wallet users, inviting them to check whether they qualify for an allocation. The page states that eligible distributions go directly to the user's wallet on the XRP Ledger, and its main interaction is a prominent blue "Claim Airdrop" button beneath that copy. The page also shows Xaman-branded navigation and product imagery. The stored VirusTotal domain result reports 4 detections out of 92 engines. ESET reported "phishing"; SOCRadar reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 23:26:07
revision
c1fbe57ca578cfc1af861a5386a3556040431c8f4b7836d50f7f8f576f5e2560
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: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
reward-xaman.pages.dev

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

User agents
  • Twitterbot
  • *
Present
Yes

Sitemap

Present
Yes
URL count
1

Page title and metadata

Open Graph URL
https://xaman-promo.app/
Page title
Xaman Airdrop | XRP Qualify
Open Graph type
website
Indexing directives
index,follow,max-image-preview:large
Open Graph image
https://xaman-promo.app/social-preview.png
Open Graph title
Claim Your $XRP Airdrop Now
Open Graph site name
Xaman
Theme color
#0030cf
Description
Explore the Xaman airdrop for XRP holders, XRPL participants and Xaman Wallet users. Check eligibility and learn about allocations on the XRP Ledger.
Twitter card
summary_large_image
Canonical URL
https://xaman-promo.app/
Open Graph description
Explore the Xaman airdrop for XRP holders, XRPL participants and Xaman Wallet users. Check eligibility and learn about allocations on the XRP Ledger.

Trackers

Requests
28
Observed services
  • Name
    Google User Content
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    ipify
    Company
    ipify
    Category
    Misc
    Requests
    1
  • Name
    X Corp.
    Company
    X Corp.
    Country
    US
    Category
    Social Media
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
3
TLS
90
Waiting
62
Connection
8
Download
1
Response time, ms
164

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
27762
CO₂, grams
0.001
Cleaner than, %
50

DNS servers

Nameservers
  • IP address
    162.159.38.9
    Host
    summer.ns.cloudflare.com
  • IP address
    173.245.59.76
    Host
    brett.ns.cloudflare.com
DNS zone
reward-xaman.pages.dev

Location

IP address
2606:4700:310c::ac42:2fc3
ASN
13335
Organization
Cloudflare, Inc.
City
Montreal
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
reward-xaman.pages.dev

DNS records

A
  • 172.66.44.61
  • 172.66.47.195
NS
  • brett.ns.cloudflare.com
  • summer.ns.cloudflare.com
SOA
Primary nameserver
brett.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418801154
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:310c::ac42:2fc3
  • 2606:4700:310c::ac42:2c3d

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
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
2606:4700:310c::ac42:2c3d
IP version
6

Redirects

Redirect chain
  • https://reward-xaman.pages.dev

Page links

External link addresses
  • https://xaman.app/security
  • https://xaman.app/developers
  • https://xaman.app/cards
  • https://xaman.app/ecosystem
  • https://xaman.app/blog
  • https://help.xaman.app/app
  • https://play.google.com/store/apps/details
  • https://apps.apple.com/us/app/xaman-wallet-formerly-xumm/id1492302343
  • https://xaman.app/
  • https://xaman.app/pro
  • https://xaman.app/download
  • https://webflow-proxy-cdn.xaman.app/66ffb9c73bc7e83a1e0e1006/670662e9cd5f477f5b1dcad2_XRPL-Labs-Privacy-Statement-V1.pdf
  • https://xrpl-labs.com/static/documents/XRPL-Labs-Terms-of-Service-V1.pdf
  • https://github.com/XRPL-Labs/Xaman-Issue-Tracker/blob/master/RESPONSIBLE-DISCLOSURE.md
  • https://xumm.app/detect/xapp:xumm.support
  • https://x.com/xrpllabs
  • https://x.com/XamanWallet
  • https://xaman.app/contact
  • https://xrpl-labs.com/static/documents/xaman-logos.zip
  • https://xrpl-labs.com/static/documents/xaman-product.zip
  • https://x.com/xamanwallet
  • https://www.youtube.com/@XamanApp
  • https://www.linkedin.com/company/13043030/
External links
23
Internal links
1

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "reward-xaman.pages.dev"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "agents": [
        "Twitterbot",
        "*"
    ],
    "present": true
}
Sitemap
{
    "present": true,
    "url_count": 1
}
Page title and metadata
{
    "ogUrl": "https://xaman-promo.app/",
    "title": "Xaman Airdrop | XRP Qualify",
    "ogType": "website",
    "robots": "index,follow,max-image-preview:large",
    "ogImage": "https://xaman-promo.app/social-preview.png",
    "ogTitle": "Claim Your $XRP Airdrop Now",
    "ogSiteName": "Xaman",
    "themeColor": "#0030cf",
    "description": "Explore the Xaman airdrop for XRP holders, XRPL participants and Xaman Wallet users. Check eligibility and learn about allocations on the XRP Ledger.",
    "twitterCard": "summary_large_image",
    "canonicalUrl": "https://xaman-promo.app/",
    "ogDescription": "Explore the Xaman airdrop for XRP holders, XRPL participants and Xaman Wallet users. Check eligibility and learn about allocations on the XRP Ledger."
}
Trackers
{
    "requests": 28,
    "trackers": [
        {
            "name": "Google User Content",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "ipify",
            "company": "ipify",
            "category": "Misc",
            "requests": 1
        },
        {
            "name": "X Corp.",
            "company": "X Corp.",
            "country": "US",
            "category": "Social Media",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 90,
        "wait": 62,
        "connect": 8,
        "download": 1
    },
    "response_ms": 164
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 27762,
    "co2_grams": 0.001,
    "cleaner_than": 50
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.38.9",
            "host": "summer.ns.cloudflare.com"
        },
        {
            "ip": "173.245.59.76",
            "host": "brett.ns.cloudflare.com"
        }
    ],
    "zone": "reward-xaman.pages.dev"
}
Location
{
    "ip": "2606:4700:310c::ac42:2fc3",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Montreal",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "reward-xaman.pages.dev"
}
DNS records
{
    "A": [
        "172.66.44.61",
        "172.66.47.195"
    ],
    "NS": [
        "brett.ns.cloudflare.com",
        "summer.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"brett.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418801154, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:310c::ac42:2fc3",
        "2606:4700:310c::ac42:2c3d"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "strict-origin-when-cross-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:310c::ac42:2c3d",
    "family": 6
}
Redirects
{
    "chain": [
        "https://reward-xaman.pages.dev"
    ]
}
Page links
{
    "external": [
        "https://xaman.app/security",
        "https://xaman.app/developers",
        "https://xaman.app/cards",
        "https://xaman.app/ecosystem",
        "https://xaman.app/blog",
        "https://help.xaman.app/app",
        "https://play.google.com/store/apps/details",
        "https://apps.apple.com/us/app/xaman-wallet-formerly-xumm/id1492302343",
        "https://xaman.app/",
        "https://xaman.app/pro",
        "https://xaman.app/download",
        "https://webflow-proxy-cdn.xaman.app/66ffb9c73bc7e83a1e0e1006/670662e9cd5f477f5b1dcad2_XRPL-Labs-Privacy-Statement-V1.pdf",
        "https://xrpl-labs.com/static/documents/XRPL-Labs-Terms-of-Service-V1.pdf",
        "https://github.com/XRPL-Labs/Xaman-Issue-Tracker/blob/master/RESPONSIBLE-DISCLOSURE.md",
        "https://xumm.app/detect/xapp:xumm.support",
        "https://x.com/xrpllabs",
        "https://x.com/XamanWallet",
        "https://xaman.app/contact",
        "https://xrpl-labs.com/static/documents/xaman-logos.zip",
        "https://xrpl-labs.com/static/documents/xaman-product.zip",
        "https://x.com/xamanwallet",
        "https://www.youtube.com/@XamanApp",
        "https://www.linkedin.com/company/13043030/"
    ],
    "external_count": 23,
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "strict-origin-when-cross-origin"
    }
}

Questions about reward-xaman.pages.dev

Is reward-xaman.pages.dev legit?

PhishDestroy rates reward-xaman.pages.dev as critical risk (85/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 4/92 engines flagged. malicious: 4. suspicious: 0. Analysis time (as stored): 2026-10-30T20:56:59Z. Retrieved (as stored): 2026-10-31T22:22:10Z. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is reward-xaman.pages.dev safe to connect a wallet?

This report does not record which wallet requests reward-xaman.pages.dev makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used reward-xaman.pages.dev?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 6 captures

Cloudflare Radar 1 / 6 Used in the analysis Source file SHA-256: 6d224380f6f841326e2974e20549ce9a714e686bb1827c6ec4e5795338041b87 SHA-256 of the prepared copy given to the model: 1fff015a28e74170606f643667506b09cdb6bf6f8806322f239c591eee851128
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://reward-xaman.pages.dev/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Context Canada172.66.47.195 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
Abuse contact["registrar-abuse@cloudflare.com", "256f9e523b2ede94s@"]
HTTP Status403 Forbidden
Elapsed Since First Report 12h
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 15/1001 brand signal
Submitted URLhttp://reward-xaman.pages.dev/
Favicon Hash
Observed page title
Xaman Airdrop | XRP Qualify
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 83 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.47.195
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaMontreal, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • brett.ns.cloudflare.com
  • summer.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-29 20:59:07
Valid until
2027-01-27 20:59:06
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbeb4ae307f10cd08708feec125b6d35e3d8a78c0c7531bcd3f8079925f6d0e9f
Certificate names · 2 SANs
  • *.reward-xaman.pages.dev
  • reward-xaman.pages.dev

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

viewdns.info · 172.66.47.195rapiddns.io

Latest Classified Outcome 2026-11-05 02:24:18 UTC

The latest check was inconclusive.

Technical details
Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Stale Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-11-05 02:24:18 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 00:11:24 UTC last content: 2026-11-01 00:11:24 UTC current episode first observed: 2026-11-01 11:02:15 UTC observed RIP window: 2026-11-01 00:11:24 UTC → 2026-11-01 11:02:15 UTC · 10.85h midpoint estimate ≈ 2026-11-01 05:36:49 UTC · precision medium · 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 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
ESET
SOCRadar
Kaspersky
alphaMountain.ai
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
10.85
Estimate basis
Bounded by observations
Estimate precision
Medium

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

Captured network requests

Network requests: 32 SHA-256 hashes: 30 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-10-31 22:23 UTC.

Open this scan on URLScan 01a1940a-bf50-769a-a794-4c02d6b9b8c0 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Xaman Airdrop | XRP Qualify
Crawler
Suspected Phishing | Cloudflare
reward-xaman.pages.dev
Stored observation history4

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

    blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Domain monitor · Recorded state

    Reachable→Unavailable

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Domain monitor · First collection record

    Reachable

All retained availability observations10

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probeblocked
    Observation source
    current_http_probe
    Cause
    cloudflare_antiphishing
    Availability state
    provider_blocked
    Content state
    provider_blocked
    DNS state
    stale
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    phishing_interstitial
    Monitor confidence
    95
    Provider action verified
    true
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:24:18.000000
    Evidence SHA-256
    9c8719ea8a16d8bef28491fbf80de7340c4aa58ab4d3c0273b8ece9d09415b7d
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-05 03:24:18
    Evidence reason
    cloudflare_ban
  2. http_observationblocked
    Observation source
    http_observation
    Cause
    cloudflare_antiphishing
    Availability state
    provider_blocked
    Content state
    provider_blocked
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    phishing_interstitial
    Monitor confidence
    95
    Provider action verified
    true
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 03:24:18.000000
    Evidence SHA-256
    9c8719ea8a16d8bef28491fbf80de7340c4aa58ab4d3c0273b8ece9d09415b7d
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-05 03:24:18
    Evidence reason
    cloudflare_ban
  3. current_http_probeblocked
    Observation source
    current_http_probe
    Cause
    cloudflare_antiphishing
    Availability state
    provider_blocked
    Content state
    provider_blocked
    DNS state
    stale
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    phishing_interstitial
    Monitor confidence
    95
    Provider action verified
    true
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 09:36:37.000000
    Evidence SHA-256
    318fdc32dd08536bac3d1f5f8fd7512d81a4ea2784ac3f6e436401e61a0ab49f
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 09:36:37
    Evidence reason
    cloudflare_ban
  4. http_observationblocked
    Observation source
    http_observation
    Cause
    cloudflare_antiphishing
    Availability state
    provider_blocked
    Content state
    provider_blocked
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    phishing_interstitial
    Monitor confidence
    95
    Provider action verified
    true
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 09:36:37.000000
    Evidence SHA-256
    318fdc32dd08536bac3d1f5f8fd7512d81a4ea2784ac3f6e436401e61a0ab49f
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 09:36:37
    Evidence reason
    cloudflare_ban
  5. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:02:15.000000
    Evidence SHA-256
    c36571e61c78c5453e88088e8015cb8c43759a24b996d327e417aeb33fe2883a
    Evidence timestamp as recorded
    2026-11-01 12:02:15
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  6. http_observationblocked
    Observation source
    http_observation
    Cause
    cloudflare_antiphishing
    Availability state
    provider_blocked
    Content state
    provider_blocked
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    phishing_interstitial
    Monitor confidence
    95
    Provider action verified
    true
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 12:02:15.000000
    Evidence SHA-256
    d1b4383c8b0b7bb7fecc92b901b5c2d622e6033484765357d8d230e960650408
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-01 12:02:15
    Evidence reason
    cloudflare_ban
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 01:11:24.000000
    Evidence SHA-256
    a92b71811c8663621d99b1f87ae914bb439cf5e1539d7bb3e939e94caa4ed297
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:24
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 01:11:24.000000
    Evidence SHA-256
    a92b71811c8663621d99b1f87ae914bb439cf5e1539d7bb3e939e94caa4ed297
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:24
    Evidence reason
    alive_content
  9. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:15.000000
    Evidence SHA-256
    4a6aef195662d978e06c0e2ea0d89a2f1ae3477652ca367f8949df97370a588c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:20:15
    Evidence reason
  10. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:20:15.000000
    Evidence SHA-256
    4a6aef195662d978e06c0e2ea0d89a2f1ae3477652ca367f8949df97370a588c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:20:15
    Evidence reason

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: 1 of 1
  • Threat Ingested
    reward-xaman.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Automated brand label: Xaman · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Automated brand label: Xaman
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Content Observed Unavailable
    Monitoring recorded an unavailable response (HTTP 403); the cause was not independently established.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. Added to PhishDestroy

    reward-xaman.pages.dev

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    4/92 engine detections

    View source
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 4 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Reachable · access restricted
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
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

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 reward-xaman.pages.dev)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/reward-xaman.pages.dev"
  title="PhishDestroy threat report for reward-xaman.pages.dev"
  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>