Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
sites1-google.com favicon

sites1-google.com

“Sites1.google.com”

Bureau d’enregistrement
Hosting Concepts
Resolved IP
35.204.150.5
Registered
08/10/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 9/92 Correspondances de la liste de blocage stockée : 2 Libellé de marque automatique : Google Domaine jeune : 12 jours
10/10/2026 1 Report Sent
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 9. Listes de blocage publiques signalant une correspondance : 2. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ 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@registrar.eu. The latest stored availability evidence still shows the domain reachable; 10 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.

Elapsed since first report
10 days
Reports sent
1
Latest case ID
PD-20261010-FA7776
Current status
HTTP 301 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
detections
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Usurpation de Google: sites1-google.com — Dernier actif connu (HTTP 301). Résumé des preuves: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 9 / 92 6 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critique
VirusTotal
9 / 92
Page captures
2

PhishDestroy threat report

Overview

sites1-google.com is an impersonation phishing domain posing as a Google property. Its page title reads "Sites1.google.com", which mimics a page hosted on Google Sites. It targets anyone who trusts a Google-branded link, and crypto users are clearly in scope because wallet-security blocklists have flagged it. PhishDestroy first saw it on 2026-10-10, and as of 2026-10-19 the site was still alive and serving a redirect.

How the scam works

The trick is in the punctuation. "sites1-google.com" uses a hyphen to look like a subdomain of google.com, but it is a separate domain that Google does not own. Victims who see the "Sites1.google.com" title assume they are on a legitimate Google Sites page. From there they are pushed into handing over Google credentials or into following the redirect to a further page. That page can ask for logins, wallet access or recovery details, and what the victim loses is account access and anything that account or wallet controls.

Evidence

On 2026-10-14, nine of 92 VirusTotal engines flagged the domain, including BitDefender, Kaspersky, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, CRDF and alphaMountain.ai. That is a modest detection count, but the vendors are independent of one another and agree on the verdict. Beyond PhishDestroy, the domain is listed by MetaMask and SEAL, two blocklists focused on protecting crypto users.

Infrastructure

The domain was registered on 2026-10-08 through Hosting Concepts B.V. d/b/a Registrar.eu. It surfaced on our radar just two days later, which fits a campaign that moves fast before lists catch up. It runs on Google Cloud Platform infrastructure located in the Netherlands, so the lookalike name sits on Google-owned servers and gains a little extra surface credibility. The Let's Encrypt certificate gives it a padlock, which says nothing about who runs the site.

What to do

If you entered a Google password here, change it immediately and turn on two-factor authentication with an authenticator app or passkey. Then review recent sign-ins and connected devices in your Google account settings. If the redirect led you to a page asking for a wallet seed phrase or recovery words, treat that wallet as compromised and move your funds to a new one. Defenders should block the domain at DNS and proxy level and alert users that real Google Sites pages never use a hyphenated lookalike domain.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Répertorié View source
PhishDestroy PhishDestroy list View source
SEAL Répertorié View source

Last checked

Capture enregistrée · 2 captures

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
Réputation de l’IP abuse score 13/100 4 reports PhishingWeb SpamPort ScanSpoofing checked 10/10/2026
Bureau d’enregistrement Hosting Concepts NL(NL)
Contact anti-abusabuse@registrar.eu
Registre de l'ICANNICANN Lookup (RDAP) →
EnregistrementCréé 08/10/2026 (12d · Very New!) — Expires 08/10/2027
Statut HTTP301 Moved Permanently
Détails techniquesProvenance & timestamps
Première détection10/10/2026
DOM Analysisanalyzed 10/10/2026score 90/1001 brand signal
Submitted URLhttp://sites1-google.com/
Favicon Hash
ID du dossier
Observed page title
Sites1.google.com
Automated brand references
Google
Certificat TLS
Émis par Let's Encrypt / YR1 · stored validity ends in 77 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
35.204.150.5
Network ASN
AS396982
Organization
Google LLC
Observed location
Groningen, NL
Server header
nginx

Serveurs de noms 3

  • ns1.openprovider.nl
  • ns2.openprovider.be
  • ns3.openprovider.eu

Mail routing 1 MX record

  • mail.webador.compriority 0

Location describes the IP network.

Certificat TLS

Issuer
Let's Encrypt / YR1
Valid from
2026-10-08 11:49:37
Valid until
2027-01-06 11:49:36
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-10 16:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint065b845529f71cbc6db7f0c18086c2e568df0d3ea52d5ca9d69b6863fa1ee566
Certificate names · 1 SANs
  • www.sites1-google.com

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-19 22:32:33 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:32:33 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-19 22:35:37 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 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

9 / Les fournisseurs de sécurité 92 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
SOCRadar

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of sites1-google.com · checked Oct 10, 2026

65
Needs Work
Performance
FCP
3.95s
First Contentful Paint
LCP
12.27s
Largest Contentful Paint
CLS
0.027
Cumulative Layout Shift
TBT
91ms
Total Blocking Time
SI
3.95s
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
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.

Stored observation history10

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

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

Earlier observations 5
  1. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  2. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  3. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  4. Availability monitor · Recorded state

    Inconnu→redirected

    http_redirect

  5. Availability monitor · First collection record

    Accessible

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    9/92 engine detections

    View source
  3. Abuse report sent

    PD-20261010-FA7776

    abuse@registrar.eu
  4. Added to PhishDestroy

    sites1-google.com

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

sites1-google.com

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20261010-FA7776 Recipient: abuse@registrar.eu
Page title stored with report: Sites1.google.com
PDF notice generated Notice text archived (814 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 (NL):
Dutch Criminal Code - Article 326 (Computer Fraud)
Dutch Criminal Code - Article 326c (Phishing)
GDPR
Netherlands law explicitly criminalizes phishing and computer fraud.
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.
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

5 evidence signal groups linked 1 stored notification records Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

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

Que dois-je faire tout de suite ?

Urgent

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

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du 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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment sites1-google.com)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

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?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

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

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
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

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

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