Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 1/92 engines flagged. malicious: 1. suspicious: 0. Analysis time (as stored): 2026-10-29T15:39:50Z. Retrieved (as stored): 2026-10-30T00:27:11Z. 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
xaman-home.app favicon

xaman-home.app

In short

The captured page at xaman-home.app presents itself as an activated Xaman airdrop aimed at XRP holders, XRPL participants and Xaman Wallet users. Its main interaction is a prominent "Claim Airdrop" button, with supporting text stating that eligible distributions go directly to the user's wallet on the XRP Ledger.

“Xaman Airdrop | XRP Qualify”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada104.21.95.240Cloudflare, Inc. · CDN
First observed
Oct 29, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 1/92 Stored blocklist matches: 2 Google Safe Browsing: threat flag recorded
VirusTotal
1 / 92
engine detections ·
Google Safe Browsing
Flagged
Blocklist matches
2
MetaMask, SEAL
OTX
4
community references
URLScan
Malicious
Cloudflare Radar
Phishing
Page captures
4
open gallery
OTX: 4 refs Oct 29, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded xaman-home.app on 2026-10-29. Stored VirusTotal result: 1/92 engines flagged. malicious: 1. suspicious: 0. Analysis time (as stored): 2026-10-29T15:39:50Z. Retrieved (as stored): 2026-10-30T00:27:11Z. Google Safe Browsing flags it. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. Listed by external blocklists: MetaMask, SEAL. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
1 / 92
Blocklist matches
2
Scam type (automated label)
Airdrop Scam
Hosting
Canada104.21.95.240Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
OTX
4 community refs
Page captures
4
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-29T11:30:22Z
SHA-256: bc1c6ff1e074c3e223f6016152546ec4d14904d9d56cd210b59bbccc33baa83b

PhishDestroy analysis, reviewed version

The captured page at xaman-home.app presents itself as an activated Xaman airdrop aimed at XRP holders, XRPL participants and Xaman Wallet users. Its main interaction is a prominent "Claim Airdrop" button, with supporting text stating that eligible distributions go directly to the user's wallet on the XRP Ledger.

A VirusTotal domain-scope analysis dated 2026-10-29 returned 1 detection out of 92 engines, with 1 malicious and 0 suspicious verdicts. The single flagging vendor, alphaMountain.ai, labeled the domain "phishing".

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

VirusTotal

1 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
1
Suspicious
0
Undetected
38

Vendor labels

alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::ac43:95a4
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.149.164
  • TTL, seconds
    21600
    Type
    NS
    Value
    jo.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::6815:5ff0
  • TTL, seconds
    21600
    Type
    NS
    Value
    apollo.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.95.240
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    apollo.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.xaman-home.app
  • xaman-home.app
Issuer
Let's Encrypt / YE1
Serial
5bb71e6ba97abe6f7f709831082b34eef3
SHA-256
ce4d4d24528b5385514f154b9f2b06f106fd504085b88e6f00532f067ad8bb7b
Subject
xaman-home.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": 53,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 38
}
Vendor labels
{
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-10-29T03:17:56Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:95a4"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.149.164"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "jo.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:5ff0"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "apollo.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.95.240"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "apollo.ns.cloudflare.com"
    }
]
Dns at
2026-10-29T16:17:21Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.xaman-home.app",
        "xaman-home.app"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5bb71e6ba97abe6f7f709831082b34eef3",
    "sha256": "ce4d4d24528b5385514f154b9f2b06f106fd504085b88e6f00532f067ad8bb7b",
    "subject": "xaman-home.app",
    "valid_to": "2027-01-27T02:18:11Z",
    "valid_from": "2026-10-29T02:18:12Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-29T02:35:17Z",
        "last changed": "2026-10-29T02:35:26Z",
        "registration": "2026-10-29T02:35:17Z",
        "registrar expiration": "2027-10-29T02:35:17Z",
        "last update of RDAP database": "2026-10-29T02:45:42Z"
    },
    "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
12
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Emsisoft","Forcepoint ThreatSeeker","Fortinet","G-Data","Google Safe Browsing","Gridinsoft","Kaspersky","Netcraft","Seclookup","Webroot"]
observed_at
null
checked_at
2026-11-02 04:01:26
fetched_at
2026-11-02 03:01:26
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

ce0a6527-96e2-40bf-8b13-22053a76e153

Final URL

https://xaman-home.app/

HTTP response

200

Navigation history

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

DOM structure hash

7c5161b588f588bc955b1e3f857d0def80964ac6ed9f9fbf88b3b03ed86b0eaa

Document hash

01b7c1540b5d4cf293899194591947eac51fcf0163f2aa4045022f00ce578c81

Phishing classifier result

  • phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    xaman-home.app
    Type
    A
    Value
    104.21.95.240
  • Name
    xaman-home.app
    Type
    A
    Value
    172.67.149.164
  • Name
    xaman-home.app
    Type
    AAAA
    Value
    2606:4700:3033::ac43:95a4
  • Name
    xaman-home.app
    Type
    AAAA
    Value
    2606:4700:3034::6815:5ff0

DNSSEC valid

No

IP address

127.0.1.14

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

Original source fields · JSON
Uuid
ce0a6527-96e2-40bf-8b13-22053a76e153
Final url
https://xaman-home.app/
Status
200
History
[
    {
        "url": "https://xaman-home.app/",
        "status": 200
    }
]
DOM structure hash
7c5161b588f588bc955b1e3f857d0def80964ac6ed9f9fbf88b3b03ed86b0eaa
Document hash
01b7c1540b5d4cf293899194591947eac51fcf0163f2aa4045022f00ce578c81
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "xaman-home.app",
        "type": "A",
        "value": "104.21.95.240"
    },
    {
        "name": "xaman-home.app",
        "type": "A",
        "value": "172.67.149.164"
    },
    {
        "name": "xaman-home.app",
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:95a4"
    },
    {
        "name": "xaman-home.app",
        "type": "AAAA",
        "value": "2606:4700:3034::6815:5ff0"
    }
]
Dnssec valid
false
Ip
127.0.1.14

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

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

URLScan

Malicious

SHA-256 b1f67a8191a8e8aa044a6e8ea6e47afc840aad300de6d5d445294e33c617e3f0

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1876c-dd46-76ad-b39f-504bf3f6fab1

Final URL

https://xaman-home.app/

HTTP response

200

Redirect type

https-only

Redirects

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

IP address

172.67.149.164

Contacted domains

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

Contacted IP addresses

  • 104.21.15.138
  • 76.76.21.21
  • 142.251.14.119
  • 146.75.120.159
  • 104.26.13.205
  • 172.67.149.164

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

295227f4659e488b3f0596cf483ff6ee93ea9d3e448c778b56c4b30c2ce2be80

Script hashes

  • 696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15
  • 295227f4659e488b3f0596cf483ff6ee93ea9d3e448c778b56c4b30c2ce2be80
  • 46ddb7c3ed1cad4a732c8319d393da3e8357f373113dc49ea923d57fa27483e3

JavaScript globals

  • _0x2cb7
  • _0x57e4bd
  • _0x29b5
  • __ledgerLogsListen
  • XRPLWalletConnect
  • __xamanSeedP
  • subscribeButton
  • emailInput
  • subscription

TLS session and certificate

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

Domain age, days

0

Registered domain age, days

0

Certificate age, days

0

Certificate validity, days

89

Page requests

39

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
01a1876c-dd46-76ad-b39f-504bf3f6fab1
Final url
https://xaman-home.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://xaman-home.app/",
        "from": "http://xaman-home.app/",
        "status": 307
    }
]
Ip
172.67.149.164
Contacted domains
[
    "xrpl-scaner.com",
    "crossmark.io",
    "play-lh.googleusercontent.com",
    "pbs.twimg.com",
    "api.ipify.org"
]
Contacted IP addresses
[
    "104.21.15.138",
    "76.76.21.21",
    "142.251.14.119",
    "146.75.120.159",
    "104.26.13.205",
    "172.67.149.164"
]
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
295227f4659e488b3f0596cf483ff6ee93ea9d3e448c778b56c4b30c2ce2be80
Script hashes
[
    "696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15",
    "295227f4659e488b3f0596cf483ff6ee93ea9d3e448c778b56c4b30c2ce2be80",
    "46ddb7c3ed1cad4a732c8319d393da3e8357f373113dc49ea923d57fa27483e3"
]
Globals
[
    "_0x2cb7",
    "_0x57e4bd",
    "_0x29b5",
    "__ledgerLogsListen",
    "XRPLWalletConnect",
    "__xamanSeedP",
    "subscribeButton",
    "emailInput",
    "subscription"
]
Tls
{
    "san": [
        "*.xaman-home.app",
        "xaman-home.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "xaman-home.app",
    "protocol": "QUIC",
    "valid_to": "2027-01-27T02:18:11Z",
    "valid_from": "2026-10-29T02:18:12Z"
}
Domain age days
0
Apex age days
0
Tls age days
0
Tls valid days
89
Requests
39
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 · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a18710-59bf-7760-af23-8727ed026c51
score
null
malicious
null
result_at
null
enriched_at
2026-10-30T09:11:49Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-30 10:11:49"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

4 community references

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report

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
xaman-home.app Xaman Airdrop Eligibility Check Page
ai_description
PhishDestroy records xaman-home.app as a page offering XRP holders and Xaman Wallet users a way to check airdrop eligibility.
ai_summary
The captured page at xaman-home.app presents itself as an activated Xaman airdrop aimed at XRP holders, XRPL participants and Xaman Wallet users. Its main interaction is a prominent "Claim Airdrop" button, with supporting text stating that eligible distributions go directly to the user's wallet on the XRP Ledger. A VirusTotal domain-scope analysis dated 2026-10-29 returned 1 detection out of 92 engines, with 1 malicious and 0 suspicious verdicts. The single flagging vendor, alphaMountain.ai, labeled the domain "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-30 01:28:24
revision
54473b8e5f7c6bf53a3cb83be8a675b78baf8352aeb06ec8571a340549a9522b
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
xaman-home.app

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Sitemap

Present
Yes
URL count
1

Page title and metadata

Open Graph URL
https://xaman-home.app/
Page title
Xaman Airdrop | XRP Qualify
Open Graph type
website
Indexing directives
index,follow,max-image-preview:large
Open Graph image
https://xaman-home.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-home.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
142
TLS
119
Waiting
436
Connection
57
Download
0
Response time, ms
754

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

DNS servers

Nameservers
  • IP address
    172.64.32.172
    Host
    jo.ns.cloudflare.com
  • IP address
    173.245.59.66
    Host
    apollo.ns.cloudflare.com
DNS zone
xaman-home.app

Location

IP address
2606:4700:3033::ac43:95a4
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

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

DNS records

A
  • 104.21.95.240
  • 172.67.149.164
NS
  • jo.ns.cloudflare.com
  • apollo.ns.cloudflare.com
SOA
Primary nameserver
apollo.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418738890
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3033::ac43:95a4
  • 2606:4700:3034::6815:5ff0

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:3034::6815:5ff0
IP version
6

Redirects

Redirect chain
  • https://xaman-home.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": "xaman-home.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-29T11:30:50Z",
    "first": "2026-10-29T11:30:50Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 8471
}
Sitemap
{
    "present": true,
    "url_count": 1
}
Page title and metadata
{
    "ogUrl": "https://xaman-home.app/",
    "title": "Xaman Airdrop | XRP Qualify",
    "ogType": "website",
    "robots": "index,follow,max-image-preview:large",
    "ogImage": "https://xaman-home.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-home.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": 142,
        "tls": 119,
        "wait": 436,
        "connect": 57,
        "download": 0
    },
    "response_ms": 754
}
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": 27753,
    "co2_grams": 0.001,
    "cleaner_than": 50
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.32.172",
            "host": "jo.ns.cloudflare.com"
        },
        {
            "ip": "173.245.59.66",
            "host": "apollo.ns.cloudflare.com"
        }
    ],
    "zone": "xaman-home.app"
}
Location
{
    "ip": "2606:4700:3033::ac43:95a4",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "xaman-home.app"
}
DNS records
{
    "A": [
        "104.21.95.240",
        "172.67.149.164"
    ],
    "NS": [
        "jo.ns.cloudflare.com",
        "apollo.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"apollo.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418738890, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3033::ac43:95a4",
        "2606:4700:3034::6815:5ff0"
    ]
}
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:3034::6815:5ff0",
    "family": 6
}
Redirects
{
    "chain": [
        "https://xaman-home.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 xaman-home.app

Is xaman-home.app legit?

PhishDestroy rates xaman-home.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-29. Stored VirusTotal result: 1/92 engines flagged. malicious: 1. suspicious: 0. Analysis time (as stored): 2026-10-29T15:39:50Z. Retrieved (as stored): 2026-10-30T00:27:11Z. 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 xaman-home.app safe to connect a wallet?

This report does not record which wallet requests xaman-home.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 xaman-home.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 · 4 captures

Cloudflare Radar 1 / 4 Used in the analysis Source file SHA-256: bc1c6ff1e074c3e223f6016152546ec4d14904d9d56cd210b59bbccc33baa83b SHA-256 of the prepared copy given to the model: 5d00123248d303cb9a90a8648195f61c38da453a92ff327611c457ca6ceef49e
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://xaman-home.app/
Position1 / 4
Open capture Source Report Wayback Download
All capture links and hashes (4)
Observed page title
Xaman Airdrop | XRP Qualify
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 82 days
xaman-home.app: Xaman impersonation — Blocked by MetaMask, flagged by SEAL, Google Safe Browsing, 1/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card xaman-home.app: Xaman impersonation — Blocked by MetaMask, flagged by SEAL, Google Safe Browsing, 1/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 300da03432fb

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
Google Safe Browsing Flagged Social engineering checked Nov 2, 2026
IP Context Canada104.21.95.240 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 xaman-home.app →
RegistrationExpires Oct 29, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 15/1001 brand signal
Submitted URLhttp://xaman-home.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
Canada104.21.95.240
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

  • apollo.ns.cloudflare.com
  • jo.ns.cloudflare.com

SOA

  • nsname: apollo.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418738890
  • 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 02:18:12
Valid until
2027-01-27 02:18:11
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintce4d4d24528b5385514f154b9f2b06f106fd504085b88e6f00532f067ad8bb7b
Certificate names · 2 SANs
  • *.xaman-home.app
  • xaman-home.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 · 104.21.95.240rapiddns.io

Latest Classified Outcome 2026-11-05 03:01:36 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-05 03:01:36 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 03:01:36 UTC last content: 2026-11-05 03:01:36 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
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://xaman-home.app/
Final URL: https://xaman-home.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.5 KB
Compressed
6.9 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 · 24
Access-Control-Allow-Headers
Content-Type, Authorization, Content-Length, X-Requested-With, Accept, Origin
Access-Control-Allow-Methods
GET, POST, PUT, DELETE, PATCH, OPTIONS
Access-Control-Allow-Origin
*
Access-Control-Max-Age
86400
alt-svc
h3=":443"; ma=86400
cast-mode
default
cf-cache-status
DYNAMIC
CF-RAY
a521d8606ae78c39-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors http: https:
Content-Type
text/html
Date
Thu, 29 Oct 2026 11:29:55 GMT
Last-Modified
Thu, 29 Oct 2026 06:34:46 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=iW7corpBtIaFCbXYgpn%2BiXf8IcJxRFLu5yw47kEO8N2Q6n6LWV%2FK7sMIrqCqXLdsBFstcmNXQh%2BKNILEgkd%2BW56qvqJM0B9Ax55aBAvXYeiKidj%2BHGMpa5TJD%2Fzn%2Bo%2B
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
timing-allow-origin
*
Transfer-Encoding
chunked
Vary
accept-encoding
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 39 SHA-256 hashes: 34 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-29 11:32 UTC.

Open this scan on URLScan 01a1876c-dd46-76ad-b39f-504bf3f6fab1 ↗

Stored observation history10

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    protected

    http_access_restricted · access_restriction

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 5
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. VirusTotal · Detection count

    0→1

    Engines added
    alphaMountain.ai
    Engines removed
    None recorded
    Recorded vendor total
    1
  4. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  5. Domain monitor · First collection record

    Reachable

All retained availability observations31

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_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-05 04:01:36.000000
    Evidence SHA-256
    7a179a3d38488e9001087636c7627da603c888d149cfe101abcf3588404b7548
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 04:01:36
    Evidence reason
    alive_content
  2. 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-05 04:01:36.000000
    Evidence SHA-256
    7a179a3d38488e9001087636c7627da603c888d149cfe101abcf3588404b7548
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 04:01:36
    Evidence reason
    alive_content
  3. 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-04 23:21:01.569244
    Evidence SHA-256
    23fc21981d3f4a4c85bb59e9f7d4d9f56b19dcaacedad495e573240b5ed9121e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:21:01.569244
    Evidence reason
  4. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    http_access_restricted
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    access_restriction
    Monitor confidence
    50
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:04:38.000000
    Evidence SHA-256
    d9aff7c6f067fdf41b984130412ef63fbf75b1f8c4c2101a3037afb101771a44
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 12:04:38
    Evidence reason
    alive_content
  5. http_observationprotected
    Observation source
    http_observation
    Cause
    http_access_restricted
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    403
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Mechanism
    access_restriction
    Monitor confidence
    50
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 12:04:38.000000
    Evidence SHA-256
    d9aff7c6f067fdf41b984130412ef63fbf75b1f8c4c2101a3037afb101771a44
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 12:04:38
    Evidence reason
    alive_content
  6. 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-03 23:21:00.551669
    Evidence SHA-256
    93de4ce3edcedd421525733b44961d482bf295f4b8d35b7851f110ca6f86698b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:21:00.551669
    Evidence reason
  7. 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-02 23:20:40.877283
    Evidence SHA-256
    25c5ac0172f94ac6589ba15d57bef64f7b2aa3a7f5fe700edf28b10d7afed8a7
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:20:40.877283
    Evidence reason
  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-02 12:32:22.000000
    Evidence SHA-256
    4b047381811169f0f02c10a08b56644e16ff6db9a868c059a00e68097b8a530c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:32:22
    Evidence reason
    alive_content
  9. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    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
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:32:22.000000
    Evidence SHA-256
    d26914b87ec794dcf52c3858f0dac806329b095da45287c70cfd307f9add95e3
    Evidence timestamp as recorded
    2026-11-02 12:32:22
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  10. 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:34:26.000000
    Evidence SHA-256
    3282ea8ac5cd2c2142e334e81ee3a43aa03ee98ddf63a58f938af5e8b90d1197
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:34:26
    Evidence reason
    alive_content
  11. 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:34:26.000000
    Evidence SHA-256
    3282ea8ac5cd2c2142e334e81ee3a43aa03ee98ddf63a58f938af5e8b90d1197
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:34:26
    Evidence reason
    alive_content
  12. 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:20:11.055498
    Evidence SHA-256
    7c023747294077bd6e2ec2b080dc137e75a3ed6faf38dbdfcaa23e6958793fa3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 23:20:11.055498
    Evidence reason
  13. 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:36:20.000000
    Evidence SHA-256
    a3b553bce0e670419fcb665ab46e22fdddb22a23581565e7dcc4a03abc39fa4c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:36:20
    Evidence reason
    alive_content
  14. 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:36:20.000000
    Evidence SHA-256
    a3b553bce0e670419fcb665ab46e22fdddb22a23581565e7dcc4a03abc39fa4c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:36:20
    Evidence reason
    alive_content
  15. 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 04:23:59.000000
    Evidence SHA-256
    e6d427cf3b0b80df68770de6f8db3d7ced1f33bbc901bc782191c37a91e5883d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:59
    Evidence reason
    alive_content
  16. 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 04:23:59.000000
    Evidence SHA-256
    e6d427cf3b0b80df68770de6f8db3d7ced1f33bbc901bc782191c37a91e5883d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 04:23:59
    Evidence reason
    alive_content
  17. 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:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  18. 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-10-31 12:36:02.000000
    Evidence SHA-256
    2d32866f9cb68e858e716398216de084644b0b0c56dd141a9fe2d6f514c325cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:36:02
    Evidence reason
    alive_content
  19. 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-10-31 12:36:02.000000
    Evidence SHA-256
    2d32866f9cb68e858e716398216de084644b0b0c56dd141a9fe2d6f514c325cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:36:02
    Evidence reason
    alive_content
  20. 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-10-31 03:56:09.000000
    Evidence SHA-256
    ab9e9780051424d6434b9b64552400f8da9a9b2a98d008e4cf6be7c0de0e0930
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:56:09
    Evidence reason
    alive_content
  21. 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-10-31 03:56:09.000000
    Evidence SHA-256
    ab9e9780051424d6434b9b64552400f8da9a9b2a98d008e4cf6be7c0de0e0930
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:56:09
    Evidence reason
    alive_content
  22. 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-10-31 00:26:24.000000
    Evidence SHA-256
    3a9167b40de966c46be7e9db3aaa66b18e0cdf625154c108fda7a9f23d61f1fc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:26:24
    Evidence reason
    alive_content
  23. 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-10-31 00:26:24.000000
    Evidence SHA-256
    3a9167b40de966c46be7e9db3aaa66b18e0cdf625154c108fda7a9f23d61f1fc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:26:24
    Evidence reason
    alive_content
  24. 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:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  25. 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-10-30 12:33:42.000000
    Evidence SHA-256
    06523ae756dc9ff3f66e148cae8b3aaf6891ab64e4a6d8695126402d771cb7f5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:33:42
    Evidence reason
    alive_content
  26. 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-10-30 12:33:42.000000
    Evidence SHA-256
    06523ae756dc9ff3f66e148cae8b3aaf6891ab64e4a6d8695126402d771cb7f5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:33:42
    Evidence reason
    alive_content
  27. 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-10-30 00:32:57.000000
    Evidence SHA-256
    805676c4e5482a3a9bc81f72308662361b1d53f50533314e5521da0bb204af1d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:32:57
    Evidence reason
    alive_content
  28. 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-10-30 00:32:57.000000
    Evidence SHA-256
    805676c4e5482a3a9bc81f72308662361b1d53f50533314e5521da0bb204af1d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:32:57
    Evidence reason
    alive_content
  29. 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-29 12:31:35.000000
    Evidence SHA-256
    88fb51f64392f1e096cb5848ba955d0b7474c427a1bea453fe52e29ee8ed86b2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:31:35
    Evidence reason
  30. 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-29 12:31:35.000000
    Evidence SHA-256
    88fb51f64392f1e096cb5848ba955d0b7474c427a1bea453fe52e29ee8ed86b2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:31:35
    Evidence reason
  31. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-10-29 12:31:25.880179
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 14. 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
    xaman-home.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.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 · VirusTotal detections +1 Recorded: 12 of 12
  • 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: 1/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.
  • VirusTotal detections +1
    New detections: +1 (0 → 1): alphaMountain.ai
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

7 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. URLScan

    Page captured

    View source
  5. Wayback Machine

    Page archived

    View source
  6. Cloudflare Radar

    Phishing

    View source
  7. Added to PhishDestroy

    xaman-home.app

    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.

xaman-home.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 1 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 Last known active
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 xaman-home.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/xaman-home.app"
  title="PhishDestroy threat report for xaman-home.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>