Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-30T02:35:29Z. Retrieved (as stored): 2026-10-31T22:40:53Z. 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
receive-xaman.app favicon

receive-xaman.app

In short

The captured page on receive-xaman.app displays Xaman branding and the headline "The Xaman Airdrop Is Activated," inviting XRP holders, XRPL participants and Xaman Wallet users to check whether they qualify for an allocation. It promises that eligible distributions go directly to the user's wallet on the XRP Ledger, and the main interaction is a single "Claim Airdrop" button beneath that eligibility message.

“Xaman Airdrop | XRP Qualify”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada172.67.198.170Cloudflare, Inc. · CDN
Registered
Oct 29, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 31, 2026 22:09 UTC · PhishDestroy
Risk signals
VirusTotal detections: 3/92 Spamhaus DBL: phishing domain Stored blocklist matches: 2 Young domain: 6 days old Google Safe Browsing: threat flag recorded
VirusTotal
3 / 92
engine detections ·
Google Safe Browsing
Flagged
Blocklist matches
2
MetaMask, SEAL
OTX
4
community references
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
6
open gallery
Domain age
6 days
registered 2026-10-29 according to WHOIS
OTX: 4 refs Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded receive-xaman.app on 2026-10-31. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-30T02:35:29Z. Retrieved (as stored): 2026-10-31T22:40:53Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: Dynadot. Hosting: Cloudflare, Inc. Listed by external blocklists: MetaMask, SEAL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
3 / 92
Blocklist matches
2
Scam type (automated label)
Fake Airdrop
Hosting
Canada172.67.198.170Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Oct 29, 2026
OTX
4 community refs
Page captures
6
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-31T22:41:53Z
SHA-256: 2e9749c90a57fc675e52fb61858e09027f5d01ffa7de8cbf32290bf51c29563e

PhishDestroy analysis, reviewed version

The captured page on receive-xaman.app displays Xaman branding and the headline "The Xaman Airdrop Is Activated," inviting XRP holders, XRPL participants and Xaman Wallet users to check whether they qualify for an allocation. It promises that eligible distributions go directly to the user's wallet on the XRP Ledger, and the main interaction is a single "Claim Airdrop" button beneath that eligibility message.

The stored VirusTotal domain result reports 3 detections out of 92 engines. CRDF reported "malicious"; Gridinsoft reported "phishing".

Source evidenceVirusTotal 3 / 92 · Google Safe Browsing: flagged · OTX 4 references 8 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
0
Malicious
3
Suspicious
0
Undetected
89

Vendor labels

CRDF
malicious
Gridinsoft
phishing
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::ac43:c6aa
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::6815:44d4
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.198.170
  • TTL, seconds
    21600
    Type
    NS
    Value
    cleo.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    cleo.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.68.212
  • TTL, seconds
    21600
    Type
    NS
    Value
    wanda.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.receive-xaman.app
  • receive-xaman.app
Issuer
Let's Encrypt / YE1
Serial
5884d2671289597eded086c8cbf7cd3a2cb
SHA-256
de417a911de508afd6528d4421a75b08bf244ecc7a896ef480d83a90e21f33d6
Subject
receive-xaman.app
Valid until
Valid from

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
DYNADOT LLC
Registrar IANA ID
472
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 0,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 89
}
Vendor labels
{
    "CRDF": "malicious",
    "Gridinsoft": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-10-30T01:41:31Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:c6aa"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::6815:44d4"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.198.170"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "cleo.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "cleo.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.68.212"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "wanda.ns.cloudflare.com"
    }
]
Dns at
2026-10-30T02:40:46Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.receive-xaman.app",
        "receive-xaman.app"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5884d2671289597eded086c8cbf7cd3a2cb",
    "sha256": "de417a911de508afd6528d4421a75b08bf244ecc7a896ef480d83a90e21f33d6",
    "subject": "receive-xaman.app",
    "valid_to": "2027-01-27T22:50:49Z",
    "valid_from": "2026-10-29T22:50:50Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-29T22:01:36Z",
        "last changed": "2026-10-29T23:45:37Z",
        "registration": "2026-10-29T22:01:36Z",
        "registrar expiration": "2027-10-29T22:01:36Z",
        "last update of RDAP database": "2026-10-29T23:45:51Z"
    },
    "registrar": "DYNADOT LLC",
    "registrar_iana_id": "472"
}
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
3
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","CRDF","Gridinsoft"]
observed_at
2026-10-30 02:35:29
checked_at
2026-10-31 23:41:04
fetched_at
2026-10-31 22:41:04
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

5b3680b1-9997-4d9d-ba22-f774f6812cef

Final URL

https://receive-xaman.app/

HTTP response

200

Navigation history

  • URL
    https://receive-xaman.app/
    Status
    200

DOM structure hash

3a6bbfdf2d7dcb90498dfde0fa59639d5209d97416912f283a1823e57dc26dc3

Document hash

a95dab92579c8cea0555f7b250855f7bb23312aa37afb9a6751276b79785a22d

Phishing classifier result

  • phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    receive-xaman.app
    Type
    A
    Value
    104.21.68.212
  • Name
    receive-xaman.app
    Type
    A
    Value
    172.67.198.170
  • Name
    receive-xaman.app
    Type
    AAAA
    Value
    2606:4700:3034::ac43:c6aa
  • Name
    receive-xaman.app
    Type
    AAAA
    Value
    2606:4700:3036::6815:44d4

DNSSEC valid

No

IP address

127.0.1.5

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

Registration record

Registrar
Dynadot LLC.
Registered
Updated
Expires
Nameservers
  • cleo.ns.cloudflare.com
  • wanda.ns.cloudflare.com
Original source fields · JSON
Uuid
5b3680b1-9997-4d9d-ba22-f774f6812cef
Final url
https://receive-xaman.app/
Status
200
History
[
    {
        "url": "https://receive-xaman.app/",
        "status": 200
    }
]
DOM structure hash
3a6bbfdf2d7dcb90498dfde0fa59639d5209d97416912f283a1823e57dc26dc3
Document hash
a95dab92579c8cea0555f7b250855f7bb23312aa37afb9a6751276b79785a22d
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "receive-xaman.app",
        "type": "A",
        "value": "104.21.68.212"
    },
    {
        "name": "receive-xaman.app",
        "type": "A",
        "value": "172.67.198.170"
    },
    {
        "name": "receive-xaman.app",
        "type": "AAAA",
        "value": "2606:4700:3034::ac43:c6aa"
    },
    {
        "name": "receive-xaman.app",
        "type": "AAAA",
        "value": "2606:4700:3036::6815:44d4"
    }
]
Dnssec valid
false
Ip
127.0.1.5

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

Registration record
{
    "registrar": "Dynadot LLC.",
    "created": "2026-10-29T22:01:36Z",
    "updated": "2026-10-29T23:45:37Z",
    "expires": "2027-10-29T22:01:36Z",
    "nameservers": [
        "cleo.ns.cloudflare.com",
        "wanda.ns.cloudflare.com"
    ]
}
Separate stored summary: suspicious · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
suspicious
categories
["Security Risks"]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

Google Safe Browsing

Threat flag recorded

Open report

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 715704ed2e9245efed0a019e88dc522898f2f8574abea02c5010c470c17220ed

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a19401-9c82-7269-ba4e-aa636b8a0f60

Final URL

https://receive-xaman.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://receive-xaman.app/
    From
    http://receive-xaman.app/
    Status
    307

IP address

172.64.80.1

Contacted domains

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

Contacted IP addresses

  • 104.21.15.138
  • 76.76.21.21
  • 192.179.18.119
  • 172.64.150.129
  • 104.26.13.205
  • 104.16.79.73
  • 172.64.80.1

Autonomous systems (ASN)

  • 13335
  • 16509
  • 15169

Server countries

  • US

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

a95dab92579c8cea0555f7b250855f7bb23312aa37afb9a6751276b79785a22d

Script hashes

  • 696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15
  • f43ae3a4555fa565144ce3214e6aabc8db42fe2916f131146c9682fcb8e84950

JavaScript globals

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

TLS session and certificate

Subject alternative names
  • *.receive-xaman.app
  • receive-xaman.app
Cipher
AES_128_GCM
Issuer
YE1
Subject
receive-xaman.app
Protocol
QUIC
Valid until
Valid from

Domain age, days

1

Registered domain age, days

1

Certificate age, days

1

Certificate validity, days

89

Page requests

33

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
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
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Content-security-policy
frame-ancestors http: https:
X-content-type-options
nosniff
Priority
u=0,i
Original source fields · JSON
Uuid
01a19401-9c82-7269-ba4e-aa636b8a0f60
Final url
https://receive-xaman.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://receive-xaman.app/",
        "from": "http://receive-xaman.app/",
        "status": 307
    }
]
Ip
172.64.80.1
Contacted domains
[
    "xrpl-scaner.com",
    "crossmark.io",
    "play-lh.googleusercontent.com",
    "pbs.twimg.com",
    "api.ipify.org",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.21.15.138",
    "76.76.21.21",
    "192.179.18.119",
    "172.64.150.129",
    "104.26.13.205",
    "104.16.79.73",
    "172.64.80.1"
]
Asns
[
    "13335",
    "16509",
    "15169"
]
Countries
[
    "US"
]
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
a95dab92579c8cea0555f7b250855f7bb23312aa37afb9a6751276b79785a22d
Script hashes
[
    "696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15",
    "f43ae3a4555fa565144ce3214e6aabc8db42fe2916f131146c9682fcb8e84950"
]
Globals
[
    "_0x1c9d",
    "_0x3699",
    "_0x42b876",
    "__ledgerLogsListen",
    "XRPLWalletConnect",
    "__cfBeacon",
    "__xamanSeedP",
    "subscribeButton",
    "emailInput",
    "subscription"
]
Tls
{
    "san": [
        "*.receive-xaman.app",
        "receive-xaman.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "receive-xaman.app",
    "protocol": "QUIC",
    "valid_to": "2027-01-27T22:50:49Z",
    "valid_from": "2026-10-29T22:50:50Z"
}
Domain age days
1
Apex age days
1
Tls age days
1
Tls valid days
89
Requests
33
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "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",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
    "content-security-policy": "frame-ancestors http: https:",
    "x-content-type-options": "nosniff",
    "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
01a19401-9c82-7269-ba4e-aa636b8a0f60
score
100
malicious
true
result_at
2026-11-01T04:30:23Z
enriched_at
2026-11-01T09:14:59Z
source_timestamps
{"urlscan_result_at":"2026-11-01 05:30:23","urlscan_enriched_at":"2026-11-01 10:14:59"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

PhishDestroy DOM

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

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

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:47:00Z
source_timestamp
2026-10-31 23:47:00
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
receive-xaman.app: Xaman Airdrop Eligibility Check Page
ai_description
PhishDestroy records the receive-xaman.app page, which presents a Xaman-branded airdrop eligibility check for XRP Ledger participants.
ai_summary
The captured page on receive-xaman.app displays Xaman branding and the headline "The Xaman Airdrop Is Activated," inviting XRP holders, XRPL participants and Xaman Wallet users to check whether they qualify for an allocation. It promises that eligible distributions go directly to the user's wallet on the XRP Ledger, and the main interaction is a single "Claim Airdrop" button beneath that eligibility message. The stored VirusTotal domain result reports 3 detections out of 92 engines. CRDF reported "malicious"; Gridinsoft reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 23:46:43
revision
c253bfa47b02d4b177312d3af4d38b8b848e44b25d797a47e74cf198763f8e8d
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
receive-xaman.app

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
27
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
2
TLS
39
Waiting
105
Connection
10
Download
1
Response time, ms
157

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
27713
CO₂, grams
0.001
Cleaner than, %
50

DNS servers

Nameservers
  • IP address
    172.64.33.89
    Host
    cleo.ns.cloudflare.com
  • IP address
    108.162.192.240
    Host
    wanda.ns.cloudflare.com
DNS zone
receive-xaman.app

Location

IP address
2606:4700:3036::6815:44d4
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
receive-xaman.app

DNS records

A
  • 104.21.68.212
  • 172.67.198.170
NS
  • wanda.ns.cloudflare.com
  • cleo.ns.cloudflare.com
SOA
Primary nameserver
cleo.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418806777
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3034::ac43:c6aa
  • 2606:4700:3036::6815:44d4

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
2606:4700:3036::6815:44d4
IP version
6

Redirects

Redirect chain
  • https://receive-xaman.app

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
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
}
Caa records
{
    "domain": "receive-xaman.app"
}
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": 27,
    "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": 2,
        "tls": 39,
        "wait": 105,
        "connect": 10,
        "download": 1
    },
    "response_ms": 157
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 27713,
    "co2_grams": 0.001,
    "cleaner_than": 50
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.89",
            "host": "cleo.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.240",
            "host": "wanda.ns.cloudflare.com"
        }
    ],
    "zone": "receive-xaman.app"
}
Location
{
    "ip": "2606:4700:3036::6815:44d4",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "receive-xaman.app"
}
DNS records
{
    "A": [
        "104.21.68.212",
        "172.67.198.170"
    ],
    "NS": [
        "wanda.ns.cloudflare.com",
        "cleo.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"cleo.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418806777, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3034::ac43:c6aa",
        "2606:4700:3036::6815:44d4"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": "1; mode=block",
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": "frame-ancestors http: https:",
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3036::6815:44d4",
    "family": 6
}
Redirects
{
    "chain": [
        "https://receive-xaman.app"
    ]
}
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",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload",
        "content-security-policy": "frame-ancestors http: https:",
        "x-content-type-options": "nosniff"
    }
}

Questions about receive-xaman.app

Is receive-xaman.app legit?

PhishDestroy rates receive-xaman.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 3/92 engines flagged. malicious: 3. suspicious: 0. Analysis time (as stored): 2026-10-30T02:35:29Z. Retrieved (as stored): 2026-10-31T22:40:53Z. Google Safe Browsing flags it. 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 receive-xaman.app safe to connect a wallet?

This report does not record which wallet requests receive-xaman.app 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 receive-xaman.app?

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: 2e9749c90a57fc675e52fb61858e09027f5d01ffa7de8cbf32290bf51c29563e SHA-256 of the prepared copy given to the model: 091b7dd63421095316f3980d1676180c86c2a19f68419d2c36a02e68c539ad2d
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://receive-xaman.app/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
Xaman Airdrop | XRP Qualify
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 83 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
Google Safe Browsing Flagged Social engineering checked Nov 2, 2026
IP Context Canada172.67.198.170 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for receive-xaman.app →
RegistrationCreated Oct 29, 2026 (6d · Brand New!) — Expires Oct 29, 2027
Elapsed Since First Report 2 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Unverified.
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://receive-xaman.app/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.198.170
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

  • cleo.ns.cloudflare.com
  • wanda.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-29 22:50:50
Valid until
2027-01-27 22:50:49
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintde417a911de508afd6528d4421a75b08bf244ecc7a896ef480d83a90e21f33d6
Certificate names · 2 SANs
  • *.receive-xaman.app
  • receive-xaman.app

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.67.198.170rapiddns.io

Latest Classified Outcome 2026-11-04 22:33:57 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Probe Inconclusive 20% 2026-11-02 11:31:41 UTC
RDAP registration
Observed timeline last reachable: 2026-11-01 23:34:01 UTC last content: 2026-11-01 23:01:58 UTC current episode first observed: 2026-11-02 22:33:36 UTC observed RIP window: 2026-11-01 23:34:01 UTC → 2026-11-02 22:33:36 UTC · 22.99h midpoint estimate ≈ 2026-11-02 11:03:48 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 · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive
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://receive-xaman.app/
Final URL: https://receive-xaman.app/
Xaman Airdrop | XRP Qualify
Explore the Xaman airdrop for XRP holders, XRPL participants and Xaman Wallet users. Check eligibility and learn about allocations on the XRP Ledger.
Response
HTTP 200
HTML body
27.1 KB
Compressed
6.7 KB
Links
2 internal · 29 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
Open Graph title: Claim Your $XRP Airdrop Now
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.
Twitter card: summary_large_image
Saved response-header values · 23
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
a535fe960e26f46f-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors http: https:
Content-Type
text/html
Date
Sat, 31 Oct 2026 22:11:15 GMT
Last-Modified
Thu, 29 Oct 2026 16:34: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=dR8Bu7CdN3xg7%2F%2BFcipTkemsuz9Yw3eiHTEW4v%2FEN8ENnw8Sz1JrOZJskKM5MQ%2FSdY2MwpqGM1P4HRlYPDunJyhwjWAXVL4AR4YiUR3CWPVj8vA7f%2BGO4tG5Z24AKUdUTJLAb
Server
cloudflare
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.

Archived
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
22.99
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: 33 SHA-256 hashes: 31 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:13 UTC.

Open this scan on URLScan 01a19401-9c82-7269-ba4e-aa636b8a0f60 ↗

Stored observation history6

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

  1. Domain monitor · Recorded state

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Earlier observations 1
  1. Domain monitor · First collection record

    Reachable

All retained availability observations19

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. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 23:33:57.507178
    Evidence SHA-256
    d90f23ef2fceb6cde0c0c3933f7f981919c265f78b9eb9b6f7967fe69561daa5
    Evidence timestamp as recorded
    2026-11-04 23:33:57.507178
  2. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 23:33:57.507178
    Evidence SHA-256
    d90f23ef2fceb6cde0c0c3933f7f981919c265f78b9eb9b6f7967fe69561daa5
    Evidence timestamp as recorded
    2026-11-04 23:33:57.507178
  3. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 23:33:53.720874
    Evidence SHA-256
    d2f93930fa3a5c87ef4e7f11adad7b0a49f810187b4e5f614005959725f4b5f7
    Evidence timestamp as recorded
    2026-11-03 23:33:53.720874
  4. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 23:33:53.720874
    Evidence SHA-256
    d2f93930fa3a5c87ef4e7f11adad7b0a49f810187b4e5f614005959725f4b5f7
    Evidence timestamp as recorded
    2026-11-03 23:33:53.720874
  5. dns_cachedns_inactive
    Observation source
    dns_cache
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 23:33:36.629046
    Evidence SHA-256
    242313e5fc8e280116b6019cc7b6a4eb72936801dba87c450c1b289e0f0c3d43
    Evidence timestamp as recorded
    2026-11-02 23:33:36.629046
  6. dns_observationdns_inactive
    Observation source
    dns_observation
    Cause
    dns_nxdomain
    Availability state
    dns_inactive
    Content state
    unreachable
    DNS state
    nxdomain
    DNS response code
    NXDOMAIN
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 23:33:36.629046
    Evidence SHA-256
    242313e5fc8e280116b6019cc7b6a4eb72936801dba87c450c1b289e0f0c3d43
    Evidence timestamp as recorded
    2026-11-02 23:33:36.629046
  7. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:41.000000
    Evidence SHA-256
    a929ac5d53c7eac9ee621f6b5226a0c9cf0f4eed5c5ff6f5a914a38f498889ba
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 12:31:41
    Evidence reason
    unavailable
  8. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:41.000000
    Evidence SHA-256
    a929ac5d53c7eac9ee621f6b5226a0c9cf0f4eed5c5ff6f5a914a38f498889ba
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 12:31:41
    Evidence reason
    unavailable
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-02 00:01:58.000000
    Evidence SHA-256
    986e710d69b8568550ab142ec5fb6f5044c499154b80c0a141131584ea138a88
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:01:58
    Evidence reason
    alive_content
  10. 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-02 00:01:58.000000
    Evidence SHA-256
    986e710d69b8568550ab142ec5fb6f5044c499154b80c0a141131584ea138a88
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:01:58
    Evidence reason
    alive_content
  11. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 23:32:58.613423
    Evidence SHA-256
    59b27e3292854a15689d14e242d8445dc6019e41fc8d1fd9ec24edac1f29a46f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:32:58.613423
    Evidence reason
  12. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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 12:02:15.000000
    Evidence SHA-256
    4eff94a91a1161c590913378e96bc445522375d022ca0e911fb49ff1d9d6302d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:02:15
    Evidence reason
    alive_content
  13. 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 12:02:15.000000
    Evidence SHA-256
    4eff94a91a1161c590913378e96bc445522375d022ca0e911fb49ff1d9d6302d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:02:15
    Evidence reason
    alive_content
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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:23.000000
    Evidence SHA-256
    27c54aa15679870b82dc1ae2505bb12acb69462572af25953178194af4bed7c5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:23
    Evidence reason
    alive_content
  15. 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:23.000000
    Evidence SHA-256
    27c54aa15679870b82dc1ae2505bb12acb69462572af25953178194af4bed7c5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:23
    Evidence reason
    alive_content
  16. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:31:41.538396
    Evidence SHA-256
    d507886309fe7925b612af112c97b5593f8ff1d1bd6793149e30d59a14244ced
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:31:41.538396
    Evidence reason
  17. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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:09:48.000000
    Evidence SHA-256
    9453af5e412e2e0f60771ef0b7e13c825ca22974f2c6ff3a2e29d968afb860a9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:09:48
    Evidence reason
  18. 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:09:48.000000
    Evidence SHA-256
    9453af5e412e2e0f60771ef0b7e13c825ca22974f2c6ff3a2e29d968afb860a9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 23:09:48
    Evidence reason
  19. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 22:35:44.819489
    Evidence SHA-256
    b115c70b57689143ecc4b9370c264aab93254bbb6510003d5a9dbfa5d3e0eccc
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:44.819489
    Evidence reason

Threat Response Pipeline

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

Recorded events: 15. 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
    receive-xaman.app detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Google Safe Browsing · Blocklist Detection · OTX Community References · Automated brand label: Xaman · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable Recorded: 13 of 13
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • 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.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 3/92
  • Google Safe Browsing
    Listed as unsafe by Google Safe Browsing (Google Transparency Report)
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 4. References are not vendor verdicts and are excluded from the evidence score.
  • 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; the cause was not independently established.
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

7 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    receive-xaman.app

    View source
  6. URLScan

    Page captured

    View source
  7. VirusTotal

    3/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

Check for cloaking

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

receive-xaman.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 3 det. ChainPatrol URLQuery Google SB Flagged SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs 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?

4 evidence signal groups linked Unverified
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 receive-xaman.app)
  • 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/receive-xaman.app"
  title="PhishDestroy threat report for receive-xaman.app"
  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>