ABUSE NOTICE · 72H+ 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 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.
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.
How the scam works
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.
Evidence
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.
Infrastructure
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.
What to do
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.
DOM Analysisanalyzed 2026年10月15日score 100/1002 brand signals
Submitted URLhttp://xn--btrefll-rfbe.com/
Favicon Hash
ケース ID
Observed page title
Google
Automated brand references
GoogleNetflix
TLS証明書
発行者 Let's Encrypt / YR1· stored validity ends in 56 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
62.60.226.163
Network ASN
AS214351
Organization
Femo IT Solutions Limited
Observed location
Frankfurt am Main, DE
Server header
gws
ネームサーバー 2
ns1.dyna-ns.net
ns2.dyna-ns.net
Location describes the IP network.
TLS証明書
Issuer
Let's Encrypt / YR1
Valid from
2026-09-16 17:37:05
Valid until
2026-12-15 17:37:04
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-15 19:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprinta73fc7b9a214206cbd53a28602005d3826fb0fecd1b408f836649e32ef20b790Certificate names · 1 SANs
www.xn--btrefll-rfbe.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:45:30 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-19 22:45:30 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.
Recorded subdomains1
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 record
The original observation time is not recorded for these hostnames.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
