Skip to security report
Analytics Dashboard
Domain security report
safe-wallet.io favicon

safe-wallet.io

“Safe wallet”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 10/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: MetaMask
OTX: 5 refs Aug 4, 2026 MetaMask
API
Registrar
Immaterialism
Resolved IP
91.92.241.159
Registered
May 14, 2025
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 10. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
10 det.
OTX references
5 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Let's Encrypt · Hostname coverage not recorded
Age
1.4 yr
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

10 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

5 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Observation time not recorded
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
10/89
OTX
5 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

The domain safe-wallet.io is actively flagged as a high‑risk crypto drainer. Analysis shows the domain appears on three independent security blocklists and has been specifically blocked by PhishDestroy, MetaMask, and SEAL, indicating that it is recognized by both generic phishing mitigation services and cryptocurrency‑wallet protection tools. VirusTotal scans report that ten of ninety‑one security vendors have identified malicious behavior associated with the domain, reinforcing the suspicion of malicious activity. The threat classification aligns with the supplied intelligence that the site attempts to illicitly capture cryptocurrency credentials or redirect funds.

Publicly available metadata such as registrar information, hosting IP, SSL certificate details, or page title have not been disclosed, leaving those infrastructure aspects unverified. Consequently, the full scope of the infrastructure, including any content‑delivery networks or geo‑location of the hosting server, remains uncertain. Likewise, no specific indicator of compromise beyond the blocklist listings and vendor detections has been released, so defenders should treat the domain as malicious until further forensic evidence is obtained. Defenders should immediately add safe-wallet.io to network‑level deny lists, enforce DNS‑based blocking, and ensure that endpoint security solutions incorporate the domain into their threat intelligence feeds.

Monitoring outbound connections for attempts to resolve or contact the domain is advisable, as is reviewing logs for any prior interactions that may indicate credential exposure. Given the domain’s active status, continuous re‑evaluation of detection rules is recommended, and any observed traffic should be quarantined and investigated for potential crypto‑drain attempts. Organizations using MetaMask or similar wallet extensions should verify that their client‑side protections are up‑to‑date, as the domain is already blocked by MetaMask’s own threat list.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
10 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
5 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Immaterialism LimitedCollection time not recorded
Network & DNS
91.92.241.159 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
59/100 · mobile performance
Availability history
15 · stored state changes
Source observation history
4 · stored source events
Lookalike relationships
79 · retained relationshipsCollection time not recorded
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Immaterialism Limited · 91.92.241.159 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 1 report PhishingExploited Host checked Oct 3, 2026
OTX tags 2026-072026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishing+1 more
Registrar Immaterialism VN(VN)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for safe-wallet.io →
RegistrationCreated May 14, 2025
Time to First Unavailability 71 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 4, 2026
DOM Analysisanalyzed Sep 18, 2026score 100/1001 brand signal
Submitted URLhttp://safe-wallet.io/
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
91.92.241.159
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL
Server header
Apache
Nameservers 1
  • 2-nest.pipe.ma

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-07-24 11:09:03
Valid until
2026-10-22 11:09:02
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-13 19:05:15 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4fbfe20d609faa62cea7092a1edf3cffd3a7ed07f25caeeb54ebb389787ea2dd

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

viewdns.info · 91.92.241.159rapiddns.io

Latest Classified Outcome 2026-10-17 02:02:21 UTC

Primary outcome Unknown reason: Probe Inconclusive 20% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-17 02:02:21 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-09 10:15:27 UTC last content: 2026-10-09 10:15:27 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 · 9 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

10 / 89 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 11 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
Ermes
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of safe-wallet.io · checked Aug 4, 2026

59
Needs Work
Performance
FCP
2.56s
First Contentful Paint
LCP
12.1s
Largest Contentful Paint
CLS
0.211
Cumulative Layout Shift
TBT
16ms
Total Blocking Time
SI
4.37s
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
Last content observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='safe-wallet.io', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Domain Status Transition 2026-10-13 22:29:42 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Domain Status Transition 2026-09-29 01:42:13 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from dead to alive.
  3. Domain Status Transition 2026-09-21 22:31:44 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  4. Threat First Observed 2026-08-04 02:07:46 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown.
Stored observation history19

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

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 14
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    live_content→Unknown

    stale_current_evidence

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unavailable→Reachable

  13. Availability monitor · Recorded state

    Reachable→Unavailable

  14. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Monitoring

17 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
safe-wallet.io detected and queued for full analysis
Aug 4, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Oct 3, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Aug 4, 2026
VirusTotal
10/89 recorded on VirusTotal
Sep 12, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
OTX Community References
5 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 5, 2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Oct 14, 2026
Site Came Back Online
Domain is responding again — monitoring resumed
Sep 29, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 22, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Aug 4, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Oct 14, 2026
Time to First Unavailability
1700 hours elapsed from detection to the first unavailable observation.
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

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

79 stored lookalike domains

etamask.io omission Internal report meetamask.io repetition Internal report megamask.io replacement Internal report metam.ask.io subdomain Internal report metamaak.io replacement Internal report metamadk.io replacement Internal report metamaks.io transposition Internal report metamassk.io insertion Internal report metamsask.io insertion Internal report metamssk.io replacement Internal report metanask.io homoglyph Internal report metanmask.io homoglyph Internal report
Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 10 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report OTX 5 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 Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

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 safe-wallet.io)
  • 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
Read the evidence in context

About This Report: safe-wallet.io

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Safe wallet”. Apparent target: MetaMask.

VirusTotal detections for safe-wallet.io: 10 (2026-09-12 02:29:25 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A 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/safe-wallet.io"
  title="PhishDestroy threat report for safe-wallet.io"
  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>