Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 21/92 engines flagged. malicious: 20. suspicious: 1. Analysis time (as stored): 2026-11-03T14:30:10Z. Retrieved (as stored): 2026-11-05T02:32:03Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
provide-ask-rabbywallat.wasmer.app favicon

provide-ask-rabbywallat.wasmer.app

In short

The page at provide-ask-rabbywallat.wasmer.app displays a heading reading "Rabby Wallet – Web3 Made Understandable" on a light blue gradient background. Below it, a paragraph states that Rabby Wallet is designed to bring clarity and confidence to decentralized finance, citing a clean interface, intelligent transaction previews, and a focus on user awareness to help individuals interact with Web3 safely and comfortably. The lower portion of the captured view is empty white space with no further visible content.

“Rabby Wallet – Clear Intelligent Web3 Access”

Review the evidence
Registrar
Wasmer
Resolved IP
France51.178.223.162OVH SAS
Registered
Oct 16, 2018
First observed
Nov 2, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 21/92 Spamhaus DBL: phishing domain
VirusTotal
21 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 88
Cloudflare Radar
Phishing
Page captures
5
open gallery
Domain age
2,944 days
registered 2018-10-16 according to RDAP · source data differ
Nov 2, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded provide-ask-rabbywallat.wasmer.app on 2026-11-02. Stored VirusTotal result: 21/92 engines flagged. malicious: 20. suspicious: 1. Analysis time (as stored): 2026-11-03T14:30:10Z. Retrieved (as stored): 2026-11-05T02:32:03Z. Risk: critical (100/100). Registrar: Wasmer. Status: Last known active. Hosting: OVH SAS. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
21 / 92
Scam type (automated label)
Seed Phrase Theft
Hosting
France51.178.223.162OVH SAS
Registrar
Wasmer
Registered
Oct 16, 2018
Page captures
5
Page captures Source results Registration record

Capture recorded with this analysis · Cloudflare Radar · 2026-11-02T06:49:25Z
SHA-256: 05259d7168bf33d1aacfdf0c5f46029f6f40b1b7e0c602dd9f467d711c5dfc1f

PhishDestroy analysis, reviewed version

The page at provide-ask-rabbywallat.wasmer.app displays a heading reading "Rabby Wallet – Web3 Made Understandable" on a light blue gradient background. Below it, a paragraph states that Rabby Wallet is designed to bring clarity and confidence to decentralized finance, citing a clean interface, intelligent transaction previews, and a focus on user awareness to help individuals interact with Web3 safely and comfortably. The lower portion of the captured view is empty white space with no further visible content.

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

Source evidenceVirusTotal 21 / 92 8 sources

VirusTotal

21 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
20
Suspicious
1
Undetected
28

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
URLQuery
suspicious
Kaspersky
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
ChainPatrol
malicious
Criminal IP
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Squarespace Domains II LLC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    alpha.ns.wasmernet.com
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    abuse.wasmer.io
    Value
    alpha.ns.wasmernet.com
  • TTL, seconds
    180
    Type
    A
    Value
    5.161.23.223
  • TTL, seconds
    21600
    Type
    NS
    Value
    beta.ns.wasmernet.com
  • TTL, seconds
    180
    Type
    AAAA
    Value
    2a01:4ff:f2:dc2e::1

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d000000ed671e3ee2b845edc9fc88fa649a040a

Certificate

Subject alternative names
  • *.wasmer.app
Issuer
Let's Encrypt / YE1
Serial
5278a21b48e63a804ee28a8f9b97a7fb5c9
SHA-256
d59b7d7e6e97a39de60190c0e1c5a86c2630a28a9c4ba036abb0c8475aefadae
Subject
*.wasmer.app
Valid until
Valid from

Registration record

Registrar
Squarespace Domains II LLC
Registrar IANA ID
895
Registrar URL
domains.squarespace.com
Registered
Updated
Expires
Status
  • client
  • clientDeleteProhibited
  • clientTransferProhibited
Nameservers
  • alpha.ns.wasmernet.com
  • beta.ns.wasmernet.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 20,
    "suspicious": 1,
    "undetected": 28
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "URLQuery": "suspicious",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "ChainPatrol": "malicious",
    "Criminal IP": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Squarespace Domains II LLC
Created
2018-10-16T15:29:56Z
Expires
2025-10-16T15:29:56Z
Updated
2024-10-06T18:43:47Z
First seen
2026-03-23T10:49:01Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "alpha.ns.wasmernet.com"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "abuse.wasmer.io",
        "value": "alpha.ns.wasmernet.com"
    },
    {
        "ttl": 180,
        "type": "A",
        "value": "5.161.23.223"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "beta.ns.wasmernet.com"
    },
    {
        "ttl": 180,
        "type": "AAAA",
        "value": "2a01:4ff:f2:dc2e::1"
    }
]
Dns at
2026-11-03T14:30:28Z
Jarm
27d40d40d00040d00042d43d000000ed671e3ee2b845edc9fc88fa649a040a
Certificate
{
    "san": [
        "*.wasmer.app"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5278a21b48e63a804ee28a8f9b97a7fb5c9",
    "sha256": "d59b7d7e6e97a39de60190c0e1c5a86c2630a28a9c4ba036abb0c8475aefadae",
    "subject": "*.wasmer.app",
    "valid_to": "2027-01-11T12:09:19Z",
    "valid_from": "2026-10-13T12:09:20Z"
}
Registration record
{
    "registrar": "Squarespace Domains II LLC",
    "registrar_iana_id": "895",
    "registrar_url": "domains.squarespace.com",
    "created": "2018-10-16T15:29:56Z",
    "updated": "2024-10-01T18:43:47Z",
    "expires": "2025-10-16T15:29:56Z",
    "status": [
        "client",
        "clientDeleteProhibited",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "alpha.ns.wasmernet.com",
        "beta.ns.wasmernet.com"
    ],
    "dnssec": "unsigned"
}
Separate collector summary

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

source
VirusTotal
scope
unknown
result_state
observed
numerator
21
denominator
92
malicious
null
suspicious
null
vendors
["ChainPatrol","Criminal IP","alphaMountain.ai","BitDefender","Chong Lua Dao","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","LevelBlue","Lionic","Seclookup","SOCRadar","Sophos","URLQuery","VIPRE","Webroot"]
observed_at
2026-11-03 14:30:10
checked_at
2026-11-05 03:32:08
fetched_at
2026-11-05 02:32:09
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

97221546-ee88-49c7-96de-8f1ba6106c2f

Final URL

https://provide-ask-rabbywallat.wasmer.app/

HTTP response

200

Navigation history

  • URL
    https://provide-ask-rabbywallat.wasmer.app/
    Status
    200

DOM structure hash

07896049604507543b92b40105256e1c7906f520a733c31d305f868d9936214d

Document hash

96dc4dc88e7785c66563935a98fb010b576a58ccf0b391efe1ba641552528e7e

Phishing classifier result

  • phishing

Domain risk categories

  • Phishing
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    provide-ask-rabbywallat.wasmer.app
    Type
    A
    Value
    192.248.172.103
  • Name
    provide-ask-rabbywallat.wasmer.app
    Type
    AAAA
    Value
    2001:19f0:7400:1bc5:5400:5ff:fe96:7b8f

DNSSEC valid

No

IP address

127.0.1.8

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

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Squarespace Domains II LLC.
Registered
Updated
Expires
Nameservers
  • alpha.ns.wasmernet.com
  • beta.ns.wasmernet.com
Original source fields · JSON
Uuid
97221546-ee88-49c7-96de-8f1ba6106c2f
Final url
https://provide-ask-rabbywallat.wasmer.app/
Status
200
History
[
    {
        "url": "https://provide-ask-rabbywallat.wasmer.app/",
        "status": 200
    }
]
DOM structure hash
07896049604507543b92b40105256e1c7906f520a733c31d305f868d9936214d
Document hash
96dc4dc88e7785c66563935a98fb010b576a58ccf0b391efe1ba641552528e7e
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "provide-ask-rabbywallat.wasmer.app",
        "type": "A",
        "value": "192.248.172.103"
    },
    {
        "name": "provide-ask-rabbywallat.wasmer.app",
        "type": "AAAA",
        "value": "2001:19f0:7400:1bc5:5400:5ff:fe96:7b8f"
    }
]
Dnssec valid
false
Ip
127.0.1.8

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

Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Squarespace Domains II LLC.",
    "created": "2018-10-16T15:29:56Z",
    "updated": "2025-10-29T13:06:21Z",
    "expires": "2031-10-16T15:29:56Z",
    "nameservers": [
        "alpha.ns.wasmernet.com",
        "beta.ns.wasmernet.com"
    ]
}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 88

SHA-256 2adaa792b7d24967ab8815a03bb9eccb3519302cc4bbd5b7515a2bface8cbc6d

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Report ID

01a19aff-6f25-7753-9e59-aed8e9c0f384

Final URL

https://provide-ask-rabbywallat.wasmer.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://provide-ask-rabbywallat.wasmer.app/
    From
    http://provide-ask-rabbywallat.wasmer.app/
    Status
    307

IP address

51.178.223.162

Contacted domains

  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 192.178.183.94
  • 192.178.183.95
  • 51.178.223.162

Autonomous systems (ASN)

  • 15169
  • 16276

Server countries

  • US
  • FR

Document hash

96dc4dc88e7785c66563935a98fb010b576a58ccf0b391efe1ba641552528e7e

JavaScript globals

  • sections
  • reveal

TLS session and certificate

Subject alternative names
  • *.wasmer.app
Cipher
AES_128_GCM
Issuer
YE1
Subject
*.wasmer.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

223

Differs from the registration date in RDAP (2018-10-16), which gives 2938 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1446

Differs from the registration date in RDAP (2018-10-16), which gives 2938 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Certificate age, days

19

Certificate validity, days

89

Page requests

5

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
88
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a19aff-6f25-7753-9e59-aed8e9c0f384
Final url
https://provide-ask-rabbywallat.wasmer.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://provide-ask-rabbywallat.wasmer.app/",
        "from": "http://provide-ask-rabbywallat.wasmer.app/",
        "status": 307
    }
]
Ip
51.178.223.162
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "192.178.183.94",
    "192.178.183.95",
    "51.178.223.162"
]
Asns
[
    "15169",
    "16276"
]
Countries
[
    "US",
    "FR"
]
Document hash
96dc4dc88e7785c66563935a98fb010b576a58ccf0b391efe1ba641552528e7e
Globals
[
    "sections",
    "reveal"
]
Tls
{
    "san": [
        "*.wasmer.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "*.wasmer.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-11T12:09:19Z",
    "valid_from": "2026-10-13T12:09:20Z"
}
Domain age days
223

Differs from the registration date in RDAP (2018-10-16), which gives 2938 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Apex age days
1446

Differs from the registration date in RDAP (2018-10-16), which gives 2938 days on the scan date 2026-11-02. The two sources disagree; both values are kept as recorded.

Tls age days
19
Tls valid days
89
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 88,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-11-08 04:31 UTC

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

record_source
domain_monitor.urlscan
uuid
01a19aff-6f25-7753-9e59-aed8e9c0f384
score
0
malicious
false
result_at
2026-11-08T04:31:11Z
enriched_at
2026-11-02T09:10:41Z
source_timestamps
{"urlscan_result_at":"2026-11-08 05:31:11","urlscan_enriched_at":"2026-11-02 10:10:41"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

70 / 100 · heuristic score · 2 brand references · 1 classification

Open report
Separate monitor score · 70 / 100 · 2026-11-02T07:20:09Z

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
70
analyzed_at
2026-11-02T07:20:09Z
source_timestamp
2026-11-02 08:20:09
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
provide-ask-rabbywallat.wasmer.app – Rabby Wallet Web3 landing page
ai_description
PhishDestroy records the page at provide-ask-rabbywallat.wasmer.app, a Rabby Wallet landing page describing Web3 clarity, transaction previews, and user awareness.
ai_summary
The page at provide-ask-rabbywallat.wasmer.app displays a heading reading "Rabby Wallet – Web3 Made Understandable" on a light blue gradient background. Below it, a paragraph states that Rabby Wallet is designed to bring clarity and confidence to decentralized finance, citing a clean interface, intelligent transaction previews, and a focus on user awareness to help individuals interact with Web3 safely and comfortably. The lower portion of the captured view is empty white space with no further visible content. The stored VirusTotal domain result reports 21 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-05 03:39:14
revision
66ed48a6560ec1b8b57f02c0952807eeb58ec0d40591672fdfd642fb4066657b
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: 19 fields

CAA records

Domain
provide-ask-rabbywallat.wasmer.app

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
Rabby Wallet – Clear Intelligent Web3 Access
Description
Rabby Wallet delivers a clean, intelligent, and secure way to interact with Web3 using transparent transaction previews and user-first design.

Trackers

Requests
4
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
14
TLS
24
Waiting
34
Connection
23
Download
1
Response time, ms
96

TLS connection

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

Ports

Open ports
  • 22
  • 53
  • 80
  • 443

Carbon estimate

Bytes
6295
CO₂, grams
0.0002
Cleaner than, %
82

DNS servers

Nameservers
  • IP address
    51.178.223.162
    Host
    beta.ns.wasmernet.com
  • IP address
    141.94.10.243
    Host
    alpha.ns.wasmernet.com
DNS zone
provide-ask-rabbywallat.wasmer.app

Location

IP address
2001:41d0:20a:800::fa3
ASN
16276
Organization
OVH SAS
City
Wattrelos
Country
FR

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
*.wasmer.app

DNS records

A
  • 51.178.223.162
NS
  • alpha.ns.wasmernet.com
  • beta.ns.wasmernet.com
SOA
Primary nameserver
alpha.ns.wasmernet.com
Hostmaster
abuse.wasmer.io
Serial
1
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
300
AAAA
  • 2001:41d0:20a:800::fa3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2001:41d0:20a:800::fa3
IP version
6

Redirects

Redirect chain
  • https://provide-ask-rabbywallat.wasmer.app

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Original source fields · JSON
Caa records
{
    "domain": "provide-ask-rabbywallat.wasmer.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "Rabby Wallet – Clear Intelligent Web3 Access",
    "description": "Rabby Wallet delivers a clean, intelligent, and secure way to interact with Web3 using transparent transaction previews and user-first design."
}
Trackers
{
    "requests": 4,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 14,
        "tls": 24,
        "wait": 34,
        "connect": 23,
        "download": 1
    },
    "response_ms": 96
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        53,
        80,
        443
    ]
}
Carbon
{
    "bytes": 6295,
    "co2_grams": 0.0002,
    "cleaner_than": 82
}
Dns server
{
    "ns": [
        {
            "ip": "51.178.223.162",
            "host": "beta.ns.wasmernet.com"
        },
        {
            "ip": "141.94.10.243",
            "host": "alpha.ns.wasmernet.com"
        }
    ],
    "zone": "provide-ask-rabbywallat.wasmer.app"
}
Location
{
    "ip": "2001:41d0:20a:800::fa3",
    "asn": "16276",
    "org": "OVH SAS",
    "city": "Wattrelos",
    "country": "FR"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "*.wasmer.app"
}
DNS records
{
    "A": [
        "51.178.223.162"
    ],
    "NS": [
        "alpha.ns.wasmernet.com",
        "beta.ns.wasmernet.com"
    ],
    "SOA": "{\"nsname\": \"alpha.ns.wasmernet.com\", \"hostmaster\": \"abuse.wasmer.io\", \"serial\": 1, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 300}",
    "AAAA": [
        "2001:41d0:20a:800::fa3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2001:41d0:20a:800::fa3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://provide-ask-rabbywallat.wasmer.app"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing
View full Cloudflare Radar report

Questions about provide-ask-rabbywallat.wasmer.app

Is provide-ask-rabbywallat.wasmer.app legit?

PhishDestroy rates provide-ask-rabbywallat.wasmer.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-02. Stored VirusTotal result: 21/92 engines flagged. malicious: 20. suspicious: 1. Analysis time (as stored): 2026-11-03T14:30:10Z. Retrieved (as stored): 2026-11-05T02:32:03Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is provide-ask-rabbywallat.wasmer.app safe to connect a wallet?

This report does not record which wallet requests provide-ask-rabbywallat.wasmer.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 provide-ask-rabbywallat.wasmer.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 matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 5 captures

Cloudflare Radar 1 / 5 Used in the analysis Source file SHA-256: 05259d7168bf33d1aacfdf0c5f46029f6f40b1b7e0c602dd9f467d711c5dfc1f SHA-256 of the prepared copy given to the model: 78919acab85209cab32175a118fea43b0d0e0defdd2086ab9a0f18fdcebde556
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://provide-ask-rabbywallat.wasmer.app/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)
Observed page title
Rabby Wallet – Clear Intelligent Web3 Access
Automated brand references
Across Rabby
TLS Certificate
Issued by YE1 · stored validity ends in 64 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 88 report ↗
IP Reputation France51.178.223.162 abuse score 0/100 0 reports checked Nov 2, 2026
Registrar (base domain) Wasmer
Abuse contactabuse@wasmer.io, abuse@ovh.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wasmer.app →
Hosting abuse contact abuse@ovh.net OVH SAS · AS16276
Registration (base domain)wasmer.app · Created Oct 16, 2018 — Expires Oct 16, 2025
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 2, 2026
DOM Analysisanalyzed Nov 2, 2026score 70/1002 brand signals
Submitted URLhttp://provide-ask-rabbywallat.wasmer.app/
Favicon Hash
ICANN OVERSIGHT Registration: wasmer.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain wasmer.app behind this subdomain, 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

Resolved IP
France51.178.223.162
Network ASN
AS16276
AS name
OVH OVH SAS, FR
Organization
OVH SAS
Observed location
FranceWattrelos, FR
Server header
ESF

Nameservers 2

  • alpha.ns.wasmernet.com
  • beta.ns.wasmernet.com

SOA

  • nsname: alpha.ns.wasmernet.com
  • hostmaster: abuse.wasmer.io
  • serial: 1
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 300

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-13 12:09:20
Valid until
2027-01-11 12:09:19
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintd59b7d7e6e97a39de60190c0e1c5a86c2630a28a9c4ba036abb0c8475aefadae
Certificate names · 1 SAN
  • *.wasmer.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 · 51.178.223.162rapiddns.io

Latest Classified Outcome 2026-11-07 23:11:51 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-07 23:11:51 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 11:10:31 UTC last content: 2026-11-07 11:10:31 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

21 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 21 detections
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
URLQuery
Kaspersky
LevelBlue
Seclookup
Gridinsoft
BitDefender
ChainPatrol
Criminal IP
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of provide-ask-rabbywallat.wasmer.app · checked Nov 2, 2026

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

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

Archived HTTP response HTTP 403
Requested URL: http://provide-ask-rabbywallat.wasmer.app/
Response
HTTP 403
HTML body
514 B
Compressed
170 B
Links
0 internal · 0 external
Selected response headers
Server: Cisco Umbrella
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 5
Connection
keep-alive
Content-Type
text/html
Date
Wed, 04 Nov 2026 21:57:15 GMT
Server
Cisco Umbrella
Transfer-Encoding
chunked

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: 5 SHA-256 hashes: 5 URLScan scan:

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

Open this scan on URLScan 01a19aff-6f25-7753-9e59-aed8e9c0f384 ↗

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

    live_content

    content_served

  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 observations21

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-08 00:11:51.000000
    Evidence SHA-256
    c2d97d9dd2ba544b34d319d363945f654f3a2b95eece5a23ecebfcfcaf31bf04
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:11:51
    Evidence reason
    alive_content
  2. 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-07 12:10:31.000000
    Evidence SHA-256
    44bc191b258b69e535e605004b951e3794bf31248472156d310b9963419eca20
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:10:31
    Evidence reason
    alive_content
  3. 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-07 12:10:31.000000
    Evidence SHA-256
    44bc191b258b69e535e605004b951e3794bf31248472156d310b9963419eca20
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:10:31
    Evidence reason
    alive_content
  4. 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-07 11:22:04.554093
    Evidence SHA-256
    d0d729b70687a3b7d23361551b91f9c7b204c4eac655fb0a10da8512b094b9d2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 11:22:04.554093
    Evidence reason
  5. 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-07 03:49:39.000000
    Evidence SHA-256
    1df2f1dc176d38353698be9002367cca1ed6d13d564035a25facae6784d355af
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 03:49:39
    Evidence reason
    alive_content
  6. 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-07 03:49:39.000000
    Evidence SHA-256
    1df2f1dc176d38353698be9002367cca1ed6d13d564035a25facae6784d355af
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 03:49:39
    Evidence reason
    alive_content
  7. 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-07 00:00:39.000000
    Evidence SHA-256
    b09b712c684819c65bb726acbf17ff6211a702f208ef3b08f2094c2b7d138450
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:00:39
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 00:00:39.000000
    Evidence SHA-256
    b09b712c684819c65bb726acbf17ff6211a702f208ef3b08f2094c2b7d138450
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:00:39
    Evidence reason
    alive_content
  9. 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-06 11:21:21.802256
    Evidence SHA-256
    1f12882395a474d0dfb24be8d84353a7af90bb8bd997a0dda9b412ed89cd7a3f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 11:21:21.802256
    Evidence reason
  10. 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-05 11:21:21.318386
    Evidence SHA-256
    547991b570db3c8269bee0185b7fa12df05c0b418f4b7a797fb4d0bb740e4f46
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 11:21:21.318386
    Evidence reason
  11. 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-05 00:57:07.000000
    Evidence SHA-256
    23a717122b341d55a6f49bea6787a4b16519f78b66ee448996e5548bd565e5cb
    Evidence timestamp as recorded
    2026-11-05 00:57:07
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  12. 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 00:57:07.000000
    Evidence SHA-256
    73a478a5ae2c59b8f3015faf5785279d474b1d25eacb4fe7df45bdf655ebbd6b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 00:57:07
    Evidence reason
    alive_content
  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-04 12:56:33.000000
    Evidence SHA-256
    e11c4da50faed87e8bc3245629e1d190b197441b84bf63fa25d4dfb9461227d8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:56:33
    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-04 12:56:33.000000
    Evidence SHA-256
    e11c4da50faed87e8bc3245629e1d190b197441b84bf63fa25d4dfb9461227d8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 12:56:33
    Evidence reason
    alive_content
  15. 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 11:21:00.849465
    Evidence SHA-256
    94a9ae3d707b6cefa8168740bcb51c53137079a19bc0cd5bd77154e93c534a76
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 11:21:00.849465
    Evidence reason
  16. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 11:20:42.213040
    Evidence SHA-256
    7f511289ea6b6d1520a698f000d7fb3be1609f5f14dbf5ab5bf1c58eb4dbb974
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 11:20:42.213040
    Evidence reason
  17. 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 13:07:44.000000
    Evidence SHA-256
    0cd868c47a6390874cc65975d9ea7266a13f4997246598ea4cafdcc7c6550bba
    Evidence timestamp as recorded
    2026-11-02 13:07:44
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  18. 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 13:07:44.000000
    Evidence SHA-256
    d423aa9d6e21e243ea9cf59232100ef0cd17921eb22bbb5e025bcd0101884465
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 13:07:44
    Evidence reason
    alive_content
  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-11-02 11:20:40.834886
    Evidence SHA-256
    6b72dd67b3184766be6163de1e7b9604e36c85641b1d2618e2bdbe21069459a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 11:20:40.834886
    Evidence reason
  20. 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-11-02 07:45:16.000000
    Evidence SHA-256
    c718d74d4383bb367cc2991a5761e65b9c409dc1ab361b7774c14cd353baca82
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 07:45:16
    Evidence reason
  21. 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-11-02 07:45:16.000000
    Evidence SHA-256
    c718d74d4383bb367cc2991a5761e65b9c409dc1ab361b7774c14cd353baca82
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 07:45:16
    Evidence reason

Threat Response Pipeline

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

Recorded events: 12. 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
    provide-ask-rabbywallat.wasmer.app detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: Rabby · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 10 of 10
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 88
  • 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: 21/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Security threats, phishing
  • Automated brand label: Rabby
    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. Wayback Machine

    Page archived

    View source
  2. VirusTotal

    21/92 engine detections

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Added to PhishDestroy

    provide-ask-rabbywallat.wasmer.app

    View source
  5. URLScan

    Page captured

    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

20 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 #667 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 abby.io omission A 13.248.169.48NS ns3.afternic.com dnstwist_results #672 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 dabby.io replacement A 165.245.184.182MX mx.zoho.comNS dns1.registrar-servers.com dnstwist_results #674 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 fabby.io replacement A 198.49.23.145MX smtp.google.comNS ns-cloud-a1.googledomains.com dnstwist_results #675 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 r.abby.io subdomain A 13.248.169.48NS ns3.afternic.com dnstwist_results #676 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 ra.bby.io subdomain A 13.248.169.48NS ns1.afternic.com dnstwist_results #677 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 rab.by.io subdomain A 3.139.159.151 dnstwist_results #669 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 rabb.io omission A 74.208.236.143MX mx00.ionos.comNS ns1024.ui-dns.com dnstwist_results #671 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 rabba.io replacement A 162.255.119.61MX eforward1.registrar-servers.comNS dns1.registrar-servers.com dnstwist_results #670 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 rabbu.io replacement A 15.197.204.56NS ns01.cashparking.com dnstwist_results #678 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 rabby-io.com various A 104.21.61.224NS diana.ns.cloudflare.com dnstwist_results #679 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 rabbyio.com various A 127.0.0.127NS ns3.my-ndns.com dnstwist_results #668 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 raby.io omission A 217.160.0.192MX alt1.aspmx.l.google.comNS ns1046.ui-dns.biz
Show all (8)
dnstwist_results #666 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 raddy.io homoglyph A 185.230.63.107MX alt1.aspmx.l.google.comNS ns4.wixdns.net dnstwist_results #665 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 ralbby.io homoglyph A 104.21.16.27NS jeremy.ns.cloudflare.com dnstwist_results #680 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 robby.io vowel-swap A 192.64.119.201MX eforward1.registrar-servers.comNS dns1.registrar-servers.com dnstwist_results #673 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:46 · Last: 2026-03-17 13:39:46 tabby.io replacement A 188.114.96.3MX alt1.aspmx.l.google.comNS aiden.ns.cloudflare.com dnstwist_results #662 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:45 · Last: 2026-03-17 13:39:45 babby.io bitsquatting A 192.195.77.68MX mx00.ionos.comNS ns1056.ui-dns.de dnstwist_results #661 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:45 · Last: 2026-03-17 13:39:45 rabbi.io bitsquatting A 13.248.169.48NS ns1.afternic.com dnstwist_results #663 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:45 · Last: 2026-03-17 13:39:45 rebby.io bitsquatting A 216.198.79.65MX rebby-io.mail.protection.outlook.comNS ns1.vercel-dns.com dnstwist_results #664 · Target: rabby.io · target_brand label · First: 2026-03-17 13:39:45 · Last: 2026-03-17 13:39:45 sabby.io bitsquatting A 94.231.108.28MX sabby-io.mail.protection.outlook.comNS ns1.curanet.dk

Check for cloaking

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

provide-ask-rabbywallat.wasmer.app

Evidence & External Reports

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

Were You Affected by This Site?

3 evidence signal groups linked 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 provide-ask-rabbywallat.wasmer.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/provide-ask-rabbywallat.wasmer.app"
  title="PhishDestroy threat report for provide-ask-rabbywallat.wasmer.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>