logsweb.cc — 콘텐츠를 사용할 수 없음. 브랜드 사칭: Google; 사기 유형: Impersonation. 증거 요약: VirusTotal 3/91 (alphaMountain.ai, Forcepoint ThreatSeeker, SOCRadar); PhishDestroy score 86/100. 등록기관: Global Domain Group.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
logsweb.cc was a phishing page that impersonated Google, presenting itself under the plain page title "Google" to people who expected a genuine Google service. PhishDestroy first saw it on 2026-09-27. The site went offline on 2026-09-30. When last checked on 2026-10-19, its domain no longer resolved in DNS, so the page is dead.
How the scam works
Pages like this copy the look of a Google sign-in or service screen so that visitors type in their email address and password without a second thought. Whatever is entered goes to the operators rather than to Google. A Google account is a master key: it often unlocks Gmail, Drive, saved browser passwords and password resets for other services, including crypto exchanges and wallet backups stored in the cloud. The "Google" title in the browser tab was part of that disguise, since nothing in the domain name itself relates to Google.
Evidence
On 2026-09-29, three of 91 VirusTotal engines flagged the domain: alphaMountain.ai, Forcepoint ThreatSeeker and SOCRadar. That is a thin count, typical for a page that lived only a few days, so most security tools never caught up with it. The domain also appears in three AlienVault OTX threat pulses, which means other researchers tracked it independently. PhishDestroy lists it on its own blocklist.
Infrastructure
The domain was registered on 2026-09-19 through Global Domain Group LLC, and PhishDestroy spotted it eight days later. It was dead within three days of that. This short lifespan fits a disposable phishing domain. Traffic ran through Cloudflare, Inc. network space with a Canadian IP location, which hides the real origin server. A free Let's Encrypt certificate gave it the usual browser padlock, a reminder that HTTPS shows only that the connection is encrypted, not who runs the site.
What to do
If you entered your Google password on this page, change it immediately from the real Google account settings. Change it as well on any other site where you reused it. Turn on two-step verification, review recent security activity and signed-in devices, and remove unfamiliar recovery emails, phone numbers or third-party app access. Then check accounts that use Google sign-in or Gmail for password resets, especially exchanges and wallet services. Security teams should search proxy and DNS logs for lookups of logsweb.cc between 2026-09-19 and 2026-09-30 and force credential resets for any users who reached it.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-19 01:16:51 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-29 01:36:45 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-29 01:36:45 UTC → 2026-09-30 16:14:55 UTC · 38.64hmidpoint estimate ≈ 2026-09-29 20:55:50 UTC · precision medium · basis bounded
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.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 logsweb.cc)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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)
