Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 18. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
dapp-walletnd.web.app favicon

dapp-walletnd.web.app

In short

PhishDestroy describes the DappWalletnode decentralized platform wallet page captured at dapp-walletnd.web.app.

“DappWalletnode”

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
United States199.36.158.100Fastly, Inc. · CDN
First observed
Oct 25, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 18/92
VirusTotal
18 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 99
Page captures
5
open gallery
Oct 25, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy describes the DappWalletnode decentralized platform wallet page captured at dapp-walletnd.web.app.

Critical
Status
Last known active
VirusTotal
18 / 92
Scam type (automated label)
Impersonation
Hosting
United States199.36.158.100Fastly, Inc. · CDN
Registrar
United StatesGoogle Domains
Page captures
5
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page at dapp-walletnd.web.app presents itself as DappWalletnode, a decentralized platform wallet. Its main interaction centers on wallet validation, with the page stating that validation of wallet will be completed below as follows, alongside sections labeled ratification, validation and recovery. The header offers navigation links for Home, Connect Dconnect, Contact us and FAQ, while an illustration of figures holding cubes accompanies the hero heading.

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

Source evidenceVirusTotal 18 / 92 7 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
18
Suspicious
0
Undetected
31

Vendor labels

DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Gridinsoft
phishing
ADMINUSLabs
malicious
BitDefender
phishing
Criminal IP
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing

Reputation score

0

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    A
    Value
    199.36.158.100
  • TTL, seconds
    21600
    Type
    AAAA
    Value
    2620:0:890::100

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • web.app
  • *.web.app
Issuer
Google Trust Services / WR4
Serial
e26d762a101120cd12a8f68d86c31d05
SHA-256
7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Subject
web.app
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.googledomains.com
  • ns2.googledomains.com
  • ns3.googledomains.com
  • ns4.googledomains.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 18,
    "suspicious": 0,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Gridinsoft": "phishing",
    "ADMINUSLabs": "malicious",
    "BitDefender": "phishing",
    "Criminal IP": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Registrar
MarkMonitor Inc.
Created
2019-01-08T22:05:04Z
Expires
2026-01-08T22:05:04Z
Updated
2024-12-12T10:14:49Z
First seen
2023-10-18T19:35:01Z
DNS records
[
    {
        "ttl": 21600,
        "type": "A",
        "value": "199.36.158.100"
    },
    {
        "ttl": 21600,
        "type": "AAAA",
        "value": "2620:0:890::100"
    }
]
Dns at
2026-10-26T00:05:43Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "issuer": "Google Trust Services / WR4",
    "serial": "e26d762a101120cd12a8f68d86c31d05",
    "sha256": "7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095",
    "subject": "web.app",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2019-01-08T22:05:04Z",
    "updated": "2024-12-12T10:14:49Z",
    "expires": "2026-01-08T22:05:04Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.googledomains.com",
        "ns2.googledomains.com",
        "ns3.googledomains.com",
        "ns4.googledomains.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 18 malicious + 0 suspicious / 92 · 2026-10-26 00:05:19 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-26T00:05:19Z
fetched_at
2026-10-31T02:31:15Z
stats
{"timeout":0,"harmless":43,"malicious":18,"suspicious":0,"undetected":31}

URLScan

Malicious · engine verdict · score 99

SHA-256 1c2896a626a5c15bac30a4aed3e88847495b985ed43917af110745d87f23e398

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1714a-e915-72f8-9cec-46643d469383

Final URL

https://dapp-walletnd.web.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://dapp-walletnd.web.app/
    From
    http://dapp-walletnd.web.app/
    Status
    307

IP address

199.36.158.100

Contacted domains

  • embed.tawk.to
  • va.tawk.to

Contacted IP addresses

  • 104.20.42.169
  • 199.36.158.100

Autonomous systems (ASN)

  • 13335
  • 54113

Server countries

  • US

Document hash

1c2896a626a5c15bac30a4aed3e88847495b985ed43917af110745d87f23e398

Script hashes

  • 2f7e5a91de6d1d362e648d46b5fe73a44287d72a49ea7bb2105f219d2efc162a
  • 5d591f9c15158c21f3878774299203f71ea6bfd2e3f986d82d4f99371c69aa18

JavaScript globals

  • Tawk_API
  • Tawk_LoadStart
  • webpackJsonpvasiti
  • $_Tawk_AccountKey
  • $_Tawk_WidgetId
  • $_Tawk_Unstable
  • $_Tawk
  • regeneratorRuntime
  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • $__TawkEngine
  • EventEmitter
  • $__TawkSocket
  • __i18next_supportNoticeShown

Cookies

  • twk_idm_key
  • TawkConnectionTime

Browser storage keys

  • exist_test

TLS session and certificate

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

Domain age, days

1183

Registered domain age, days

1183

Certificate age, days

31

Certificate validity, days

89

Page requests

20

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1714a-e915-72f8-9cec-46643d469383
Final url
https://dapp-walletnd.web.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://dapp-walletnd.web.app/",
        "from": "http://dapp-walletnd.web.app/",
        "status": 307
    }
]
Ip
199.36.158.100
Contacted domains
[
    "embed.tawk.to",
    "va.tawk.to"
]
Contacted IP addresses
[
    "104.20.42.169",
    "199.36.158.100"
]
Asns
[
    "13335",
    "54113"
]
Countries
[
    "US"
]
Document hash
1c2896a626a5c15bac30a4aed3e88847495b985ed43917af110745d87f23e398
Script hashes
[
    "2f7e5a91de6d1d362e648d46b5fe73a44287d72a49ea7bb2105f219d2efc162a",
    "5d591f9c15158c21f3878774299203f71ea6bfd2e3f986d82d4f99371c69aa18"
]
Globals
[
    "Tawk_API",
    "Tawk_LoadStart",
    "webpackJsonpvasiti",
    "$_Tawk_AccountKey",
    "$_Tawk_WidgetId",
    "$_Tawk_Unstable",
    "$_Tawk",
    "regeneratorRuntime",
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "$__TawkEngine",
    "EventEmitter",
    "$__TawkSocket",
    "__i18next_supportNoticeShown"
]
Cookies
[
    "twk_idm_key",
    "TawkConnectionTime"
]
Storage keys
[
    "exist_test"
]
Tls
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR4",
    "subject": "web.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Domain age days
1183
Apex age days
1183
Tls age days
31
Tls valid days
89
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
}
Separate monitor record · 2026-10-25 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a1714a-e915-72f8-9cec-46643d469383
score
0
malicious
false
result_at
2026-10-25T04:30:42Z
enriched_at
2026-10-25T09:11:42Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:42","urlscan_enriched_at":"2026-10-25 10:11:42"}
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

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

93 / 100 · heuristic score · 6 brand references · 1 classification

Open report
Separate monitor score · 10 / 100 · 2026-10-25T07:20:22Z

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
10
analyzed_at
2026-10-25T07:20:22Z
source_timestamp
2026-10-25 08:20:22
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
dapp-walletnd.web.app DappWalletnode decentralized platform wallet page
ai_description
PhishDestroy describes the DappWalletnode decentralized platform wallet page captured at dapp-walletnd.web.app.
ai_summary
The captured page at dapp-walletnd.web.app presents itself as DappWalletnode, a decentralized platform wallet. Its main interaction centers on wallet validation, with the page stating that validation of wallet will be completed below as follows, alongside sections labeled ratification, validation and recovery. The header offers navigation links for Home, Connect Dconnect, Contact us and FAQ, while an illustration of figures holding cubes accompanies the hero heading. The stored VirusTotal domain result reports 18 detections out of 92 engines. DNS8 reported "phishing"; ESET reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 03:31:51
revision
9279bd743a79a98ea5faba38e46c702092910e289e27aa5e9a8b0249f67ed9f3
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: 21 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
web.app
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
DappWalletnode
Theme color
#000000
Description
DappWalletnode

Trackers

Requests
14
Observed services
  • Name
    Tawk
    Company
    Tawk
    Country
    US
    Category
    Customer Interaction
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
41
TLS
21
Waiting
20
Connection
17
Download
0
Response time, ms
99

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
2603
CO₂, grams
0.0001
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    216.239.34.99
    Host
    ns2.googledomains.com
  • IP address
    216.239.32.99
    Host
    ns1.googledomains.com
  • IP address
    216.239.36.99
    Host
    ns3.googledomains.com
  • IP address
    216.239.38.99
    Host
    ns4.googledomains.com
DNS zone
web.app

Location

IP address
2620:0:890::100
ASN
54113
Organization
Fastly, Inc.
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
web.app

DNS records

A
  • 199.36.158.100
AAAA
  • 2620:0:890::100

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31556926; 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
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=31556926; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2620:0:890::100
IP version
6

Redirects

Redirect chain
  • https://dapp-walletnd.web.app

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "web.app",
    "issuers": [
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "DappWalletnode",
    "themeColor": "#000000",
    "description": "DappWalletnode"
}
Trackers
{
    "requests": 14,
    "trackers": [
        {
            "name": "Tawk",
            "company": "Tawk",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 41,
        "tls": 21,
        "wait": 20,
        "connect": 17,
        "download": 0
    },
    "response_ms": 99
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 2603,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.99",
            "host": "ns2.googledomains.com"
        },
        {
            "ip": "216.239.32.99",
            "host": "ns1.googledomains.com"
        },
        {
            "ip": "216.239.36.99",
            "host": "ns3.googledomains.com"
        },
        {
            "ip": "216.239.38.99",
            "host": "ns4.googledomains.com"
        }
    ],
    "zone": "web.app"
}
Location
{
    "ip": "2620:0:890::100",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "web.app"
}
DNS records
{
    "A": [
        "199.36.158.100"
    ],
    "AAAA": [
        "2620:0:890::100"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31556926; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31556926; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2620:0:890::100",
    "family": 6
}
Redirects
{
    "chain": [
        "https://dapp-walletnd.web.app"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
    }
}

Questions about dapp-walletnd.web.app

Is dapp-walletnd.web.app legit?

PhishDestroy describes the DappWalletnode decentralized platform wallet page captured at dapp-walletnd.web.app.

Is dapp-walletnd.web.app safe to connect a wallet?

This report does not record which wallet requests dapp-walletnd.web.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 dapp-walletnd.web.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

URLScan · 2026-10-25 1 / 5 Used in the analysis Source file SHA-256: 9ae05618099b0a4a89f348db4cf9dc83706b2a31c69378eb04bf84204722f97f SHA-256 of the prepared copy given to the model: 7ee3bc128fe5f285f5253ed0ce8a0eee83a633ff1f36ba72227964be84168aec
SourceURLScan · 2026-10-25
Recorded
StateStored capture
Final URLhttps://dapp-walletnd.web.app/
Position1 / 5
Open capture Source Report Wayback Download
All capture links and hashes (5)
dapp-walletnd.web.app: caution — 18/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card dapp-walletnd.web.app: caution — 18/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v ed6c9d4b639a

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Context United States199.36.158.100 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
Abuse contactnetwork-abuse@google.com, cloud-abuse@google.com
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 93/1006 brand signals
Submitted URLhttp://dapp-walletnd.web.app/
Favicon Hash
Observed page title
DappWalletnode
Automated brand references
Avalanche Ethereum Ledger Polygon Revolut Trezor
TLS Certificate
Issued by Google Trust Services / WR4 · stored validity ends in 51 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States199.36.158.100
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
Fastly, Inc.
Observed location
United StatesUS
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR4
Valid from
2026-09-23 17:59:58
Valid until
2026-12-22 17:59:57
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-25 05:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Certificate names · 1 SAN
  • web.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 · 199.36.158.100rapiddns.io

Latest Classified Outcome 2026-10-31 23:08:48 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: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 23:08:48 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:08:48 UTC last content: 2026-10-31 23:08:48 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

18 / 92 security vendors flagged this domain
View on VT
Last analyzed
ADMINUSLabs
Criminal IP
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
DNS8
ESET
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot
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: 20 SHA-256 hashes: 18 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:58 UTC.

Open this scan on URLScan 01a1714a-e915-72f8-9cec-46643d469383 ↗

Stored observation history2

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

    Reachable

All retained availability observations28

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
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:08:48.000000
    Evidence SHA-256
    ff8c55c9c0edb1e7b62c365c46fc0893f92ff627910a84e5c6e6d8a2ed4cc314
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:48
    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-01 00:08:48.000000
    Evidence SHA-256
    ff8c55c9c0edb1e7b62c365c46fc0893f92ff627910a84e5c6e6d8a2ed4cc314
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:08:48
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:31.000000
    Evidence SHA-256
    733d3af9e0bd3001facc781bf2cff506c9adf1ced585a26f4328f61c16a6acc8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:31
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:09:31.000000
    Evidence SHA-256
    733d3af9e0bd3001facc781bf2cff506c9adf1ced585a26f4328f61c16a6acc8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:09:31
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:30:38.000000
    Evidence SHA-256
    9ea6598920d40eec3ea18d377ff265c94cd02d99946511570f7a988eabdd4bc6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:38
    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-10-31 03:30:38.000000
    Evidence SHA-256
    9ea6598920d40eec3ea18d377ff265c94cd02d99946511570f7a988eabdd4bc6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:30:38
    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
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:06:54.000000
    Evidence SHA-256
    27277d09a4b71617d6e89cdaf110e1e8c335475c905c75eca5c18b06aafefb9d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:54
    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-10-30 12:06:54.000000
    Evidence SHA-256
    27277d09a4b71617d6e89cdaf110e1e8c335475c905c75eca5c18b06aafefb9d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:06:54
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:13.000000
    Evidence SHA-256
    329fd96b90110d4d4d8fb92c0d67eb6bdc5371b6387be2b86d8f1927c7b02914
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:13
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:07:13.000000
    Evidence SHA-256
    329fd96b90110d4d4d8fb92c0d67eb6bdc5371b6387be2b86d8f1927c7b02914
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:07:13
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:07:32.000000
    Evidence SHA-256
    08118107e0649983f902d02ae1c1fde20ee91518279146c0d60e3ed4d0e548c5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:32
    Evidence reason
    alive_content
  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-10-29 12:07:32.000000
    Evidence SHA-256
    08118107e0649983f902d02ae1c1fde20ee91518279146c0d60e3ed4d0e548c5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:07:32
    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
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:35:44.000000
    Evidence SHA-256
    bf972075bcdb830fe8fc6c1f707910a9dbdd0897f81cfcc40dfef39219b42f03
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:35:44
    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-10-29 03:35:44.000000
    Evidence SHA-256
    bf972075bcdb830fe8fc6c1f707910a9dbdd0897f81cfcc40dfef39219b42f03
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:35:44
    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
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:01:20.000000
    Evidence SHA-256
    6343fc5eb628b66aa63c7cf4b325ccb0f66fa89d523517b702208620e37e7381
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:20
    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-10-28 12:01:20.000000
    Evidence SHA-256
    6343fc5eb628b66aa63c7cf4b325ccb0f66fa89d523517b702208620e37e7381
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:01:20
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:01:48.000000
    Evidence SHA-256
    299817108c8562ee94c4f828a82720ef5f9543e76339133dcdd5723eaefb3800
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:01:48
    Evidence reason
    alive_content
  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-10-28 00:01:48.000000
    Evidence SHA-256
    299817108c8562ee94c4f828a82720ef5f9543e76339133dcdd5723eaefb3800
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:01:48
    Evidence reason
    alive_content
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:12.000000
    Evidence SHA-256
    8f5c3549aae35489582ec817cdb51de731c46a31a3af3e4e1f9cfc212b87099f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:12
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:02:12.000000
    Evidence SHA-256
    8f5c3549aae35489582ec817cdb51de731c46a31a3af3e4e1f9cfc212b87099f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:02:12
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:13.000000
    Evidence SHA-256
    ca5732ee2dd773b82c531649c7766589d9a922e9df0475cba09870ca59335ca2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:13
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 13:02:13.000000
    Evidence SHA-256
    ca5732ee2dd773b82c531649c7766589d9a922e9df0475cba09870ca59335ca2
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 13:02:13
    Evidence reason
    alive_content
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:14.000000
    Evidence SHA-256
    0355295960658a2fc27b01f931bffdf63f07e1ad6ddfa5bd4583fcd2aa4584cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:14
    Evidence reason
    alive_content
  24. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:19:14.000000
    Evidence SHA-256
    0355295960658a2fc27b01f931bffdf63f07e1ad6ddfa5bd4583fcd2aa4584cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:19:14
    Evidence reason
    alive_content
  25. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:46.000000
    Evidence SHA-256
    410a27afd2af3ce654241e5d2be12c458f36ec0e8545c039a3bccb21b9677f07
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:46
    Evidence reason
    alive_content
  26. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:22:46.000000
    Evidence SHA-256
    410a27afd2af3ce654241e5d2be12c458f36ec0e8545c039a3bccb21b9677f07
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:22:46
    Evidence reason
    alive_content
  27. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    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-25 05:22:57.000000
    Evidence SHA-256
    85194b5400e4b21f1b28c48181181e8c915d247f3b70c9d1ccf223eeb3dde5f8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 05:22:57
    Evidence reason
  28. 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-25 05:22:57.000000
    Evidence SHA-256
    85194b5400e4b21f1b28c48181181e8c915d247f3b70c9d1ccf223eeb3dde5f8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 05:22:57
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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
    dapp-walletnd.web.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · VirusTotal · Automated brand label: Ethereum · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • VirusTotal
    Detections recorded on VirusTotal: 18/92
  • Automated brand label: Ethereum
    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

3 entries
  1. VirusTotal

    18/92 engine detections

    View source
  2. Added to PhishDestroy

    dapp-walletnd.web.app

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

Lookalike domains

52 stored lookalike domains

ethercum.org homoglyph Internal report A 188.114.96.3NS bart.ns.cloudflare.com etheruem.org transposition Internal report A 212.99.218.66NS ns-1511.awsdns-60.org athereum.org bitsquatting A 199.188.200.6MX mail.athereum.orgNS dns1.namecheaphosting.com dethereum.org insertion A 216.198.79.1NS liv.ns.cloudflare.com e.thereum.org subdomain A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com efhereum.org replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ehereum.org omission A 15.197.225.128NS ns65.domaincontrol.com etereum.org omission A !ServFailNS !ServFail eth3reum.org replacement A 15.197.142.173NS ns31.domaincontrol.com ether.eum.org subdomain A 13.248.169.48NS ns1.afternic.com etheream.org vowel-swap A 162.255.119.154MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereim.org replacement A 15.197.142.173NS ns33.domaincontrol.com
Show all (40)
ethereium.org insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherem.org omission A 15.197.225.128NS ns39.domaincontrol.com etheremu.org transposition A 13.248.169.48NS ns1.afternic.com ethereom.org vowel-swap A 192.0.78.24NS ns1.wordpress.com etheresum.org insertion A 104.21.87.66NS aron.ns.cloudflare.com ethereujm.org insertion A 104.21.46.240NS jerry.ns.cloudflare.com ethereum2.org addition A 24.199.74.33NS ns3.namefi.io ethereum3.org addition NS a.share-dns.com ethereum4.org addition A 198.54.117.242NS failed-whois-verification.namecheap.com ethereumc.org addition A 188.114.96.3NS camilo.ns.cloudflare.com ethereumd.org addition A 188.114.96.3NS earl.ns.cloudflare.com ethereumorg.com various NS ns1.openprovider.nl ethereumr.org addition A 188.114.96.3NS monroe.ns.cloudflare.com ethereums.org addition A 15.197.148.33MX mailstore1.secureserver.netNS ns73.domaincontrol.com ethereumx.org addition A 64.190.63.222MX localhostNS ns1.sedoparking.com ethereun.org homoglyph A 52.20.84.62NS ns1.squadhelp.com ethereunm.org homoglyph A 104.21.86.145NS koa.ns.cloudflare.com ethereurm.org homoglyph A 188.114.96.3NS rita.ns.cloudflare.com ethereurn.org homoglyph MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereuym.org insertion A 104.21.22.142NS everton.ns.cloudflare.com ethereuzm.org insertion A 188.114.96.3NS dale.ns.cloudflare.com ethereyum.org insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherium.org vowel-swap A 32.216.8.188NS ns1.no-ip.com etherrum.org replacement MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etherteum.org insertion A 13.248.243.5NS ns41.domaincontrol.com etherum.org omission A 103.224.212.201MX park-mx.above.comNS ns1.abovedomains.com ethezeum.org bitsquatting A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethireum.org vowel-swap A 192.64.119.29MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethnereum.org insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethreum.org omission A 15.197.225.128NS ns65.domaincontrol.com ethureum.org bitsquatting A 162.255.119.109MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etihereum.org homoglyph A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ithereum.org vowel-swap A 188.114.96.3NS celine.ns.cloudflare.com othereum.org vowel-swap NS ns-cloud-a1.googledomains.com rethereum.org insertion A 54.36.108.60MX eforward1.registrar-servers.comNS dns1.registrar-servers.com sethereum.org insertion A !ServFailNS !ServFail thereum.org omission A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com uthereum.org bitsquatting A 15.197.148.33NS ns15.domaincontrol.com zethereum.org insertion NS ns-1335.awsdns-38.org zthereum.org replacement NS ns-1294.awsdns-33.org

Check for cloaking

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

dapp-walletnd.web.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 18 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch 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 dapp-walletnd.web.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/dapp-walletnd.web.app"
  title="PhishDestroy threat report for dapp-walletnd.web.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>