Skip to security report
ribnxnholdlogen.gitbook.io favicon
Domain security and threat intelligence

ribnxnholdlogen.gitbook.io

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

On 2026-09-29, ribnxnholdlogen.gitbook.io redirected to ribnxnholdlogen.gitbook.io/account/. The destination page on ribnxnholdlogen.gitbook.io displays a Robinhood-branded login and account portal hosted on GitBook. The interface features promotional text about investment accounts, security claims regarding popular financial authorities, and mobile app previews with an advertised earn a 1% match offer.

Page title: “Róbinhood Login | Log in to My Account”

More about the sources
Recorded security signals

Stored VirusTotal result: 20/92 engines flagged. Malicious: 18. Suspicious: 2. Analysis time (as stored): 2026-11-16 08:21 UTC. Retrieved (as stored): 2026-11-16 21:34 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

VirusTotal detections: 20/92 Stored blocklist matches: 2 Last known active Google Safe Browsing: threat flag recorded
Registrar
United StatesCloudflare
Resolved IP
Canada172.64.147.209Cloudflare, Inc. · CDN
Registered
2014-03-30
First seen by PhishDestroy
2026-10-15
URLScan
Page captures
open gallery
Domain age
registered 2014-03-30 according to RDAP · source data differ
2026-10-15 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded ribnxnholdlogen.gitbook.io on 2026-10-15. Stored VirusTotal result: 20/92 engines flagged. Malicious: 18. Suspicious: 2. Analysis time (as stored): 2026-11-16 08:21 UTC. Retrieved (as stored): 2026-11-16 21:34 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Registrar: Cloudflare. Status: Reachable · access restricted. Hosting: Cloudflare, Inc. Listed by external blocklists: MetaMask, SEAL. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
20 / 92
Blocklist matches
2 external + PhishDestroy list
Hosting
Canada172.64.147.209Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Registered
2014-03-30
Page captures
2

URLScan capture · 2026-09-29 13:11 UTC · SHA-256 d54dbe13…7d34844

PhishDestroy analysis, reviewed version

On 2026-09-29, ribnxnholdlogen.gitbook.io redirected to ribnxnholdlogen.gitbook.io/account/. The destination page on ribnxnholdlogen.gitbook.io displays a Robinhood-branded login and account portal hosted on GitBook. The interface features promotional text about investment accounts, security claims regarding popular financial authorities, and mobile app previews with an advertised earn a 1% match offer.

The stored VirusTotal domain result reports 20 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".

Source evidenceVirusTotal 20 / 92 · Google Safe Browsing: flagged 7 sources

VirusTotal

20 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
20
Denominator
92
Vendors
ChainPatrol, alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, Kaspersky, LevelBlue, Lionic, MalwareURL, Netcraft, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Observed at
2026-11-16 08:21:35
Checked at
2026-11-16 22:34:11
Fetched at
2026-11-16 21:34:12

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 d3c115a8…feadf72

Open report
URLScanOriginal source recordObserved: 22 fields
Separate monitor record · 2026-11-17 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a0ed4a-4813-77fe-a81a-0085d0b8f16a
Score
100
Malicious
✓
Result at
2026-11-17T04:30:32Z
Enriched at
2026-11-17T09:18:25Z
Source timestamps
Urlscan result at: 2026-11-17 05:30:32; Urlscan enriched at: 2026-11-17 10:18:25

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-11-16 23:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
15
Analyzed at
2026-11-16T23:20:35Z
Source timestamp
2026-11-17 00:20:35
Technical metadata

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
ribnxnholdlogen.gitbook.io: Robinhood-branded login page
AI description
PhishDestroy examines a Robinhood-branded login and account portal hosted on ribnxnholdlogen.gitbook.io with promotional investment text.
AI summary
On 2026-09-29, ribnxnholdlogen.gitbook.io redirected to ribnxnholdlogen.gitbook.io/account/. The destination page on ribnxnholdlogen.gitbook.io displays a Robinhood-branded login and account portal hosted on GitBook. The interface features promotional text about investment accounts, security claims regarding popular financial authorities, and mobile app previews with an advertised earn a 1% match offer. The stored VirusTotal domain result reports 20 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "malware".
AI generated by
threat-v6-gemini
AI generated at
2026-11-16T22:55:29Z
Revision
cb8cafb27997ee8d4f991022e1193efc581c43c2678a84f8b88072a6e86b7ed7
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source 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
Security Signals
SA Scamadviser Warnings 21/100
The owner of the website is using a service to hide their identity on WHOIS According to Tranco this site has a low rank This site is a website within another website This website has been reported as unsafe by Maltiverse This website has been reported for Phishing by IPQS This website has been reported as Suspicious by IPQS
The SSL certificate is valid The domain name has been registered for more than one year in advance This website is (very) old This website is safe according to DNSFilter
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Questions about ribnxnholdlogen.gitbook.io

Is ribnxnholdlogen.gitbook.io legit?

PhishDestroy rates ribnxnholdlogen.gitbook.io as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-15. Stored VirusTotal result: 20/92 engines flagged. Malicious: 18. Suspicious: 2. Analysis time (as stored): 2026-11-16 08:21 UTC. Retrieved (as stored): 2026-11-16 21:34 UTC. Google Safe Browsing flags it. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ribnxnholdlogen.gitbook.io safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on ribnxnholdlogen.gitbook.io. A confirmed blockchain transaction cannot be reversed.

What should I do if I used ribnxnholdlogen.gitbook.io?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (2)

All capture links and hashes (2)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Robinhood report ↗
Google Safe Browsing Flagged Social engineering checked 2026-11-21
IP Context Canada172.64.147.209 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Cloudflare US(US)
Hosting abuse contact registry-abuse@cloudflare.com Cloudflare, Inc. · AS13335
Registration (base domain)gitbook.io · Created 2014-03-30 — Expires 2031-03-30
HTTP Status403 Forbidden
Elapsed Since First Report 37 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-10-15
DOM Analysisanalyzed 2026-11-17score 15/100
Submitted URLhttp://ribnxnholdlogen.gitbook.io/
Observed page title
Suspected Phishing | Cloudflare
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 80 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.64.147.209
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dahlia.ns.cloudflare.com
  • hugh.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-11-12 22:38:49
Valid until
2027-02-10 23:38:38
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte0ba1019384c6709db121aa92013875d8d9e60e6fe84e1d89ad53a08231d45a3
Certificate names · 2 SANs
  • gitbook.io
  • *.gitbook.io

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

Technologies · 7 identified
Open complete records

VirusTotal Analysis

20 / 92 security vendors flagged this domain
View on VT
Last analyzed
ESET
VIPRE
G-Data
Lionic
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
Kaspersky
LevelBlue
Gridinsoft
MalwareURL
BitDefender
ChainPatrol
alphaMountain.ai
Google Safe Browsing
Forcepoint ThreatSeeker
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: http://ribnxnholdlogen.gitbook.io/
Final URL: https://ribnxnholdlogen.gitbook.io/account
Róbinhood Login | Log in to My Account
Róbinhood login is operated by popular financial authorities, making it a secure option. The investment account of Róbinhood Login is covered by Securities
Response
HTTP 200
HTML body
274.1 KB
Compressed
52.0 KB
Links
5 internal · 2 external
Detected technologies
cloudflarereact
Selected response headers
Content-Type: text/html; charset=utf-8
Cache-Control: s-maxage=43931, stale-while-revalidate=2592000
Server: cloudflare
Content-Encoding: gzip
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Content-Type-OptionsReferrer-Policy
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 440bc02f99c0efb822e158ce825ade277fcf46355c6341709f0daf265bafd7e8
Open Graph title: Róbinhood Login | Log in to My Account
Open Graph description: Róbinhood login is operated by popular financial authorities, making it a secure option. The investment account of Róbinhood Login is covered by Securities
Twitter card: summary_large_image
Saved response-header values · 21
alt-svc
h3=":443"; ma=86400
Cache-Control
s-maxage=43931, stale-while-revalidate=2592000
CF-Ray
a4aead7f2d1c925d-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
default-src 'self' *; script-src 'self' 'unsafe-inline' 'unsafe-eval' *; style-src 'self' 'unsafe-inline' blob: *; img-src * 'self' blob: data:; connect-src *; font-src *; frame-src *; object-src 'none'; base-uri 'self' https://static-2c.gitbook.com; form-action 'self' https://static-2c.gitbook.com *; frame-ancestors h
Content-Type
text/html; charset=utf-8
Date
Thu, 15 Oct 2026 12:02:56 GMT
Etag
W/"1d4c2b90f2b3f842f92fcd30a8ab6f0b"
Referrer-Policy
no-referrer-when-downgrade
Server
cloudflare
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, accept-encoding, accept
X-Content-Type-Options
nosniff
x-gitbook-route-site
ribnxnholdlogen.gitbook.io/account/
x-gitbook-route-type
static
x-gitbook-target
2c
x-nextjs-stale-time
300
x-opennext-cache
HIT
x-opennext-request-id
0.em79kobadvm

Values retained by the collector; long values may be shortened during collection.

Registration & observation details1

Availability observations

Last reachable observation

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

All stored data106
Open complete records

Captured network requests

Network requests: 37 SHA-256 hashes: 36 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-16 21:34 UTC.

Open this scan on URLScan 01a0ed4a-4813-77fe-a81a-0085d0b8f16a ↗

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

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Domain monitor · Recorded state

    Unavailable→Reachable

  4. Domain monitor · Recorded state

    Reachable→Unavailable

  5. Domain monitor · Recorded state

    Unavailable→Reachable

Earlier observations 3
  1. Domain monitor · Recorded state

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

All retained availability observations13
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 18. 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
  • Threat Ingested
    ribnxnholdlogen.gitbook.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Cloudflare Radar: Malicious · Automated brand label: Robinhood · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable recorded
Publication & AvailabilityDestroyList Published · Time to First Unavailability · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 886
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+4582 d 5 h
  3. VirusTotal analysis with detections+31 d 20 h
  1. Google Safe Browsing

    Threat flag recorded

    +4 d 20 h
  2. VirusTotal

    20/92 engine detections

    +31 d 20 h
  3. Added to PhishDestroy

    ribnxnholdlogen.gitbook.io

    +15 d 22 h
  4. URLScan

    Malicious

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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

ribnxnholdlogen.gitbook.io

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 ribnxnholdlogen.gitbook.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

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.

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/ribnxnholdlogen.gitbook.io"
  title="PhishDestroy threat report for ribnxnholdlogen.gitbook.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>