Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T03:05:55Z. Retrieved (as stored): 2026-10-31T23:24:41Z. 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
rntb-xaman.app favicon

rntb-xaman.app

In short

The captured page on rntb-xaman.app presents itself as an activated Xaman airdrop, with a headline announcing that the Xaman Airdrop Is Activated. It tells XRP holders, XRPL participants and Xaman Wallet users they can check whether they qualify for an allocation, and the main interaction is a prominent Claim Airdrop button beneath that eligibility text.

“Xaman Airdrop | XRP Qualify”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United States188.114.97.3Cloudflare, Inc. · CDN
Registered
Oct 27, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 2/92 Spamhaus DBL: phishing domain Stored blocklist matches: 2 Young domain: 8 days old
VirusTotal
2 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
OTX
1
community references
URLScan
Malicious
Page captures
3
open gallery
Domain age
8 days
registered 2026-10-27 according to WHOIS
OTX: 1 ref Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded rntb-xaman.app on 2026-10-31. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T03:05:55Z. Retrieved (as stored): 2026-10-31T23:24:41Z. Listed by external blocklists: MetaMask, SEAL. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
2 / 92
Blocklist matches
2
Scam type (automated label)
Fake Airdrop
Hosting
United States188.114.97.3Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Oct 27, 2026
OTX
1 community ref
Page captures
3
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-10-31T23:26:16Z
SHA-256: 8e62e486b4db31fe96a4080336e97b67f1ae1ae07dc692dca44986aac2b3cc00

PhishDestroy analysis, reviewed version

The captured page on rntb-xaman.app presents itself as an activated Xaman airdrop, with a headline announcing that the Xaman Airdrop Is Activated. It tells XRP holders, XRPL participants and Xaman Wallet users they can check whether they qualify for an allocation, and the main interaction is a prominent Claim Airdrop button beneath that eligibility text.

The stored VirusTotal domain result reports 2 detections out of 92 engines. CRDF reported "malicious"; alphaMountain.ai reported "suspicious".

Source evidenceVirusTotal 2 / 92 · OTX 1 references 8 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
1
Suspicious
1
Undetected
35

Vendor labels

CRDF
malicious
alphaMountain.ai
suspicious

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Unrated (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::ac43:a8dd
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    cheryl.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3032::6815:1b22
  • TTL, seconds
    21600
    Type
    NS
    Value
    rommy.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    cheryl.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.168.221
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.27.34

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.rntb-xaman.app
  • rntb-xaman.app
Issuer
Let's Encrypt / YE2
Serial
57deee0171b8dcdfe54c1c7b63564cee31
SHA-256
d85369dc320e06e14505c96135f0b1823e020ead714b904ed63dbc5913eafad9
Subject
rntb-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": 55,
    "malicious": 1,
    "suspicious": 1,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Unrated (alphaMountain.ai)"
}
First seen
2026-10-29T05:29:56Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:a8dd"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "cheryl.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::6815:1b22"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "rommy.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "cheryl.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.168.221"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.27.34"
    }
]
Dns at
2026-10-31T03:18:27Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.rntb-xaman.app",
        "rntb-xaman.app"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "57deee0171b8dcdfe54c1c7b63564cee31",
    "sha256": "d85369dc320e06e14505c96135f0b1823e020ead714b904ed63dbc5913eafad9",
    "subject": "rntb-xaman.app",
    "valid_to": "2027-01-28T06:42:21Z",
    "valid_from": "2026-10-30T06:42:22Z"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-27T21:44:56Z",
        "last changed": "2026-10-27T21:45:17Z",
        "registration": "2026-10-27T21:44:56Z",
        "registrar expiration": "2027-10-27T21:44:56Z",
        "last update of RDAP database": "2026-10-28T09:51:19Z"
    },
    "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
10
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CRDF","Emsisoft","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Webroot"]
observed_at
null
checked_at
2026-11-05 04:04:39
fetched_at
2026-11-05 03:04:39
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Suspicious

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

bc384f7a-6e13-4ec4-b6a8-1f04a8c9bbd4

Final URL

https://rntb-xaman.app/

HTTP response

200

Navigation history

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

DOM structure hash

26165c4e37eadd27f2ba0619ab59584eb24e6193d314114931a81d480e543617

Document hash

be97216bc8de394398dccb6213d213ae8aa8b466cacbd6b0884ed6c511608cb3

Domain risk categories

  • New Domains
  • Security Risks
  • Newly Seen Domains

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    rntb-xaman.app
    Type
    A
    Value
    188.114.96.0
  • Name
    rntb-xaman.app
    Type
    A
    Value
    188.114.97.0
  • Name
    rntb-xaman.app
    Type
    AAAA
    Value
    2a06:98c1:3120::
  • Name
    rntb-xaman.app
    Type
    AAAA
    Value
    2a06:98c1:3121::

DNSSEC valid

No

IP address

127.0.1.1

127.0.1.1 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
bc384f7a-6e13-4ec4-b6a8-1f04a8c9bbd4
Final url
https://rntb-xaman.app/
Status
200
History
[
    {
        "url": "https://rntb-xaman.app/",
        "status": 200
    }
]
DOM structure hash
26165c4e37eadd27f2ba0619ab59584eb24e6193d314114931a81d480e543617
Document hash
be97216bc8de394398dccb6213d213ae8aa8b466cacbd6b0884ed6c511608cb3
Domain risks
[
    "New Domains",
    "Security Risks",
    "Newly Seen Domains"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "rntb-xaman.app",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "rntb-xaman.app",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "rntb-xaman.app",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    },
    {
        "name": "rntb-xaman.app",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    }
]
Dnssec valid
false
Ip
127.0.1.1

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

Spamhaus DBL

phishing domain

URLScan

Malicious

SHA-256 b73a1b1be29e6d14edb3cbdb6b6e71cc968c19259bfccbaf236c2e5d2d93c368

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a19424-88df-7642-88ba-280d5adf4004

Final URL

https://rntb-xaman.app/

HTTP response

200

Redirect type

https-only

Redirects

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

IP address

104.21.27.34

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
  • 172.253.62.119
  • 172.64.150.129
  • 104.26.13.205
  • 104.16.79.73
  • 104.21.27.34

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

501e5429464a1e97ff5b9fdf91967731e46d24cba7d9a210ecfa71ac056e04d4

Script hashes

  • 696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15
  • f43ae3a4555fa565144ce3214e6aabc8db42fe2916f131146c9682fcb8e84950

JavaScript globals

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

TLS session and certificate

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

Domain age, days

2

Registered domain age, days

2

Certificate age, days

1

Certificate validity, days

89

Page requests

33

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
85
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
01a19424-88df-7642-88ba-280d5adf4004
Final url
https://rntb-xaman.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://rntb-xaman.app/",
        "from": "http://rntb-xaman.app/",
        "status": 307
    }
]
Ip
104.21.27.34
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",
    "172.253.62.119",
    "172.64.150.129",
    "104.26.13.205",
    "104.16.79.73",
    "104.21.27.34"
]
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
501e5429464a1e97ff5b9fdf91967731e46d24cba7d9a210ecfa71ac056e04d4
Script hashes
[
    "696c135f7ad08d2714a53e8e68b37b17554185780741fb7c0896ad94601b1e15",
    "f43ae3a4555fa565144ce3214e6aabc8db42fe2916f131146c9682fcb8e84950"
]
Globals
[
    "_0x1c9d",
    "_0x3699",
    "_0x42b876",
    "__ledgerLogsListen",
    "XRPLWalletConnect",
    "__cfBeacon",
    "__xamanSeedP",
    "subscribeButton",
    "emailInput",
    "subscription"
]
Tls
{
    "san": [
        "*.rntb-xaman.app",
        "rntb-xaman.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "rntb-xaman.app",
    "protocol": "QUIC",
    "valid_to": "2027-01-28T06:42:21Z",
    "valid_from": "2026-10-30T06:42:22Z"
}
Domain age days
2
Apex age days
2
Tls age days
1
Tls valid days
89
Requests
33
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "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
01a19424-88df-7642-88ba-280d5adf4004
score
100
malicious
true
result_at
2026-11-01T04:30:19Z
enriched_at
2026-11-02T09:14:32Z
source_timestamps
{"urlscan_result_at":"2026-11-01 05:30:19","urlscan_enriched_at":"2026-11-02 10:14:32"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 15 / 100 · 2026-10-31T23:20:13Z

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-31T23:20:13Z
source_timestamp
2026-11-01 00:20:13
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
rntb-xaman.app Xaman Airdrop Eligibility Page
ai_description
PhishDestroy records the rntb-xaman.app page, which presents an activated Xaman airdrop and a Claim Airdrop button for XRP holders.
ai_summary
The captured page on rntb-xaman.app presents itself as an activated Xaman airdrop, with a headline announcing that the Xaman Airdrop Is Activated. It tells XRP holders, XRPL participants and Xaman Wallet users they can check whether they qualify for an allocation, and the main interaction is a prominent Claim Airdrop button beneath that eligibility text. The stored VirusTotal domain result reports 2 detections out of 92 engines. CRDF reported "malicious"; alphaMountain.ai reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 00:31:57
revision
c94be0dfa4edd7338f9bc33d356d3319c8664e2723feba45290b6a27522021c8
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
rntb-xaman.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
8467

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.

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
5
TLS
24
Waiting
114
Connection
7
Download
0
Response time, ms
150

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
    108.162.195.20
    Host
    rommy.ns.cloudflare.com
  • IP address
    172.64.32.83
    Host
    cheryl.ns.cloudflare.com
DNS zone
rntb-xaman.app

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
rntb-xaman.app

DNS records

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

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

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

HTTP security policies

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

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

Redirects

Redirect chain
  • https://rntb-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": "rntb-xaman.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T22:49:17Z",
    "first": "2026-10-31T22:49:17Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 8467
}
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."
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 5,
        "tls": 24,
        "wait": 114,
        "connect": 7,
        "download": 0
    },
    "response_ms": 150
}
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": "108.162.195.20",
            "host": "rommy.ns.cloudflare.com"
        },
        {
            "ip": "172.64.32.83",
            "host": "cheryl.ns.cloudflare.com"
        }
    ],
    "zone": "rntb-xaman.app"
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "rntb-xaman.app"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "NS": [
        "rommy.ns.cloudflare.com",
        "cheryl.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"cheryl.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418831755, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::3",
        "2a06:98c1:3121::3"
    ]
}
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": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://rntb-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 rntb-xaman.app

Is rntb-xaman.app legit?

PhishDestroy rates rntb-xaman.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 2/92 engines flagged. malicious: 1. suspicious: 1. Analysis time (as stored): 2026-10-31T03:05:55Z. Retrieved (as stored): 2026-10-31T23:24:41Z. 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 rntb-xaman.app safe to connect a wallet?

This report does not record which wallet requests rntb-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 rntb-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 · 3 captures

Cloudflare Radar 1 / 3 Used in the analysis Source file SHA-256: 8e62e486b4db31fe96a4080336e97b67f1ae1ae07dc692dca44986aac2b3cc00 SHA-256 of the prepared copy given to the model: 88cda7167054f9d136b4c97a9ca57047f32dcaca787a84d0d9698612b985351d
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://rntb-xaman.app/
Position1 / 3
Open capture Source Report Wayback Download
All capture links and hashes (3)
Observed page title
Xaman Airdrop | XRP Qualify
Automated brand references
Ledger
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 83 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
IP Context United States188.114.97.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags blocklistcryptodrainerfraudphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for rntb-xaman.app →
RegistrationCreated Oct 27, 2026 (8d · Very New!) — Expires Oct 27, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Nov 1, 2026score 15/1001 brand signal
Submitted URLhttp://rntb-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
United States188.114.97.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
United StatesSan Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • cheryl.ns.cloudflare.com
  • rommy.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-30 06:42:22
Valid until
2027-01-28 06:42:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-31 23:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintd85369dc320e06e14505c96135f0b1823e020ead714b904ed63dbc5913eafad9
Certificate names · 2 SANs
  • *.rntb-xaman.app
  • rntb-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 · 188.114.97.3rapiddns.io

Latest Classified Outcome 2026-11-05 02:59:18 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 02:59:18 UTC
RDAP registration
Observed timeline last reachable: 2026-11-05 02:59:18 UTC last content: 2026-11-05 02:59:18 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 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
CRDF
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://rntb-xaman.app/
Final URL: https://rntb-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
a53636108a6dd279-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors http: https:
Content-Type
text/html
Date
Sat, 31 Oct 2026 22:49:08 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=GiOAkM0wVhsISTSyGGeBviXB%2Farm4NiSbPqvn2%2FuyL%2FkcTZhkMjytYDGOaqGDvtUPwagWwVYBtNkaQu9rmSAbvoaoM%2FAO5lJZuWhh3Xy125CIxfAMVGSjh18jJwi9H2B4w%3D%3
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 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: 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:49 UTC.

Open this scan on URLScan 01a19424-88df-7642-88ba-280d5adf4004 ↗

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. 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 1
  1. Domain monitor · First collection record

    Reachable

All retained availability observations20

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 03:59:18.000000
    Evidence SHA-256
    4fc0ad8ce9381770debb5b6132f94a6ec92e88c466bcd7535c85401fd81ff1a0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:59:18
    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 03:59:18.000000
    Evidence SHA-256
    4fc0ad8ce9381770debb5b6132f94a6ec92e88c466bcd7535c85401fd81ff1a0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 03:59:18
    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:33:57.507178
    Evidence SHA-256
    88889b50c6a46b5bfe067798e8d5b1b458bdfd09ccac17ea178a280bc22e10e3
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 23:33:57.507178
    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:01:47.000000
    Evidence SHA-256
    51f425bf2201049dc5abbc15a917f02687850c3fb7bc141263b349b3cc3a54b3
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 12:01:47
    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:01:47.000000
    Evidence SHA-256
    51f425bf2201049dc5abbc15a917f02687850c3fb7bc141263b349b3cc3a54b3
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-04 12:01:47
    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:33:53.720874
    Evidence SHA-256
    aea6a11223bdc60e237ee10c278d2bc47d9eb0893481092d584258b8839d2728
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 23:33:53.720874
    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:33:36.629046
    Evidence SHA-256
    0726bd26e43e4d7d238a159c0116f3a42369220f2c48c7f62f70e1fa3436c65f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 23:33:36.629046
    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:31:41.000000
    Evidence SHA-256
    2e1d5239e98ddecc90c04874131875f891997e5a79ea77eaa36a19b91ef054e2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:41
    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:31:41.000000
    Evidence SHA-256
    7fc4755f49bd308f372debbc30f55c14702c20da58f1bdb9dd8442d2143ea1b7
    Evidence timestamp as recorded
    2026-11-02 12:31:41
    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:02:02.000000
    Evidence SHA-256
    73e01d966c00d89f5e8f26346de7005401652e599dd39cd0a164dcac28db7cf3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:02:02
    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:02:02.000000
    Evidence SHA-256
    73e01d966c00d89f5e8f26346de7005401652e599dd39cd0a164dcac28db7cf3
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:02:02
    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: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
  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:02:19.000000
    Evidence SHA-256
    023c94d8014372d1d1694defb698ac615d1ca61fd78a7206ae1a1e6a903f7f73
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:02:19
    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:02:19.000000
    Evidence SHA-256
    023c94d8014372d1d1694defb698ac615d1ca61fd78a7206ae1a1e6a903f7f73
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:02:19
    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 01:11:28.000000
    Evidence SHA-256
    347c2bf021dad97e9efdb420ba9938ea29c39eddd52f37b5d7e36b7aea9b0596
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:28
    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 01:11:28.000000
    Evidence SHA-256
    347c2bf021dad97e9efdb420ba9938ea29c39eddd52f37b5d7e36b7aea9b0596
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 01:11:28
    Evidence reason
    alive_content
  17. current_state_backfillunknown
    Observation source
    current_state_backfill
    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:48:13.000000
    Evidence SHA-256
    02dbcfaa52f322632771ec81c8aaf7be89e218f9b46e9867b0ff99c627a0b1bd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:48:13
    Evidence reason
  18. 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-10-31 23:48:13.000000
    Evidence SHA-256
    02dbcfaa52f322632771ec81c8aaf7be89e218f9b46e9867b0ff99c627a0b1bd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:48:13
    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-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
  20. 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 · in progress

Recorded events: 13. 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
    rntb-xaman.app detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · OTX Community References · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 11 of 11
  • 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: 2/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Automated brand label: Ledger
    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.
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

5 entries
  1. AlienVault OTX

    1 community references

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    rntb-xaman.app

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

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

Lookalike domains

151 stored lookalike domains

Source: dnstwist_results. These are saved variants of target domains. Selection may use older collector labels whose own observation date was not retained. It does not establish impersonation, common ownership or current availability. Dates belong to dnstwist observations; the legacy timezone is not established.

dnstwist_results #601 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledfger.com insertion Internal report A 185.244.151.84MX ledfger.comNS ns3.ro.hostsailor.com dnstwist_results #603 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgfer.com insertion Internal report A 185.244.151.84MX ledgfer.comNS ns3.ro.hostsailor.com dnstwist_results #604 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgher.com insertion Internal report A 185.244.151.84MX ledgher.comNS ns3.ro.hostsailor.com dnstwist_results #640 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgrr.com replacement Internal report A 185.244.151.84MX ledgrr.comNS ns3.ro.hostsailor.com dnstwist_results #609 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lefdger.com insertion Internal report A 185.244.151.84MX lefdger.comNS ns3.ro.hostsailor.com dnstwist_results #611 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lesdger.com insertion Internal report A 185.244.151.84MX lesdger.comNS ns3.ro.hostsailor.com dnstwist_results #613 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lkedger.com insertion Internal report A 185.244.151.84MX lkedger.comNS ns3.ro.hostsailor.com dnstwist_results #614 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lredger.com insertion Internal report A 185.244.151.84MX lredger.comNS ns3.ro.hostsailor.com dnstwist_results #615 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lwedger.com insertion Internal report A 185.244.151.84MX lwedger.comNS ns3.ro.hostsailor.com dnstwist_results #592 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 xn--ledgr-9za.com homoglyph Internal report NS ns-cloud-d1.googledomains.com dnstwist_results #524 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:33 · Last: 2026-03-17 13:39:33 ledgerk.com addition Internal report A 156.250.67.229NS ns1.bdydns.cn dnstwist_results #624 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 edger.com omission A 54.215.31.113NS ns1.dyna-ns.net
Show all (88)
dnstwist_results #652 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 eldger.com transposition A 185.244.151.84MX eldger.comNS ns3.ro.hostsailor.com dnstwist_results #634 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 kedger.com replacement A 13.56.33.8NS ns1.brandbucket.com dnstwist_results #617 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 kledger.com insertion A 20.65.18.151NS ns-1490.awsdns-58.org dnstwist_results #644 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 l3dger.com replacement A 216.198.79.1MX inbound-smtp.eu-west-1.amazonaws.comNS ns1.bluehost.com dnstwist_results #653 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ldeger.com transposition A 185.244.151.84MX ldeger.comNS ns3.ro.hostsailor.com dnstwist_results #621 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ldger.com omission A 13.248.169.48NS ns1.dan.com dnstwist_results #650 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 le.dger.com subdomain A 13.248.169.48NS ns5.afternic.com dnstwist_results #635 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lecger.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #630 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledber.com replacement A 104.21.35.54NS chin.ns.cloudflare.com dnstwist_results #654 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledegr.com transposition A 185.244.151.84MX ledegr.comNS ns3.ro.hostsailor.com dnstwist_results #626 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 leder.com omission A 85.13.132.113MX w01a4668.kasserver.comNS ns5.kasserver.com dnstwist_results #649 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledg3r.com replacement NS ns1.dreamhost.com dnstwist_results #625 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledge.com omission A 54.215.31.113NS ns1.dyna-ns.net dnstwist_results #646 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledged.com replacement A 52.20.84.62NS ns1.atom.com dnstwist_results #619 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgedr.com insertion A 31.43.160.6NS ns6.wixdns.net dnstwist_results #631 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgee.com replacement A 13.248.169.48NS ns3.afternic.com dnstwist_results #629 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgeer.com repetition A 52.20.84.62NS ns1.squadhelp.com dnstwist_results #656 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgercom.com various A 91.215.86.207NS ns3.epik.com dnstwist_results #632 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledget.com replacement A 13.248.169.48NS ns1.afternic.com dnstwist_results #602 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgewr.com insertion A 185.244.151.84MX ledgewr.comNS ns3.ro.hostsailor.com dnstwist_results #627 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgger.com repetition A 13.56.33.8NS ns1.brandbucket.com dnstwist_results #659 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgir.com vowel-swap A 188.114.96.3NS lynn.ns.cloudflare.com dnstwist_results #657 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgor.com vowel-swap A 103.230.136.195MX mxn.mxhichina.comNS ens11.bigwww.com dnstwist_results #622 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgr.com omission A 188.114.96.3NS kim.ns.cloudflare.com dnstwist_results #651 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgre.com transposition A 172.65.185.109NS sp1.gname-dns.com dnstwist_results #605 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgrer.com insertion A 185.244.151.84MX ledgrer.comNS ns3.ro.hostsailor.com dnstwist_results #636 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgsr.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #606 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgwer.com insertion A 185.244.151.84MX ledgwer.comNS ns3.ro.hostsailor.com dnstwist_results #641 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledgwr.com replacement A 185.244.151.84MX ledgwr.comNS ns3.ro.hostsailor.com dnstwist_results #639 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledher.com replacement A 15.197.148.33MX mailstore1.secureserver.netNS ns03.domaincontrol.com dnstwist_results #607 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledhger.com insertion A 185.244.151.84MX ledhger.comNS ns3.ro.hostsailor.com dnstwist_results #608 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledsger.com insertion A 185.244.151.84MX ledsger.comNS ns3.ro.hostsailor.com dnstwist_results #616 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledtger.com insertion A 188.114.96.3NS janet.ns.cloudflare.com dnstwist_results #645 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledyer.com replacement A 31.43.160.6MX alt1.aspmx.l.google.comNS ns-1051.awsdns-03.org dnstwist_results #643 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 ledzer.com replacement A 188.114.96.3NS kimora.ns.cloudflare.com dnstwist_results #620 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 leedger.com insertion MX mxbiz1.qq.comNS dns10.hichina.com dnstwist_results #655 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 legder.com transposition A 64.190.63.222MX localhostNS ns1.sedoparking.com dnstwist_results #623 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 leger.com omission A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dnstwist_results #610 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lerdger.com insertion A 185.244.151.84MX lerdger.comNS ns3.ro.hostsailor.com dnstwist_results #633 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lerger.com replacement A 13.248.169.48NS ns1.afternic.com dnstwist_results #642 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lesger.com replacement A 185.244.151.84MX lesger.comNS ns3.ro.hostsailor.com dnstwist_results #612 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lewdger.com insertion A 185.244.151.84MX lewdger.comNS ns3.ro.hostsailor.com dnstwist_results #660 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lidger.com vowel-swap A 66.241.124.184MX route1.mx.cloudflare.netNS erin.ns.cloudflare.com dnstwist_results #628 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lledger.com repetition A 50.254.19.65MX lledger-com.mail.protection.outlook.comNS ns-1532.awsdns-63.org dnstwist_results #658 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lodger.com vowel-swap A 149.210.148.65MX mail.lodger.comNS aron.ns.cloudflare.com dnstwist_results #648 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lrdger.com replacement A 77.247.179.85MX mail.h-email.netNS ns1.badgerdns.com dnstwist_results #637 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 lsdger.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #638 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 oedger.com replacement A 14.63.215.245NS ns1.hostname.net dnstwist_results #647 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 pedger.com replacement A 74.220.199.6 dnstwist_results #618 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:35 · Last: 2026-03-17 13:39:35 pledger.com insertion A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dnstwist_results #555 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 dedger.com bitsquatting MX aspmx1.migadu.comNS apollo.ns.cloudflare.com dnstwist_results #547 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 hedger.com bitsquatting A 15.197.225.128MX alt1.aspmx.l.google.comNS ns23.domaincontrol.com dnstwist_results #570 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 iedger.com homoglyph A 217.70.184.38MX fb.mail.gandi.netNS ns-157-c.gandi.net dnstwist_results #596 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 l-edger.com hyphenation A 216.198.79.65NS ns1.vercel-dns.com dnstwist_results #551 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ladger.com bitsquatting A 185.80.2.134MX ladger.comNS ns209.superhosting.bg dnstwist_results #591 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lcdlger.com homoglyph NS ns2.my-ndns.com dnstwist_results #544 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lddger.com bitsquatting A 14.63.215.245NS ns1.hostname.net dnstwist_results #560 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lebger.com homoglyph A 104.247.81.99NS ns1.parkingcrew.net dnstwist_results #589 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leclger.com homoglyph A 34.42.100.71NS ns-cloud-e1.googledomains.com dnstwist_results #546 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledcer.com bitsquatting A 15.197.148.33MX ledcer-com.mail.protection.outlook.comNS pdns11.domaincontrol.com dnstwist_results #598 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leddger.com insertion A 13.248.169.48NS ns1.afternic.com dnstwist_results #540 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledeer.com bitsquatting A 13.248.169.48NS ns1.dan.com dnstwist_results #597 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledeger.com insertion A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com dnstwist_results #545 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledfer.com bitsquatting A 15.197.142.173MX mailstore1.secureserver.netNS ns11.domaincontrol.com dnstwist_results #595 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledg-er.com hyphenation A 162.255.119.245MX mail.protonmail.chNS dns1.registrar-servers.com dnstwist_results #541 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgar.com bitsquatting A 13.248.169.48NS ns1.namefind.com dnstwist_results #530 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger0.com addition A 20.82.12.44MX ledger0-com.mail.protection.outlook.comNS ns1-04.azure-dns.com dnstwist_results #532 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger1.com addition A 44.232.173.249NS launch1.spaceship.net dnstwist_results #535 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger4.com addition A 52.201.53.166NS nsg1.namebrightdns.com dnstwist_results #538 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger5.com addition MX mail.protonmail.chNS ns-1175.awsdns-18.org dnstwist_results #533 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledger6.com addition A 52.20.84.62NS ns1.atom.com dnstwist_results #536 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerb.com addition A 91.195.240.82NS ns1dhl.name.com dnstwist_results #528 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerc.com addition A 198.185.159.144MX alt1.aspmx.l.google.comNS dns1.p02.nsone.net dnstwist_results #537 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerf.com addition A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com dnstwist_results #534 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgeri.com addition A 52.20.84.62NS ns1.atom.com dnstwist_results #527 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgern.com addition A 192.0.78.162MX ledgern-com.mail.protection.outlook.comNS ns1.wordpress.com dnstwist_results #531 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerq.com addition A 31.43.160.6MX ledgerq-com.mail.protection.outlook.comNS ns03.domaincontrol.com dnstwist_results #529 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgerx.com addition A 198.202.211.1MX usb-smtp-inbound-1.mimecast.comNS alla.ns.cloudflare.com dnstwist_results #549 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledges.com bitsquatting A 170.249.218.186MX ledges-com.mail.protection.outlook.comNS ns47.domaincontrol.com dnstwist_results #554 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgez.com bitsquatting A 67.23.254.40MX ledgez.comNS ns1.reseller-228.mco2.hostdime.com dnstwist_results #543 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledgur.com bitsquatting A 13.248.243.5MX ledgur-com.mail.protection.outlook.comNS ns23.domaincontrol.com dnstwist_results #565 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lediger.com homoglyph A 185.225.135.100MX mail02.lediger-consulting.deNS ns1.routing.net dnstwist_results #561 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ledqer.com homoglyph A 13.223.25.84NS nsg1.namebrightdns.com dnstwist_results #552 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leeger.com bitsquatting A 194.191.24.29MX alt1.aspmx.l.google.comNS cns1.cloudpit.de dnstwist_results #562 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 leelger.com homoglyph A 15.197.148.33NS ns69.domaincontrol.com dnstwist_results #539 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 lefger.com bitsquatting A 103.224.182.244MX park-mx.above.comNS ns1.abovedomains.com dnstwist_results #548 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 letger.com bitsquatting A 156.245.108.206NS ns1.dnsowl.com dnstwist_results #550 · Target: ledger.com · target_brand label · First: 2026-03-17 13:39:34 · Last: 2026-03-17 13:39:34 ludger.com bitsquatting A 18.195.62.85MX ludger-com.mail.protection.outlook.comNS ns11.worldnic.com

Showing 100 of 151

Check for cloaking

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

rntb-xaman.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 2 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 1 ref 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 rntb-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/rntb-xaman.app"
  title="PhishDestroy threat report for rntb-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>