Skip to security report
Analytics Dashboard
Domain security and threat intelligence
robinhoodilogin.tilda.ws favicon

robinhoodilogin.tilda.ws

In short

robinhoodilogin.tilda.ws is a credential phishing page detected by PhishDestroy on 2026-09-11. Risk: critical (95/100). Registrar: Tilda. Status: Reachable · access restricted. Hosting: AS205282 TILDA PLATFORM CLOUD SERVICES CO. L.L.C. VirusTotal: 9/89 engines flag it. Do not enter credentials or connect a wallet.

“403”

Registrar
Tilda
Resolved IP
194.48.203.16
Registered
Feb 15, 2014
PhishDestroy assessment Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
VirusTotal detections: 9/89 Stored blocklist matches: 2 Automated brand label: Robinhood Last known active
Sep 11, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 9. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
9 / 89
engine detections
Google Safe Browsing
No threat flag
Page captures
5
open gallery
Domain age
4633 days
Source evidenceVirusTotal 9 / 89 6 sources

VirusTotal

9 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing
View full Cloudflare Radar report

Analysis

Critical
VirusTotal
9 / 89
Page captures
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

robinhoodilogin.tilda.ws is a credential phishing page that impersonates Robinhood. It targets Robinhood customers who might hold stocks or crypto on the platform. The address sits on a free subdomain of the Tilda website builder, and the name splices "robinhood" and "login" together to look like an official sign-in link. PhishDestroy first flagged it on 2026-09-11, and the site was still online on 2026-10-19.

How the scam works

Victims usually arrive from a text, email or ad warning about a locked account, a suspicious trade or a pending withdrawal. The link leads to a page styled as Robinhood's sign-in screen. Anything typed there goes to the operators: email, password and often the one-time 2FA code. They then use those details to log in to the real account and move out funds or crypto before the owner notices. The page currently displays the title "403", while our classification is based on it serving as a Robinhood credential phishing page.

Evidence

On 2026-09-20, 9 of 89 VirusTotal engines flagged the domain as malicious. Those vendors include ChainPatrol, alphaMountain.ai, Emsisoft, Forcepoint ThreatSeeker, Fortinet, Kaspersky, Lionic and Netcraft. That is a modest share of engines, but it combines crypto-focused, general security and anti-phishing vendors. Beyond PhishDestroy, the domain is listed by MetaMask and SEAL. As a result, it is blocked in wallet warnings and in feeds shared across the crypto security community.

Infrastructure

The operators did not register a domain of their own. They used a subdomain on Tilda, a website builder that issues these addresses instantly and at no cost. This makes the page cheap to set up and easy to replace with a new name once it is taken down. It is served from Tilda's own cloud network (AS205282) in Ireland, which is normal hosting for any site built on that platform.

What to do

If you entered your Robinhood login on this page, change your password right away through the official app and turn on app-based 2FA. Log out of all other active sessions and check your trades, transfers and linked bank accounts for anything you did not authorize. Contact Robinhood support if anything looks wrong. If you reuse that password on other sites, change it there too, and if you ever typed a wallet recovery phrase, move those funds to a new wallet. Defenders should block the subdomain, report it to Tilda for removal, and watch for similar Robinhood-themed names on website-builder platforms.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-10T19:00:41Z

Observed: · Retrieved:

Uuid
01a08cb1-75e4-7706-9ac8-ad2214e3c3ec
Final url
https://robinhoodilogin.tilda.ws/
Status
200
Ip
194.48.203.17
Contacted domains
[
    "static.tildacdn.info",
    "stat.tildaapi.com",
    "static.tildacdn.com",
    "thumb.tildacdn.com",
    "fonts.gstatic.com",
    "fonts.googleapis.com",
    "stat.tildacdn.com"
]
Contacted IP addresses
[
    "5.101.71.73",
    "192.178.183.94",
    "142.251.110.95",
    "92.223.124.62",
    "185.129.100.115",
    "194.48.203.17"
]
Asns
[
    "201589",
    "15169",
    "199524",
    "57724",
    "205282"
]
Countries
[
    "AM",
    "US",
    "DE",
    "RU",
    "AE"
]
Linked domains
[
    "tilda.cc",
    "help.tilda.cc"
]
Document hash
f1aceadeb856aba043f144f5174f491fcab0f8a610a128e87285073b54755a47
Script hashes
[
    "ba5e83077e988ea458b32054eb388000173427b5eca6e80e7ac56a03b5ce4d23"
]
Globals
[
    "t_onReady",
    "t_onFuncLoad",
    "$",
    "jQuery",
    "t_addClass",
    "t_removeClass",
    "t_removeEl",
    "t_outerWidth",
    "t_throttle",
    "t_debounce",
    "t_checkIsEditMode",
    "t_checkEditorIsReady",
    "t_scrollBarWidthCompensator__setObject",
    "t_scrollBarWidthCompensator__init",
    "t_scrollBarWidthCompensator__checkSize",
    "t_scrollBarWidthCompensator__cancel",
    "t_triggerEvent",
    "t_getRootZone",
    "t_modifyRootZone",
    "t_loadJsFile",
    "t_loadCSSFile",
    "t_scrollTo",
    "t_smoothScrollTo",
    "isSearchBot",
    "isMobile",
    "$isMobile",
    "isTablet",
    "isiOS",
    "isiOSChrome",
    "isFirefox",
    "isOpera",
    "isiOSVersion",
    "isSafari",
    "isIE",
    "isSafariVersion",
    "browserLang",
    "tildaBrowserLang",
    "nojscode",
    "dataLayer",
    "mainTracker"
]
Storage keys
[
    "visited"
]
Tls
{
    "san": [
        "*.tilda.ws",
        "tilda.ws"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "GlobeSSL RSA DV SSL CA 2",
    "subject": "*.tilda.ws",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-30T23:59:59Z",
    "valid_from": "2026-07-16T00:00:00Z"
}
Domain age days
110
Apex age days
3842
Tls age days
56
Tls valid days
198
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 23,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN"
}
Cloudflare Radar · 2026-09-11T09:53:19Z

Observed: · Retrieved:

Uuid
8c6137bd-a141-43eb-bd7f-b87a4472411b
Final url
https://robinhoodilogin.tilda.ws/
Status
404
History
[
    {
        "url": "https://robinhoodilogin.tilda.ws/",
        "status": 404
    }
]
DOM structure hash
6d2dfc121ce1fe8439c110b3f4ffc779a6a525d4e562c128901823496f4b69f3
Document hash
0d0f8dab1199f7754dc34194d9e22a3cd0fd42bb5254966050e2bcd00dea5031
Url risks
[
    "Phishing"
]
Domain risks
[
    "Phishing",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "robinhoodilogin.tilda.ws",
        "type": "A",
        "value": "194.48.203.17"
    },
    {
        "name": "robinhoodilogin.tilda.ws",
        "type": "A",
        "value": "194.48.203.16"
    },
    {
        "name": "robinhoodilogin.tilda.ws",
        "type": "A",
        "value": "194.48.203.15"
    },
    {
        "name": "tilda.ws",
        "type": "A",
        "value": "194.48.203.16"
    },
    {
        "name": "tilda.ws",
        "type": "A",
        "value": "194.48.203.17"
    },
    {
        "name": "tilda.ws",
        "type": "A",
        "value": "194.48.203.15"
    }
]
Dnssec valid
false
Ip
194.48.203.17
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "GoDaddy.com",
    "created": "2014-02-15T10:17:05Z",
    "updated": "2022-03-17T11:13:27Z",
    "expires": "2027-02-15T10:17:05Z",
    "nameservers": [
        "ns-118.awsdns-14.com",
        "ns-1258.awsdns-29.org",
        "ns-1912.awsdns-47.co.uk",
        "ns-985.awsdns-59.net"
    ]
}
VirusTotal · 2026-10-11T15:06:15Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 9,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Kaspersky": "phishing",
    "ChainPatrol": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
GoDaddy.com
Created
2014-02-15T10:17:05Z
Updated
2022-03-17T11:13:27Z
First seen
2026-09-09T13:25:55Z
DNS records
[
    {
        "ttl": 900,
        "type": "A",
        "value": "194.48.203.17"
    },
    {
        "ttl": 900,
        "type": "A",
        "value": "194.48.203.15"
    },
    {
        "ttl": 900,
        "type": "A",
        "value": "194.48.203.16"
    }
]
Dns at
2026-10-11T15:15:19Z
Jarm
15d15d15d29d15d00041d41d000000ab8dbe12fa0c1eeebf055e3115374289
Certificate
{
    "san": [
        "*.tilda.ws",
        "tilda.ws"
    ],
    "issuer": "Key-Systems GmbH / GlobeSSL RSA DV SSL CA 2",
    "serial": "9f3f55b6502aff026831d13b40fa6781",
    "sha256": "390470a69a8b956f6d27281e00d3e955ceafcca79d998cc97458262c8697cda5",
    "subject": "*.tilda.ws",
    "valid_to": "2027-01-30T23:59:59Z",
    "valid_from": "2026-07-16T00:00:00Z"
}
Registration record
{
    "registrar": "GoDaddy.com",
    "registrar_iana_id": "146",
    "registrar_url": "www.godaddy.com",
    "created": "2014-02-15T10:17:05Z",
    "updated": "2022-03-17T11:13:27Z",
    "expires": "2027-02-15T10:17:05Z",
    "status": [
        "clientDeleteProhibited",
        "clientRenewProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns-118.awsdns-14.com",
        "ns-1258.awsdns-29.org",
        "ns-1912.awsdns-47.co.uk",
        "ns-985.awsdns-59.net"
    ],
    "dnssec": "unsigned"
}

Questions about robinhoodilogin.tilda.ws

Is robinhoodilogin.tilda.ws legit?

No. PhishDestroy classifies robinhoodilogin.tilda.ws as a credential phishing page (risk: critical, 95/100); it was first detected on 2026-09-11. VirusTotal: 9/89 engines flag it. Treat the site as unsafe.

Is robinhoodilogin.tilda.ws safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on robinhoodilogin.tilda.ws. 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 robinhoodilogin.tilda.ws?

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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-09-11 09:51 UTC
StateStored capture
Position1 / 5
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 1 report Port Scan checked Oct 11, 2026
Registrar (base domain) Tilda
Abuse contact["abuse@godaddy.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for tilda.ws →
Registration (base domain)tilda.ws · Created Feb 15, 2014 — Expires Feb 15, 2027
HTTP Status403 Forbidden
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
DOM Analysisanalyzed Sep 12, 2026score 85/1003 brand signals
Submitted URLhttp://robinhoodilogin.tilda.ws/
Favicon Hash
Observed page title
403
Automated brand references
Across PayPal Revolut
TLS Certificate
Issued by Key-Systems GmbH / GlobeSSL RSA DV SSL CA 2 · stored validity ends in 99 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
194.48.203.16
Network ASN
AS205282
Organization
TILDA PLATFORM CLOUD SERVICES CO. L.L.C
Observed location
Dublin, IE

Nameservers 4

  • ns-118.awsdns-14.com
  • ns-1258.awsdns-29.org
  • ns-1912.awsdns-47.co.uk
  • ns-985.awsdns-59.net

Location describes the IP network.

TLS certificate

Issuer
Key-Systems GmbH / GlobeSSL RSA DV SSL CA 2
Valid from
2026-07-16 00:00:00
Valid until
2027-01-30 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-12 01:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint390470a69a8b956f6d27281e00d3e955ceafcca79d998cc97458262c8697cda5
Certificate names · 1 SAN
  • tilda.ws

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

viewdns.info · 194.48.203.16rapiddns.io

Latest Classified Outcome 2026-10-23 10:07:29 UTC

Primary outcome Reachable but protected reason: HTTP access restricted 50% confidence
Attribution mechanism: Access Restriction source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected HTTP access restricted Access Restriction 50% 2026-10-23 10:07:29 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 10:07:29 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 · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
ChainPatrol
alphaMountain.ai
Emsisoft
Forcepoint ThreatSeeker
Fortinet
Kaspersky
Lionic
Netcraft
Sophos
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of robinhoodilogin.tilda.ws · checked Sep 11, 2026

100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
1.54s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.04s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable 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.

Check for cloaking

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

Page titles differ

alive_content: raw=content_403; http=403; via=https_proxy

Browser
403
Crawler
Pages are not published.
robinhoodilogin.tilda.ws
Saved result
Keitaro TDS
Stored observation history24

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

    Unknown→protected

    http_access_restricted · access_restriction

  2. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

Earlier observations 19
  1. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  2. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  3. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  4. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  5. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  6. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  7. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  8. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  9. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  10. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  11. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  12. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  13. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  14. Availability monitor · Recorded state

    Unavailable→Reachable

  15. Availability monitor · Recorded state

    protected→inactive

    http_no_content

  16. Availability monitor · Recorded state

    Reachable→Unavailable

  17. Availability monitor · Recorded state

    Unknown→protected

    http_access_restricted · access_restriction

  18. Availability monitor · Recorded state

    Unavailable→Reachable

  19. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    9/89 engine detections

    View source
  3. Added to PhishDestroy

    robinhoodilogin.tilda.ws

    View source

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 9 det. ChainPatrol URLQuery Scamadviser 15 trust SSL Labs Certificate hostname mismatch CF Radar Malicious WOT 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 0 stored notification records Reachable · access restricted

Listed domains receive at least one abuse report; this entry has no retained notification history.

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

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

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 robinhoodilogin.tilda.ws)
  • 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

Live Threat Feed Appeal This Listing
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/robinhoodilogin.tilda.ws"
  title="PhishDestroy threat report for robinhoodilogin.tilda.ws"
  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>