0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48Format validated · Domain analysisrdnhood.vercel.app
rdnhood.vercel.app is a Berachain impersonation page detected by PhishDestroy on 2026-10-22.
“Vote for Listing — Hood Wallet”
- Registrar
- Vercel
- Resolved IP
- 216.198.79.195
Record details & risk signals
Network Security Intelligence
Analysis
PhishDestroy threat report
rdnhood.vercel.app is a tenant hostname on Vercel, not a separately registered domain. PhishDestroy first observed the hostname on Oct 22, 2026. Stored content metadata identifies Berachain as the apparent target. The captured page title is “Vote for Listing — Hood Wallet”. Page analysis recorded additional brand references to Base, Dexscreener, Ethereum, Jito, Jupiter, Layerzero, Mantle, Raydium, Sui, Wormhole, and Zora. Stored page analysis classifies the content as crypto drainer. Current evidence score: 100/100 (critical).
Positive findings are stored from 7 sources: VirusTotal, MetaMask, ScamSniffer, SEAL, Google Safe Browsing, Cloudflare Radar, and URLScan. VirusTotal recorded 24 detections among 92 engines: ChainPatrol, alphaMountain.ai, BitDefender, CyRadar, DNS8, Ermes, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, Kaspersky, LevelBlue, Lionic, Netcraft, OpenPhish, PhishFort, SOCRadar, Sophos, URLQuery, VIPRE, Webroot on Oct 18, 2026 at 09:34 UTC. MetaMask, ScamSniffer, and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 25, 2026 at 03:20 UTC. Google Safe Browsing flagged the domain: Social Engineering on Oct 24, 2026 at 04:00 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category on Oct 24, 2026 at 14:20 UTC on Oct 24, 2026 at 14:20 UTC. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Robinhood and assigned phishing as its category on Oct 23, 2026 at 03:30 UTC.
HTTP 200 was recorded on Oct 25, 2026 at 02:54 UTC. Latest classified outcome: live content observed; cause content served on Oct 24, 2026 at 08:00 UTC. Vercel is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 216.198.79.195 on AS16509 (Amazon.com, Inc.). The IP and ASN identify shared Vercel infrastructure, not the tenant operator. DOM analysis on Oct 22, 2026 at 18:20 UTC returned 85/100. The evidence archive retains 7 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. IoC extraction on Oct 23, 2026 at 04:01 UTC retained 2 format-validated wallet addresses and 1 Telegram indicator. The platform TLS certificate was issued by Google Trust Services / WR1 with validity through Nov 27, 2026.
The content indicators and 7 positive source findings support the current Berachain-themed crypto drainer classification.
Source evidenceVirusTotal 24 / 92 · Google Safe Browsing: flagged 5 sources
| Source | Result | Recorded · UTC | Evidence |
|---|---|---|---|
VirusTotal | 24 / 92 engine detections | Open report | |
Cloudflare Radar | Phishing | Open report | |
Google Safe Browsing | Threat flag recorded | Open report | |
URLScan | Malicious | Open report | |
OTX | no community references | Open report | |
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Questions about rdnhood.vercel.app
Is rdnhood.vercel.app legit?
No. PhishDestroy classifies rdnhood.vercel.app as a Berachain impersonation page (risk: critical, 100/100); it was first detected on 2026-10-22. VirusTotal: 24/92 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.
Is rdnhood.vercel.app safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on rdnhood.vercel.app. 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 rdnhood.vercel.app?
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
Observed indicators
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0xeaf7ac0fdf150cdd89340fb762d83848de6a7b83Format validated · Domain analysishttps://t.me/share/urlStored page referenceIoC extraction recorded 2026-10-23 04:01:56 UTC
Blocklist matchesMetaMask · ScamSniffer · PhishDestroy · SEAL 4
Last checked
Network & certificates
Stored technical evidenceNetwork & DNS
Shared CDN edge- Resolved IP
- 216.198.79.195
- Network ASN
- AS16509
- Organization
- Vercel, Inc
- Observed location
- Walnut, US
- Server header
- Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
- Issuer
- Google Trust Services / WR1
- Valid from
- 2026-08-29 19:48:09
- Valid until
- 2026-11-27 19:48:08
- Hostname coverage
- Stored certificate dates valid
- Validity
- Within stored validity dates
- Collection source
- PhishDestroy collector
Certificate fingerprint
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093Certificate names · 1 SAN
*.vercel.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest Classified Outcome 2026-10-24 10:00:22 UTC
Technologies · 3 identified
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
VirusTotal Analysis
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.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
URLScan · 2026-10-22T17:38:02Z
Observed: · Retrieved:
| Uuid | 01a164b0-e30b-7115-9c7d-7892c2e0cf86 |
|---|---|
| Final url | https://rdnhood.vercel.app/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://rdnhood.vercel.app/",
"from": "http://rdnhood.vercel.app/",
"status": 307
}
] |
| Ip | 64.29.17.3 |
| Contacted domains | [
"lb.drpc.live",
"side-still-sky.megaeth-mainnet.quiknode.pro",
"side-still-sky.sei-pacific.quiknode.pro",
"evm-ws.sei-apis.com",
"cdn.jsdelivr.net",
"cdn.robinhood.com"
] |
| Contacted IP addresses | [
"104.17.208.5",
"18.66.102.52",
"64.29.17.3"
] |
| Asns | [
"13335",
"16509"
] |
| Countries | [
"US"
] |
| Document hash | a0ada193cf12f51958adca8307899187d98b94d7b4059099fb27d98e9fde9e0c |
| Script hashes | [
"e2fde6a6a7420492da1f9655943470bdee02110efbd3aa0725a1570e1cf40700"
] |
| Globals | [
"chainKeyFromDexId",
"extractAddress",
"addressFromUrl",
"setChain",
"detectChain",
"hashStr",
"votesFromAddr",
"votersFromAddr",
"shortAddr",
"formatUsd",
"formatPrice",
"formatSupply",
"updateMeta",
"setTemplateDescription",
"loadTokenData",
"fetchRealCandles",
"mulberry32",
"buildSyntheticPath",
"pointsToPath",
"renderChart",
"loadChart",
"animateNum",
"updateBar",
"startCountdown",
"genShortAddr",
"timeAgo",
"seedActivities",
"renderActivity",
"pushNewVote",
"scheduleNextVote",
"handleVote",
"closeVoteModal",
"connectWallet",
"showToast",
"getShareText",
"shareTwitter",
"shareTelegram",
"shareCopyLink",
"showNoTokenState",
"showUnknownTokenState"
] |
| Cookies | [
"__cflb"
] |
| Tls | {
"san": [
"*.vercel.app"
],
"cipher": "AES_128_GCM",
"issuer": "WR1",
"subject": "*.vercel.app",
"protocol": "TLS 1.3",
"valid_to": "2026-11-27T19:48:08Z",
"valid_from": "2026-08-29T19:48:09Z"
} |
| Domain age days | 88 |
| Apex age days | 88 |
| Tls age days | 53 |
| Tls valid days | 89 |
| Requests | 7 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"robinhood"
],
"malicious": true,
"categories": [
"phishing"
]
},
"urlscan": {
"tags": [
"phishing"
],
"score": 100,
"brands": [
"Robinhood"
],
"malicious": true,
"categories": [
"phishing"
]
}
} |
| HTTP headers | {
"server": "Vercel",
"content-type": "text/html; charset=utf-8",
"strict-transport-security": "max-age=63072000; includeSubDomains; preload"
} |
Cloudflare Radar · 2026-10-24T14:20:05Z
Observed: · Retrieved:
| Uuid | a619a392-a97a-46fc-b650-f42e31476253 |
|---|---|
| Final url | https://rdnhood.vercel.app/ |
| Status | 200 |
| History | [
{
"url": "https://rdnhood.vercel.app/",
"status": 200
}
] |
| DOM structure hash | 34309204cf146766c43283ac47ff15b76b6b4a0fa6ef44d96c3e28fedfe73084 |
| Document hash | a0ada193cf12f51958adca8307899187d98b94d7b4059099fb27d98e9fde9e0c |
| Phishing v2 | [
"phishing"
] |
| Url risks | [
"Phishing"
] |
| Domain risks | [
"Phishing",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "rdnhood.vercel.app",
"type": "A",
"value": "216.198.79.3"
},
{
"name": "rdnhood.vercel.app",
"type": "A",
"value": "64.29.17.3"
}
] |
| Dnssec valid | false |
| Ip | 216.198.79.3 |
| Verdict | {
"tags": [
"phishing"
],
"malicious": true,
"categories": [
"phishing"
]
} |
| Registration record | {
"registrar": "Tucows Domains Inc",
"created": "2020-01-28T03:03:04Z",
"updated": "2026-03-14T03:03:04Z",
"expires": "2036-01-28T03:03:04Z",
"nameservers": [
"ns1.vercel-dns-3.com",
"ns2.vercel-dns-3.com",
"ns3.vercel-dns-3.com",
"ns4.vercel-dns-3.com"
]
} |
VirusTotal · 2026-10-18T09:34:50Z
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 41,
"malicious": 20,
"suspicious": 4,
"undetected": 27
} |
|---|---|
| Vendor labels | {
"DNS8": "suspicious",
"ESET": "phishing",
"Ermes": "not recommended",
"VIPRE": "phishing",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"CyRadar": "phishing",
"Webroot": "malicious",
"Emsisoft": "phishing",
"Fortinet": "phishing",
"Netcraft": "malicious",
"SOCRadar": "suspicious",
"URLQuery": "malicious",
"Kaspersky": "phishing",
"LevelBlue": "phishing",
"OpenPhish": "phishing",
"PhishFort": "phishing",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"ChainPatrol": "malicious",
"alphaMountain.ai": "phishing",
"Google Safe Browsing": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Registrar | Tucows Domains Inc |
| Created | 2020-01-28T03:03:04Z |
| Expires | 2026-01-28T03:03:04Z |
| Updated | 2025-01-26T03:25:55Z |
| First seen | 2026-09-22T11:32:52Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "216.198.79.131"
},
{
"ttl": 300,
"type": "A",
"value": "64.29.17.131"
}
] |
| Dns at | 2026-10-18T09:35:03Z |
| Jarm | 3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb |
| Certificate | {
"san": [
"*.vercel.app"
],
"issuer": "Google Trust Services / WR1",
"serial": "f7911168ffa7d0f4135e24792e7a52a8",
"sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
"subject": "*.vercel.app",
"valid_to": "2026-11-27T19:48:08Z",
"valid_from": "2026-08-29T19:48:09Z"
} |
| Registration record | {
"registrar": "Tucows Domains Inc",
"registrar_iana_id": "69",
"registrar_url": "http://www.tucows.com",
"created": "2020-01-28T03:03:04Z",
"updated": "2025-01-26T03:25:55Z",
"expires": "2026-01-28T03:03:04Z",
"status": [
"clientTransferProhibited",
"clientUpdateProhibited"
],
"nameservers": [
"ns1.vercel-dns-3.com",
"ns2.vercel-dns-3.com",
"ns3.vercel-dns-3.com",
"ns4.vercel-dns-3.com"
],
"dnssec": "unsigned"
} |
Website checks · 2026-10-23T21:57:23Z
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"count": 2,
"domain": "vercel.app",
"issuers": [
"letsencrypt.org",
"pki.goog"
]
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Page title and metadata | {
"title": "Vote for Listing — Hood Wallet",
"ogType": "website",
"robots": "index, follow",
"ogImage": "http://rndconnect.cc/x.png",
"ogTitle": "Vote for Listing — Hood Wallet",
"description": "Vote for your favorite token to be listed on Hood Wallet. Community-driven token listing.",
"twitterCard": "summary_large_image",
"ogDescription": "Vote for your favorite token to be listed on Hood Wallet. Community-driven token listing."
} |
| Trackers | {
"requests": 5,
"trackers": [
{
"name": "jsDelivr",
"company": "jsDelivr",
"category": "Hosting",
"requests": 1
}
]
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 39,
"tls": 51,
"wait": 11,
"connect": 5,
"download": 5
},
"response_ms": 111
} |
| 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": 65440,
"co2_grams": 0.0024,
"cleaner_than": 31
} |
| Dns server | {
"ns": [
{
"ip": "205.251.194.149",
"host": "ns2.vercel-dns-3.com"
},
{
"ip": "205.251.197.116",
"host": "ns3.vercel-dns-3.com"
},
{
"ip": "205.251.199.60",
"host": "ns4.vercel-dns-3.com"
},
{
"ip": "205.251.193.92",
"host": "ns1.vercel-dns-3.com"
}
],
"zone": "vercel.app"
} |
| Cookies | {
"cookies": [
{
"name": "__cflb",
"secure": true,
"http_only": true,
"same_site": "None"
}
]
} |
| Location | {
"ip": "216.198.79.195",
"asn": "16509",
"org": "Amazon.com, Inc.",
"city": "Walnut",
"country": "US"
} |
| Ssl | {
"issuer": "Google Trust Services / WR1",
"subject": "*.vercel.app"
} |
| DNS records | {
"A": [
"64.29.17.195",
"216.198.79.195"
]
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"header": "max-age=63072000; includeSubDomains; preload",
"message": "Site is compatible with the HSTS preload list!",
"compatible": true
} |
| HTTP security policies | {
"xFrameOptions": false,
"referrerPolicy": false,
"xXSSProtection": false,
"permissionsPolicy": false,
"xContentTypeOptions": false,
"contentSecurityPolicy": false,
"strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "64.29.17.195",
"family": 4
} |
| Redirects | {
"chain": [
"https://rdnhood.vercel.app"
]
} |
| Page links | {
"internal_count": 1
} |
| HTTP headers | {
"headers": {
"server": "Vercel",
"content-type": "text/html; charset=utf-8",
"strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
} |
Stored observation history4
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
- Availability monitor · Recorded state
Unknown→live_content
content_served
- Google Safe Browsing · Threat flag
No flag recorded→Flag recorded
- Availability monitor · Recorded state
Unknown
probe_inconclusive
- Availability monitor · First collection record
Reachable
Recorded activity
5 entries- VirusTotal
24/92 engine detections
View source - Cloudflare Radar
Phishing
View source - Google Safe Browsing
Threat flag recorded
View source - Added to PhishDestroy
rdnhood.vercel.app
View source - URLScan
Page captured
View source
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
rdnhood.vercel.app Evidence & External Reports
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Official reporting routes
IC3 does not accept attachments. Keep original evidence for investigators. IC3 guidance
Federal tips line1-800-CALL-FBICurrent service: Report Fraud. England, Wales and Northern Ireland. Scotland: 101.
Contact centre0300 123 2040Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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
rdnhood.vercel.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 NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
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.
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.