VirusTotal
13 / 92 engine detections
Buka laporan“Google”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 4 days 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.
Peniruan Google: xn--btrefll-rfbe.com — Terakhir diketahui aktif (HTTP 302). Ringkasan bukti: VirusTotal 13/92 (ChainPatrol, alphaMountain.ai, BitDefender…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
13 / 92 engine detections
Buka laporanDBL_SPAM
Scan report
Buka laporan4 community references
Buka laporanprovider verdict: clean
Buka laporanNo threat flag
Buka laporanNo malicious flag
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
xn--btrefll-rfbe.com is an impersonation phishing page that presents itself as Google, with the page title simply reading "Google". It targets anyone who trusts the Google brand, including people in the crypto space who rely on Google accounts for email and recovery. PhishDestroy first saw the domain on 2026-10-15. As of 2026-10-19 the site was still online and its content was serving a redirect.
Brand-impersonation pages like this copy Google's name and look so visitors believe they are on a genuine Google service. The victim is prompted to sign in or confirm details, and whatever they type, typically email addresses, passwords and sometimes one-time codes, goes straight to the operators. A hijacked Google account can then be used to reset passwords elsewhere, read private mail, and reach exchange or wallet-related services tied to that inbox. The punycode domain name is a common way to make an address look less obviously suspicious at a glance.
VirusTotal shows 13 of 92 engines flagging the domain as of 2026-10-19, including ChainPatrol, alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet and G-Data. Besides PhishDestroy, the domain appears on the MetaMask and SEAL blocklists, both maintained by the crypto security community. Spamhaus DBL lists it as DBL_SPAM, and it is referenced in 4 AlienVault OTX pulses.
The domain was registered on 2026-09-16 through DYNADOT LLC, about a month before PhishDestroy flagged it. It is hosted at 62.60.226.163 on the FEMO IT SOLUTIONS LIMITED network in Germany (DE). Its TLS certificate was issued by Let's Encrypt (YR1), so the padlock in the browser says nothing about whether the site is legitimate.
If you entered your Google password on this site, change it immediately from the real Google account page and sign out of all other sessions. Turn on two-step verification with an authenticator app or security key, and review recovery options, forwarding rules and connected apps for anything you did not add. Then change passwords on any services, especially exchanges, that use the same password or can be reset through that Gmail inbox. Defenders should block the domain and its hosting IP at DNS, proxy and email gateways, and search logs for users who visited it after 2026-09-16.
Last checked
ns1.dyna-ns.netns2.dyna-ns.netLocation describes the IP network.
a73fc7b9a214206cbd53a28602005d3826fb0fecd1b408f836649e32ef20b790www.xn--btrefll-rfbe.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.xn--btrefll-rfbe.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of xn--btrefll-rfbe.com · checked Oct 15, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://xn--btrefll-rfbe.com/https://www.google.com/Content-Type: text/html; charset=UTF-8Cache-Control: private, max-age=0Content-Encoding: gzipServer: gws8720df457a93b97d3cdd7c05714c8e255a1969085844eb247756b869dbea636aSec-CH-Prefers-Color-Schemeh3=":443"; ma=2592000,h3-29=":443"; ma=2592000private, max-age=0gzipobject-src 'none';base-uri 'self';script-src 'nonce-tVXPOX9LJzTBR0cYfD6wAQ' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hptext/html; charset=UTF-8same-origin-allow-popups; report-to="gws"Thu, 15 Oct 2026 16:08:11 GMT-1; rel="compression-dictionary"CP="This is not a P3P policy! See g.co/p3phelp for more info."unload=(){"group":"gws","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/gws/other"}]}gwschunkedSAMEORIGIN0Values retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→redirected
http_redirect
Tidak diketahui→redirected
http_redirect
Tidak diketahui→redirected
http_redirect
Tidak diketahui→redirected
http_redirect
Tidak diketahui→redirected
http_redirect
Dapat dijangkau
No threat flag
View source13/92 engine detections
View source4 community references
View sourcePD-20261015-CB1B31
xn--btrefll-rfbe.com
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
xn--btrefll-rfbe.com
PD-20261015-CB1B31 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
xn--btrefll-rfbe.com)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
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.