VirusTotal
16 / 92 engine detections
Open report121z2.ralind.at is a Blockchain impersonation page detected by PhishDestroy on 2026-09-25. Risk: critical (100/100). Registrar: helloly. Status: Last known active. Hosting: AS56971 Cloud. PhishDestroy sent 1 abuse report. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Blockchain Payout Notification”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@cloudbackbone.net.
The latest stored availability evidence still shows the domain reachable; 27 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
16 / 92 engine detections
Open reportMalicious
Open reportDBL_PHISH
Malicious
Open reportScan report
Open reportno community references
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
121z2.ralind.at is an impersonation phishing page that poses as Blockchain under the title Blockchain Payout Notification. It targets people who hold crypto with Blockchain, or who might believe they are owed funds there. PhishDestroy first saw it on 2026-09-25. On 2026-10-19 the site was still alive and its content was reachable through a redirect, so the lure remains active.
A payout notification works on anticipation. The page tells the visitor that a Blockchain payout or balance is waiting and only needs to be claimed. Claiming it typically means signing in with Blockchain credentials and a 2FA code, typing in a wallet recovery phrase to verify ownership, or paying a small release or processing fee. Each of these hands value to the operators. Credentials allow account takeover, a recovery phrase gives them full control of the wallet, and the fee is simply kept. The promised payout never exists.
On 2026-10-07, 16 of 92 VirusTotal engines flagged the domain. They include BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, CRDF, CyRadar and alphaMountain.ai, a mix of major antivirus and web-filtering vendors that judged it independently. urlscan.io rated the page malicious and recognised Blockchain branding on it. Spamhaus lists the domain in its DBL as a phishing domain, and it is on the PhishDestroy blocklist.
The page sits on a throwaway-style subdomain of ralind.at, an Austrian .at domain registered through helloly GmbH. It is hosted in France on the AS56971 Cloud network. Its Let's Encrypt certificate comes from a free, automated service, so the padlock in the browser says nothing about whether the site is genuine.
Do not pay any fee to release a payout, and do not enter anything on this page. If you entered your Blockchain password or a 2FA code, change the password from the official app or site, reset 2FA, and review recent logins and withdrawals. If you typed in a recovery phrase, treat that wallet as compromised and move the funds to a newly created wallet at once. Defenders should block 121z2.ralind.at and the ralind.at parent at DNS and proxy level and alert users about fake Blockchain payout messages.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0d712-d629-7598-bffb-475ca636ec61 |
|---|---|
| Final url | https://121z2.ralind.at/trs/6Iqaws.php |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://121z2.ralind.at/trs/6Iqaws.php",
"from": "http://121z2.ralind.at/trs/6Iqaws.php",
"status": 307
}
] |
| Ip | 31.59.121.53 |
| Contacted domains | [
"cdn.jsdelivr.net",
"cdn.tailwindcss.com",
"code.jquery.com"
] |
| Contacted IP addresses | [
"151.101.193.229",
"151.101.1.155",
"104.26.3.143",
"31.59.121.53"
] |
| Asns | [
"54113",
"13335",
"56971"
] |
| Countries | [
"US",
"FR"
] |
| Document hash | 722cff51e23c74e476336458867784ff5bbc50fbbcb537f35131aa5f8f7d57a0 |
| Script hashes | [
"08fd87d46286ff16b870aa23975cb5051bc7c116fa4d88482bb8de3b95261d24",
"dcf10a2cb8c66e9073c172543bcbd5c903e29ae91a5beca9238a5e93d2f6b056"
] |
| Globals | [
"requestResize",
"page_id",
"CRedirectName",
"redirectLastPage",
"cookee_page_id",
"cookee_pages",
"pages",
"setCookie",
"readCookie",
"setPageCookie",
"readPageCookie",
"redirectPage",
"load",
"init",
"tailwind",
"$",
"jQuery",
"/template.html",
"navigateForward2"
] |
| Storage keys | [
"page_id_mirntk_blockpay2",
"pages",
"registered_date",
"balance"
] |
| Tls | {
"san": [
"*.ralind.at",
"ralind.at"
],
"cipher": "AES_256_GCM",
"issuer": "YR2",
"subject": "ralind.at",
"protocol": "TLS 1.3",
"valid_to": "2026-10-06T09:54:20Z",
"valid_from": "2026-07-08T09:54:21Z"
} |
| Domain age days | 18 |
| Apex age days | 179 |
| Tls age days | 78 |
| Tls valid days | 89 |
| Requests | 10 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 96,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"blockchain"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Blockchain"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html; charset=UTF-8"
} |
Observed: · Retrieved:
| Uuid | e5c89ae3-1438-4e99-923d-56d9272ddf46 |
|---|---|
| Final url | https://121z2.ralind.at/ |
| Status | 200 |
| History | [
{
"url": "https://121z2.ralind.at/",
"status": 200
}
] |
| DOM structure hash | a7fe83ec64bb23eb28090598db3d166ed98e52e39d1afbbfd74c579553f93e4e |
| Document hash | 5f04ae9ed6a865bb382c66ef4bd4e57df4ce19d4142b8c87ac40d65ae54d278f |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "121z2.ralind.at",
"type": "A",
"value": "31.59.121.53"
}
] |
| Dnssec valid | false |
| Ip | 31.59.121.53 |
| Verdict | {
"tags": [
"phishing"
],
"malicious": true,
"categories": [
"phishing"
]
} |
| Registration record | {
"registrar": "helloly GmbH ( https://nic.at/registrar/743 )",
"updated": "2026-04-15T12:52:13Z",
"nameservers": [
"a.dnspod.com",
"c.dnspod.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 0,
"suspicious": 0,
"undetected": 37
} |
|---|---|
| Reputation | 0 |
| Registrar | helloly GmbH ( https://nic.at/registrar/743 ) |
| First seen | 2026-09-22T19:07:09Z |
| DNS records | [
{
"ttl": 600,
"type": "A",
"value": "31.59.121.53"
}
] |
| Dns at | 2026-10-20T20:34:16Z |
| Jarm | 3fd3fd0003fd3fd00042d42d00000000f78d2dc0ce6e5bbc5b8149a4872356 |
| Certificate | {
"san": [
"121z2.ralind.at",
"www.121z2.ralind.at"
],
"issuer": "Let's Encrypt / YR1",
"serial": "672b729f8e41ed0eb99eda6159cc0cfb7b8",
"sha256": "a5b7fa7ade88f2c7d69f53f42864dda10fbe703a54e9c7a389f736d908dfcdbb",
"subject": "121z2.ralind.at",
"valid_to": "2027-01-10T13:25:47Z",
"valid_from": "2026-10-12T13:25:48Z"
} |
| Registration record | {
"registrar": "helloly GmbH ( https://nic.at/registrar/743 )"
} |
No. PhishDestroy classifies 121z2.ralind.at as a Blockchain impersonation page (risk: critical, 100/100); it was first detected on 2026-09-25. VirusTotal: 16/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on 121z2.ralind.at. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
a.dnspod.comc.dnspod.comLocation describes the IP network.
14aaa6eeb5a76065065872448fb21625b18e79166a5102f3e3b8d0e45a40fb0bralind.atSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of 121z2.ralind.at · checked Sep 25, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://121z2.ralind.at:443/; server=nginx
121z2.ralind.at
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
No threat flag
View source16/92 engine detections
View sourcePD-20260925-2EBF41
Page captured
View source121z2.ralind.at
View sourcePD-20260925-2EBF41 Recipient: abuse@cloudbackbone.net If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
121z2.ralind.at)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.