Ir para o relatório de segurança
Domain security report
theroomemes.com favicon

theroomemes.com

“Roo ($ROO) | Nobody knows what he is.”

Veredicto de ameaça
Assessment sources

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

Disponibilidade Último ativo conhecido Última observação de acessibilidade armazenada Observado · HTTP probe
Correspondências da lista de bloqueio armazenada: 1 Automated brand label: Google Domínio jovem: 13 dias atrás
OTX: 4 refs 16/10/2026 Google 1 Report Sent CDN
API
Registrador
Dominet (HK)
Resolved IP
188.114.97.3
Registered
03/10/2026
2 sources
In this reportGet help
Este domínio foi sinalizado como malicioso
Listas de bloqueio públicas relatando uma correspondência: 1. Tenha extremo cuidado – não insira credenciais ou informações pessoais.
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is domainabuse@service.aliyun.com. The latest stored availability evidence still shows the domain reachable; 28 hours has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
28 hours
Reports sent
1
Latest case ID
PD-20261016-0D6BCD
Current status
HTTP 200 at latest stored check
Resumo do relatório

theroomemes.com — Último ativo conhecido (HTTP 200). Representação da marca: Google; Tipo de golpe: Crypto Drainer. Resumo das evidências: VirusTotal 0/92; 1 external blocklist match (ScamSniffer); PhishDestroy score 100/100. Registrador: Dominet (HK).

A análise detalhada do PhishDestroy AI permanece em inglês para preservar o registro forense original.

Additional indicators at a glance

OTX references
URLScan
URLScan
Certificado TLS
Within stored validity dates
Let's Encrypt / YE1 · Hostname coverage not recorded
Idade
13d Very New!
Status observado
Último ativo conhecido 200
PhishDestroy
DestroyList
Listado
Reports Sent
1

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.

Public blocklists

1 external matches

Detalhes
Interpretation & limits

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

VirusTotal

checked — no detections recorded

Denunciar
Interpretation & limits

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

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Denunciar
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

4 community references

Denunciar
Interpretation & limits

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

CF Radar

provider verdict: suspicious

Observation time not recorded
Denunciar
Interpretation & limits

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

URLScan capture

relatório armazenado

View stored capture ↗
Denunciar
Interpretation & limits

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

URLScan verdict

Análise concluída

Denunciar
Interpretation & limits

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

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

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

Resumo das evidências

Crítico
OTX
4 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.

Assessment

theroomemes.com was recorded with multiple security observations, including a ScamSniffer blocklist entry dated 2026-10-16. The domain also had a PageSpeed performance score captured on the same date.

Recorded Evidence

On 2026-10-16, theroomemes.com was listed on the ScamSniffer blocklist. VirusTotal checked the domain on 2026-10-16, recording 0 detections out of 92 scanners. OTX pulses referenced theroomemes.com four times as of 2026-10-16. The domain was registered through Dominet (HK) Limited on 2026-10-03. PhishDestroy internally listed the domain, and PageSpeed measured its performance score as 66 on 2026-10-16.

Interpretation

The ScamSniffer blocklist entry for theroomemes.com contains an external security listing, which is a form of blocklist record. VirusTotal provides a scan-based measurement, documenting how many security engines detected the domain as of its check. OTX pulses reference the domain as a subject of security intelligence, offering a broader context for its observation. These sources together cover both external and internal security monitoring, but each uses its own method and scope.

Recommended Actions

To maintain a clear security profile for theroomemes.com, retain the ScamSniffer blocklist entry and VirusTotal scan results for future comparison. The OTX pulse references and PhishDestroy internal listing should also be preserved as supporting evidence. Regularly compare new security records to these existing observations to track any changes in external listings or scan results.

Data coverage & collection

23 · datasets with records / 8 · 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
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
1 · external matches
Cloudflare Radar
suspiciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Dominet (HK) LimitedCollection time not recorded
Network & DNS
188.114.97.3 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YE1
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
9 · automated brand labels
Observed indicators
2 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
66/100 · mobile performance
Response records
1 · outgoing report records
Availability history
2 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 8

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Recorded subdomains
  • Lookalike relationships
  • Denúncias da comunidade
  • Chainabuse records
Download the dated observations and supporting metadata.
Extracted from stored page analysis

Observed indicators

1 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x3458e003F6ED93df0F537b8AcaC6FbE08E41247fFormat validated · Domain analysis
Telegram
https://t.me/RooCoinETHStored page reference

IoC extraction recorded 2026-10-17 04:00:27 UTC

Blocklist records

1 · external source matches

Status da lista de bloqueios pública

Domain, network & archive

Dominet (HK) Limited · 188.114.97.3 · DNS, TLS and retained responses

Domain details

Domínio
URLScan verdict Análise concluída score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden A reputação do Edge-IP não é atribuída a este domínio.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomíniosdrainerfraudlivemonthlyphishdestroyphishingscam
Registrador Dominet (HK) US(US)
Contato para abusosdomainabuse@service.aliyun.com
Registro da ICANNICANN Lookup (RDAP) →
RegistroCriado 03/10/2026 (13d · Very New!) — Expires 03/10/2027
Status HTTP200
Detalhes técnicosProvenance & timestamps
Detectado pela primeira vez16/10/2026
DOM Analysisanalyzed 16/10/2026score 100/1009 brand signals
IoC Extractionscanned 17/10/20261 wallet · 1 Telegram IoCs
Submitted URLhttp://theroomemes.com/
Favicon Hash
ID do caso

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

A reputação do Edge-IP não é atribuída a este domínio.

Servidores de nomes 2
  • kira.ns.cloudflare.com
  • west.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-10-03 21:05:38
Valid until
2027-01-01 21:05:37
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte6ef4ff3e2ed755420585bfa53d7b574ffe7d18823b3c0303058459ad173e3b0

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-17 10:00:14 UTC

Primary outcome Conteúdo ativo reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Conteúdo ativo Ordinary HTTP content served 90% 2026-10-17 10:00:14 UTC
RDAP registration Desconhecido
Observed timeline last reachable: 2026-10-17 10:00:14 UTC last content: 2026-10-17 10:00:14 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.
Tecnologias · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este domínio Envie evidências e ajude a proteger outras pessoas

Evidências arquivadas

Wayback Machine Snapshot
Um instantâneo histórico está disponível para revisão de evidências
View Archive
Análise de desempenho do site

Google PageSpeed Insights — mobile performance audit of theroomemes.com · checked Oct 16, 2026

66
Needs Work
Performance
FCP
1.84s
First Contentful Paint
LCP
2.63s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
5378ms
Total Blocking Time
SI
2.16s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://theroomemes.com/
Final URL: https://theroomemes.com/
Roo ($ROO) | Nobody knows what he is.
Roo ($ROO) is a meme coin on Robinhood chain for a small fuzzy creature nobody can identify. The sightings, the contract and how to buy.
Resposta
HTTP 200
HTML body
445.8 KB
Compressed
56.8 KB
Links
16 internal · 15 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Roo: Nobody knows what he is.
Open Graph description: A meme coin on Robinhood chain. Nobody knows what he is. He looks funny.
Twitter card: summary_large_image
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4b7b4f97cdf9760-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 14:20:54 GMT
Last-Modified
Tue, 06 Oct 2026 13:16:33 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ptA3CwfADPEtPyB%2Bi%2BNC8pxe%2FlXiP43YP93Vl1JEmBF5fyZ0C%2FFSIWTf9KgNUBkuUnkXEVTs2LuhHtJYYh5pEJhftEPsmbDKL%2B5e0nucouEj73HCotL0S6rtO%2FsOcF2IAiU
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding

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

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-16 14:20:55 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 14:20:55 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-16 14:20:55 UTC
Fonte
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

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.

Detection & evasion checks

Stored browser and crawler observations

Análise de detecção e evasão

Verificação de cloaking e distribuição de tráfego

Ainda não foi digitalizado Ainda não foi registrada nenhuma diferença entre o rastreador e o navegador

Observações armazenadas comparando o rastreador com o navegador para este host, além de uma verificação em tempo real da assinatura digital para sistemas de distribuição de tráfego do tipo Keitaro.

Sinalizador de camuflagem armazenado
Ainda não foi digitalizado
Última varredura de camuflagem
Cabeçalho do servidor detectado pelo scanner
cloudflare
Roteamento de captura
Local arquivado em 2026-10-16 14:20:55 UTC

Nota do digitalizador: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Verificação de impressão digital “TDS” em tempo real
Sete indicadores do Keitaro e uma comparação entre navegador e rastreador. Uma nova análise começa somente ao pressionar o botão.
Sob demanda

Nenhum resultado desta verificação foi salvo.

Timeline & response

1 · outbound report records

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. Threat First Observed 2026-10-16 14:21:52 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
Stored observation history3

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

    Desconhecido→live_content

    content_served

  2. Availability monitor · First collection record

    Desconhecido

  3. Availability monitor · Recorded state

    Desconhecido

    probe_inconclusive

Pipeline de resposta a ameaças

Descoberta
Analysis
Notifications
Monitoring

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

Ameaça detectada
theroomemes.com detectados e colocados na fila para análise completa
16/10/2026
URLScan.io Capture
Armazenado URLScan report with capture artifacts
16/10/2026
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
17/10/2026
Detecção de lista de bloqueio
Encontrado em 1 blocklist: ScamSniffer
17/10/2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
16/10/2026
Brand Impersonation
Impersonation of Google
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
O relatório contém tecnologia armazenada ou resultados de análises forenses.
17/10/2026
Sent Report Recorded
Stored outgoing record associated with registrar Dominet (HK) Limited, 1 abuse contact
domainabuse@service.aliyun.com
16/10/2026
Lista de Destruição Publicada
16/10/2026
Monitoring Continues
O domínio permanece acessível ou com acesso restrito; verificações futuras poderão atualizar esta observação.
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.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidências e relatórios externos

Instantâneo das evidências enviadas
Sent: Ledger records: 1 Case ID: PD-20261016-0D6BCD Recipient: domainabuse@service.aliyun.com
PDF notice generated Notice text archived (859 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (US):
18 U.S.C. § 1343 - Wire Fraud
18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA)
15 U.S.C. § 45 - FTC Act (Deceptive Practices)
Federal laws prohibit wire fraud, computer fraud, and deceptive business practices.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Análise aprofundada

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Você foi afetado por este site?

5 evidence signal groups linked 1 stored notification records Último ativo conhecido
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Se você inseriu credenciais de conta, informações pessoais ou de pagamento, ou baixou um arquivo deste domínio, tome medidas imediatas. Abaixo estão os recursos para ajudá-lo a relatar o incidente e se proteger.

Official reporting routes
Cuidado com os golpistas que prometem recuperação! Os criminosos podem entrar em contato novamente com as vítimas fingindo ser investigadores, advogados ou agentes de recuperação. Não pague taxas antecipadas nem compartilhe credenciais. Saiba mais sobre fraudes relacionadas à recuperação →
Notifique as autoridades locais

Selecione seu país para obter contactos oficiais do cibercrime ou crie um rascunho de reclamação →.

Diretório de 97 países

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

Rascunho assistido por IA – os detalhes do incidente são processados pelo provedor de IA · Revise e envie você mesmo
After a phishing incident

Recomendações e orientações para as vítimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

O que devo fazer agora mesmo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Alterar todas as senhas — e-mail, contas do Exchange, qualquer coisa que use a mesma senha
  • Ativar a autenticação de dois fatores usando um aplicativo autenticador (não por SMS). Desative a recuperação por SMS
  • Cartões de congelamento se você inseriu dados bancários no site de phishing

Que informações devo coletar para o meu relatório?

Diretrizes do FBI

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.
  • Datas e horários exatos — de cada transação e do primeiro contato com o golpista
  • Capturas de tela — sites fraudulentos, mensagens de bate-papo, e-mails, transações em carteiras digitais, redes sociais
  • Todas as URLs e domínios utilizado pelo golpista (incluindo theroomemes.com)
  • Comunicações — e-mails, mensagens de texto, números de telefone e nomes de usuário que o golpista utilizou

Mesmo que você não tenha todos os detalhes — registre uma ocorrência mesmo assim. Mesmo informações parciais ainda ajudam nas investigações.

A quem devo denunciar o golpe?

  • FBI IC3 — Centro de Denúncias de Crimes na Internet (sistema federal de denúncias dos EUA)
  • Europol — Relatórios sobre crimes cibernéticos na Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polícia local — cria um registro oficial, mesmo que não possam agir imediatamente

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?

  • Sites falsos — clones idênticos, até o último pixel, de sites legítimos, com domínios ligeiramente alterados
  • Abate de suínos — confiança construída ao longo de semanas pelo Telegram, WhatsApp e aplicativos de namoro; em seguida, o dinheiro foi roubado
  • Golpes relacionados à recuperação — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Golpes baseados em IA — deepfakes, phishing automatizado e sites gerados por IA, o que torna a fraude mais difícil de detectar

Como posso me proteger no futuro?

  • Adicione os sites oficiais aos favoritos — nunca clique em links de e-mails, mensagens diretas ou anúncios
  • Verificar domínios — verificar PhishDestroy antes de interagir. Verifique se o site usa HTTPS, a ortografia e a idade do domínio
  • "Bom demais para ser verdade" = golpe — retornos garantidos, endossos de celebridades, prazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantenha-se informado, mantenha-se seguro

Monitore ameaças em tempo real ou conteste esta listagem caso acredite que se trate de um falso positivo

Feed de ameaças em tempo real Recorrer deste anúncio
Read the evidence in context

Sobre este relatório: theroomemes.com

Este relatório apresenta as últimas evidências armazenadas disponíveis para PhishDestroy. Os carimbos de data/hora de origem são mostrados quando disponíveis; a disponibilidade e os veredictos do fornecedor podem mudar após a coleta.

O site capturado exibia o título da página “Roo ($ROO) | Nobody knows what he is.” e pode estar se passando por Google.

PhishDestroy lista theroomemes.com como suspeito. Foi verificado pelos mecanismos de segurança 92; veredictos automatizados podem mudar. O monitoramento continua. Observado: 2026-10-16 15:22:19 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.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Incorporar este relatório

Compartilhe essas informações sobre ameaças em seu site ou blog

embed.html
<iframe
  src="https://phishdestroy.io/pt-br/embed/domain/theroomemes.com"
  title="PhishDestroy threat report for theroomemes.com"
  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>