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

my-wallets.at

In short

my-wallets.at is a phishing page detected by PhishDestroy on 2026-10-23.

“Application placeholder”

Review the evidence
Registrar
NetherlandsHosting concepts
Resolved IP
Canada172.67.193.233Cloudflare, Inc. · CDN
Registered
Oct 5, 2026
First observed
Oct 23, 2026
PhishDestroy assessment Critical
93/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 6/92 Young domain: 22 days old
VirusTotal
6 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 58
Cloudflare Radar
Phishing
Page captures
5
open gallery
Domain age
22 days
OTX: 3 refs Oct 23, 2026 CDN
X Telegram API

Analysis

Domain summary

my-wallets.at is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (93/100). Registrar: Hosting concepts. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 6/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
6 / 92
Hosting
Canada172.67.193.233Cloudflare, Inc. · CDN
Registrar
NetherlandsHosting concepts
Registered
Oct 5, 2026
OTX
3 community refs
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added my-wallets.at to its internal blocklist on 2026-10-23 after an admin report. The recorded page title was “Application placeholder”, meaning no substantive content was available for analysis. The site returned HTTP 200 on the same date. The domain was first seen by PhishDestroy on 2026-10-23.

How the scam works

A domain classified as suspicious may be used for phishing, credential harvesting, or crypto‑related fraud, but no specific malicious behavior was observed on this page. The placeholder page provides no indication of a particular scheme, so the risk remains generic rather than tied to a concrete attack vector.

Evidence

VirusTotal scanned the domain on 2026-10-23 with 92 engines and reported 0 malicious or suspicious detections. Google Safe Browsing checked on 2026-10-23 and did not flag the URL. OTX listed three public pulses referencing the domain as of 2026-10-23. URLScan captured the page on 2026-10-23; its machine‑learning engine gave a malicious score of 58, but the overall verdict was non‑malicious. Cloudflare Radar marked the domain under “phishing” and noted it as a newly seen domain with security risks. PhishDestroy’s internal blocklist marks the domain as true.

Infrastructure

The domain was registered on 2026-10-05 through Hosting concepts B.V. / Registrar.eu, giving it a 14‑day age at observation. DNS records resolved to Cloudflare IPs 172.67.193.233 and 104.21.52.10, plus IPv6 addresses. The TLS certificate, issued by Let’s Encrypt on 2026-10-05, is valid until 2027-01-03 and covers *.my-wallets.at. No DNSSEC records were present. The hosting network is Cloudflare, Inc., recorded in Canada.

What to do

Do not submit credentials, wallet addresses, or private keys to the site. If any credentials were entered, change the associated passwords immediately. Organizations should block the domain or its resolved IPs at network perimeters and review recent access logs for connections to the recorded IPs. Continue monitoring the domain for content changes or reputation updates and treat any future activity as potentially malicious.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T04:01:36Z)URLScan screenshot (2026-10-23T02:11:24Z)URLScan capture reportURLScan screenshot (2026-10-23T03:22:06Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 6 / 92 · OTX 3 references 8 sources

VirusTotal

6 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
0
Suspicious
0
Undetected
37

Reputation score

0

Registrar

Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::ac43:c1e9
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    dan.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    jewel.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.193.233
  • TTL, seconds
    21600
    Type
    NS
    Value
    dan.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.52.10
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3032::6815:340a

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.my-wallets.at
  • my-wallets.at
Issuer
Let's Encrypt / YE1
Serial
53b865de6db3be8bb1f9c93aed75bf4849e
SHA-256
2c178a0248eb7ac61a2aadb409ac50f7608c8b8571c87290ec617fa3a025e975
Subject
my-wallets.at
Valid until
Valid from

Registration record

Registrar
Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
Registrar
Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )
First seen
2026-10-05T16:22:23Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:c1e9"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "dan.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "jewel.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.193.233"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "dan.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.52.10"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::6815:340a"
    }
]
Dns at
2026-10-23T02:48:07Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.my-wallets.at",
        "my-wallets.at"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "53b865de6db3be8bb1f9c93aed75bf4849e",
    "sha256": "2c178a0248eb7ac61a2aadb409ac50f7608c8b8571c87290ec617fa3a025e975",
    "subject": "my-wallets.at",
    "valid_to": "2027-01-03T12:09:28Z",
    "valid_from": "2026-10-05T12:09:29Z"
}
Registration record
{
    "registrar": "Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-23 02:42:43 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-23T02:42:43Z
fetched_at
2026-10-23T04:01:28Z
stats
{"timeout":0,"harmless":55,"malicious":0,"suspicious":0,"undetected":37}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

b590a138-a9a0-4543-b5f2-dbd4ff76cefb

Final URL

https://my-wallets.at/

HTTP response

200

Navigation history

  • URL
    https://my-wallets.at/
    Status
    200

DOM structure hash

7ae9687a6252eaf8bf44abd08791d8478b3233f04818c091a38d27f51725c3d5

Document hash

3a018289e1261bd84ec371e56c6ce5483b5c27ee46bfcac3194f892a5659dce3

Phishing classifier result

  • phishing

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    my-wallets.at
    Type
    A
    Value
    104.21.52.10
  • Name
    my-wallets.at
    Type
    A
    Value
    172.67.193.233
  • Name
    my-wallets.at
    Type
    AAAA
    Value
    2606:4700:3032::6815:340a
  • Name
    my-wallets.at
    Type
    AAAA
    Value
    2606:4700:3037::ac43:c1e9

DNSSEC valid

No

IP address

104.21.52.10

Registration record

Registrar
Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )
Registered
Updated
Nameservers
  • dan.ns.cloudflare.com
  • jewel.ns.cloudflare.com
Original source fields · JSON
Uuid
b590a138-a9a0-4543-b5f2-dbd4ff76cefb
Final url
https://my-wallets.at/
Status
200
History
[
    {
        "url": "https://my-wallets.at/",
        "status": 200
    }
]
DOM structure hash
7ae9687a6252eaf8bf44abd08791d8478b3233f04818c091a38d27f51725c3d5
Document hash
3a018289e1261bd84ec371e56c6ce5483b5c27ee46bfcac3194f892a5659dce3
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "my-wallets.at",
        "type": "A",
        "value": "104.21.52.10"
    },
    {
        "name": "my-wallets.at",
        "type": "A",
        "value": "172.67.193.233"
    },
    {
        "name": "my-wallets.at",
        "type": "AAAA",
        "value": "2606:4700:3032::6815:340a"
    },
    {
        "name": "my-wallets.at",
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:c1e9"
    }
]
Dnssec valid
false
Ip
104.21.52.10
Registration record
{
    "registrar": "Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )",
    "created": "2026-10-05T12:19:29Z",
    "updated": "2026-10-05T14:04:53Z",
    "nameservers": [
        "dan.ns.cloudflare.com",
        "jewel.ns.cloudflare.com"
    ]
}
Separate stored summary: suspicious · observation date not recorded

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

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

URLScan

Malicious · engine verdict · score 58

SHA-256 9ada7fc91d398e5d18f490c6822e4895a6a23dfffa1139fdaf55494a90a2c246

Open report
URLScanOriginal source recordObserved: 17 fields

Observed: · Retrieved:

Report ID

01a166ce-921a-7348-abe4-37eef7dfb442

Final URL

https://my-wallets.at/

HTTP response

200

IP address

172.67.193.233

Contacted domains

  • static.cloudflareinsights.com

Contacted IP addresses

  • 104.16.79.73
  • 172.67.193.233

Autonomous systems (ASN)

  • 13335

Document hash

3a018289e1261bd84ec371e56c6ce5483b5c27ee46bfcac3194f892a5659dce3

JavaScript globals

  • cycle
  • __cfBeacon
  • messages
  • index
  • msgEl

TLS session and certificate

Subject alternative names
  • *.my-wallets.at
  • my-wallets.at
Cipher
AES_128_GCM
Issuer
YE1
Subject
my-wallets.at
Protocol
QUIC
Valid until
Valid from

Domain age, days

14

Registered domain age, days

14

Certificate age, days

17

Certificate validity, days

89

Page requests

4

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a166ce-921a-7348-abe4-37eef7dfb442
Final url
https://my-wallets.at/
Status
200
Ip
172.67.193.233
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "172.67.193.233"
]
Asns
[
    "13335"
]
Document hash
3a018289e1261bd84ec371e56c6ce5483b5c27ee46bfcac3194f892a5659dce3
Globals
[
    "cycle",
    "__cfBeacon",
    "messages",
    "index",
    "msgEl"
]
Tls
{
    "san": [
        "*.my-wallets.at",
        "my-wallets.at"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "my-wallets.at",
    "protocol": "QUIC",
    "valid_to": "2027-01-03T12:09:28Z",
    "valid_from": "2026-10-05T12:09:29Z"
}
Domain age days
14
Apex age days
14
Tls age days
17
Tls valid days
89
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 58,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}

OTX

3 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 · 0 brand references · 0 classifications

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
my-wallets.at — Suspicious Domain
ai_description
PhishDestroy flagged my-wallets.at as a suspicious domain after observing only an “Application placeholder” page; no malicious content was detected.
ai_generated_at
2026-10-23T04:03:05Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 23 fields

Mail configuration

SPF lookups
0

CAA records

Domain
my-wallets.at

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.06
Average page size, bytes
2804

Page title and metadata

Page title
Application placeholder
Indexing directives
noindex,nofollow

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
4
TLS
62
Waiting
290
Connection
6
Download
8
Response time, ms
370

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
9900
CO₂, grams
0.0004
Cleaner than, %
72

DNS servers

Nameservers
  • IP address
    162.159.38.171
    Host
    jewel.ns.cloudflare.com
  • IP address
    173.245.59.108
    Host
    dan.ns.cloudflare.com
DNS zone
my-wallets.at

Location

IP address
2606:4700:3037::ac43:c1e9
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
my-wallets.at

DNS records

A
  • 104.21.52.10
  • 172.67.193.233
NS
  • jewel.ns.cloudflare.com
  • dan.ns.cloudflare.com
SOA
Primary nameserver
dan.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416698765
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:3037::ac43:c1e9
  • 2606:4700:3032::6815:340a

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

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3032::6815:340a
IP version
6

Redirects

Redirect chain
  • https://my-wallets.at

Registration record

Registrar
Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )
Registered
Updated
Nameservers
  • dan.ns.cloudflare.com
  • jewel.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "my-wallets.at"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T03:31:55Z",
    "first": "2026-10-05T20:41:16Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.06,
    "avg_page_bytes": 2804
}
Page title and metadata
{
    "title": "Application placeholder",
    "robots": "noindex,nofollow"
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 62,
        "wait": 290,
        "connect": 6,
        "download": 8
    },
    "response_ms": 370
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 9900,
    "co2_grams": 0.0004,
    "cleaner_than": 72
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.38.171",
            "host": "jewel.ns.cloudflare.com"
        },
        {
            "ip": "173.245.59.108",
            "host": "dan.ns.cloudflare.com"
        }
    ],
    "zone": "my-wallets.at"
}
Location
{
    "ip": "2606:4700:3037::ac43:c1e9",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "my-wallets.at"
}
DNS records
{
    "A": [
        "104.21.52.10",
        "172.67.193.233"
    ],
    "NS": [
        "jewel.ns.cloudflare.com",
        "dan.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"dan.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416698765, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2606:4700:3037::ac43:c1e9",
        "2606:4700:3032::6815:340a"
    ]
}
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
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3032::6815:340a",
    "family": 6
}
Redirects
{
    "chain": [
        "https://my-wallets.at"
    ]
}
Registration record
{
    "registrar": "Hosting concepts B.V. / Registrar.eu ( https://nic.at/registrar/648 )",
    "created": "2026-10-05T12:19:29Z",
    "updated": "2026-10-05T14:04:53Z",
    "nameservers": [
        "dan.ns.cloudflare.com",
        "jewel.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8"
    }
}

Questions about my-wallets.at

Is my-wallets.at legit?

No. PhishDestroy classifies my-wallets.at as a phishing page (risk: critical, 93/100); it was first detected on 2026-10-23. VirusTotal: 6/92 engines flag it. Treat the site as unsafe.

Is my-wallets.at safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on my-wallets.at. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used my-wallets.at?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. 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

Primary capture 1 / 5
SourcePrimary capture
Recorded
StateStored capture
Position1 / 5
Open capture Wayback Download
All capture links and hashes (5)
my-wallets.at: caution — 6/92 VirusTotal engines. PhishDestroy risk score 93/100 (critical).
Social preview card my-wallets.at: caution — 6/92 VirusTotal engines. PhishDestroy risk score 93/100 (critical). v 2e643b82c28d

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 58 report ↗
IP Context Canada172.67.193.233 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Hosting concepts NL(NL)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for my-wallets.at →
RegistrationCreated Oct 5, 2026 (22d · Very New!)
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 93/100
Submitted URLhttps://my-wallets.at/
Observed page title
Application placeholder
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 67 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.193.233
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dan.ns.cloudflare.com
  • jewel.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-05 12:09:29
Valid until
2027-01-03 12:09:28
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint2c178a0248eb7ac61a2aadb409ac50f7608c8b8571c87290ec617fa3a025e975
Certificate names · 2 SANs
  • *.my-wallets.at
  • my-wallets.at

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 172.67.193.233rapiddns.io

Latest Classified Outcome 2026-10-27 12:09:49 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-10-27 12:09:49 UTC
RDAP registration
Observed timeline last reachable: 2026-10-26 00:02:30 UTC last content: 2026-10-26 00:02:30 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

6 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
LevelBlue
SOCRadar
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of my-wallets.at · checked Oct 23, 2026

100
Good
Performance
FCP
0.77 s
First Contentful Paint
LCP
0.77 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
5 ms
Total Blocking Time
SI
0.97 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 200
Requested URL: https://my-wallets.at/
Application placeholder
Response
HTTP 200
HTML body
10.0 KB
Compressed
3.3 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4edab313b29f17b-GRU
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Fri, 23 Oct 2026 03:31:25 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=9BsJyMnvMbmj%2Bd8%2FgljNhIYs4p2Pff7Zbkm7J9Kmgs3jRC5d2H0YKboHp3uA6M7mIYJr3j6yRWe1e%2BTT8t7h8MMzl9ooQ1vKpNV85QQIx915qBDrIUogiwu3gZx%2F5TfW"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

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.

Stored observation history8

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. Domain monitor · Recorded state

    Unavailable→Reachable

Earlier observations 3
  1. Domain monitor · Recorded state

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-10-23 04:28:10
All retained availability observations25

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-10-27 13:09:49.000000
    Evidence SHA-256
    eacc03a23595c9e40ac6510976b8566b2564e8eabd7fe677da8f7e7f01f9ff96
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 13:09:49
    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-10-27 13:09:49.000000
    Evidence SHA-256
    eacc03a23595c9e40ac6510976b8566b2564e8eabd7fe677da8f7e7f01f9ff96
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 13:09:49
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 09:55:08.586816
    Evidence SHA-256
    fa8e9b8de0fa2ff3f2c60817f493162c8480eb1a7ff0a28e0a7abc823995c62f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 09:55:08.586816
    Evidence reason
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 05:02:52.000000
    Evidence SHA-256
    a6c974784e3d6f331dbead218a6b0ec24c296c49ba532684c44d770ba93ea633
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 05:02:52
    Evidence reason
    alive_content
  5. 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 05:02:52.000000
    Evidence SHA-256
    a6c974784e3d6f331dbead218a6b0ec24c296c49ba532684c44d770ba93ea633
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 05:02:52
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:59:21.000000
    Evidence SHA-256
    1a7f25a8ffad33dd59f435c90215226a7ce78c17d8db851533d79a0892cea0a8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:59:21
    Evidence reason
    alive_content
  7. 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 12:59:21.000000
    Evidence SHA-256
    1a7f25a8ffad33dd59f435c90215226a7ce78c17d8db851533d79a0892cea0a8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:59:21
    Evidence reason
    alive_content
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 09:55:08.299319
    Evidence SHA-256
    37b5c19af06da555fb6055130c267aaeda09ed615e57f17df294ffe2591f7ef9
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 09:55:08.299319
    Evidence reason
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 01:02:30.000000
    Evidence SHA-256
    dae4a873cb06af0ca95e388c310e1f6da2ad3e20d6f91f75d6be92b26cd6d295
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:02:30
    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-26 01:02:30.000000
    Evidence SHA-256
    dae4a873cb06af0ca95e388c310e1f6da2ad3e20d6f91f75d6be92b26cd6d295
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 01:02:30
    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
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 13:04:49.000000
    Evidence SHA-256
    a5fd4e78994d31eff709031f5899887a6fdbf7666b436c425597a56d1b77963b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:04:49
    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-25 13:04:49.000000
    Evidence SHA-256
    a5fd4e78994d31eff709031f5899887a6fdbf7666b436c425597a56d1b77963b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 13:04:49
    Evidence reason
    alive_content
  13. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 09:55:07.418941
    Evidence SHA-256
    f29421045a2f0d44850c6f52d6d8bbdf0829af36630a6ed5c83feca2dfe013b6
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 09:55:07.418941
    Evidence reason
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:53:22.000000
    Evidence SHA-256
    8c4691d7ce776b0d730a5b43ed0ab3204919e9abfe81654858be6af9aa0ef4e0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:53:22
    Evidence reason
    alive_content
  15. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:53:22.000000
    Evidence SHA-256
    8c4691d7ce776b0d730a5b43ed0ab3204919e9abfe81654858be6af9aa0ef4e0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:53:22
    Evidence reason
    alive_content
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:56:16.000000
    Evidence SHA-256
    aec30ad132d7f9ae3b66eee249de317ca5a745a0f8930a61bf5eaba629475e8b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:56:16
    Evidence reason
    alive_content
  17. 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-24 12:56:16.000000
    Evidence SHA-256
    aec30ad132d7f9ae3b66eee249de317ca5a745a0f8930a61bf5eaba629475e8b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:56:16
    Evidence reason
    alive_content
  18. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 10:55:03.666169
    Evidence SHA-256
    3db3280361d0b0da230e0746730e29bf48f3dcd3dc85a990b2931515e779b43a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 10:55:03.666169
    Evidence reason
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 01:14:17.000000
    Evidence SHA-256
    ae522d5bdaa1b967bdcc90fc956d8d535b68ee8e9d1cd999ba9dce57ac434bb6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 01:14:17
    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-24 01:14:17.000000
    Evidence SHA-256
    ae522d5bdaa1b967bdcc90fc956d8d535b68ee8e9d1cd999ba9dce57ac434bb6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 01:14:17
    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
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 13:24:12.000000
    Evidence SHA-256
    f84e23ad28811b1a8fe1e56b48f43e67c3682bbd20a0c59f1e0135bbb95b44e0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 13:24:12
    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-23 13:24:12.000000
    Evidence SHA-256
    f84e23ad28811b1a8fe1e56b48f43e67c3682bbd20a0c59f1e0135bbb95b44e0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 13:24:12
    Evidence reason
    alive_content
  23. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 10:55:00.743425
    Evidence SHA-256
    13567a4852d2464d4e779931d6b58e9a7e4c364f8037d80b364e44546cdc66cf
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 10:55:00.743425
    Evidence reason
  24. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 05:30:33.000000
    Evidence SHA-256
    7f3fd73da818542e37dd5c0a9a6dbd7b8bc15a6dca9b6b954efa359a4e1ca655
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 05:30:33
    Evidence reason
  25. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 05:30:33.000000
    Evidence SHA-256
    7f3fd73da818542e37dd5c0a9a6dbd7b8bc15a6dca9b6b954efa359a4e1ca655
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 05:30:33
    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
    my-wallets.at detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · Site Came Back Online · Content Observed Unavailable Recorded: 10 of 10
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 58
  • 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: 6/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • Site Came Back Online
    The domain is responding again; monitoring resumed
  • Content Observed Unavailable
    Monitoring recorded an unavailable response (HTTP 200); the cause was not independently established.
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

6 entries
  1. VirusTotal

    6/92 engine detections

    View source
  2. AlienVault OTX

    3 community references

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    my-wallets.at

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

Check for cloaking

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

my-wallets.at

Evidence & External Reports

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

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

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 →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 my-wallets.at)
  • 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/my-wallets.at"
  title="PhishDestroy threat report for my-wallets.at"
  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>