VirusTotal
8 / 92 engine detections
보고서 열기“Gmail”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@tencent.com.
The latest stored availability evidence still shows the domain reachable; 5 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.
Argent 사칭: thinkingol.com — 마지막으로 알려진 활성 (HTTP 200). 증거 요약: VirusTotal 8/92 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, G-Data, LevelBlue); PhishDestroy…
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
8 / 92 engine detections
보고서 열기Scan report
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기No malicious flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
thinkingol.com is an impersonation phishing page that presents itself as Gmail, carrying the page title "Gmail" to pass as Google's email login. It targets anyone with a Google account, including crypto users whose exchange and wallet-service logins are tied to that inbox. PhishDestroy first flagged the domain on 2026-10-15. As of 2026-10-19 the site was still online and serving live content.
Pages like this copy the look of a Gmail sign-in screen so a visitor arriving from a link in an email, message or ad believes they are logging in to Google. Whatever is typed into the form, usually the email address and password and sometimes a one-time verification code, goes straight to the operators. With a hijacked inbox, attackers can read private mail, trigger password resets on exchanges and other linked services, intercept security alerts, and use the account to phish the victim's contacts. The loss goes beyond a single password, since control of the email account can open every service connected to it.
On 2026-10-18, VirusTotal showed 8 of 92 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, G-Data, LevelBlue, Lionic, SOCRadar and Sophos. That is a modest detection rate, so many security products and browsers may not yet warn visitors. PhishDestroy lists the domain on its blocklist.
The domain was registered on 2025-10-20 through Alibaba Cloud Computing Ltd. d/b/a HiChina. It resolves to 43.130.125.154, on a network registered to Tencent Building, Kejizhongyi Avenue, with the server located in the US. Its TLS certificate comes from Let's Encrypt (YR1), so the browser padlock only means the connection is encrypted and says nothing about whether the site is legitimate.
If you entered your Gmail credentials on this site, go to Google's official sign-in page yourself, change your password at once, and review active sessions, recovery email, recovery phone and mail forwarding rules for changes you did not make. Turn on two-step verification with an authenticator app or security key. Then change passwords on exchanges and other accounts that rely on this inbox, and watch for unexpected reset emails. Defenders should block the domain and its IP at the mail gateway, DNS and proxy layers, search mail logs for links to it, and report it to Google and the registrar.
vip1.alidns.comvip2.alidns.comLocation describes the IP network.
ff7674892df20037e873c182c67de6b58f1391a8e482eb6f79ccf2e1256ca511www.thinkingol.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.
mail.1.thinkingol.comDomain recordmail.10.thinkingol.comDomain recordmail.11.thinkingol.comDomain recordmail.12.thinkingol.comDomain recordmail.13.thinkingol.comDomain recordmail.14.thinkingol.comDomain recordmail.15.thinkingol.comDomain recordmail.16.thinkingol.comDomain recordmail.17.thinkingol.comDomain recordmail.18.thinkingol.comDomain recordmail.19.thinkingol.comDomain recordmail.2.thinkingol.comDomain recordmail.20.thinkingol.comDomain recordmail.21.thinkingol.comDomain recordmail.22.thinkingol.comDomain recordmail.23.thinkingol.comDomain recordmail.24.thinkingol.comDomain recordmail.25.thinkingol.comDomain recordmail.26.thinkingol.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of thinkingol.com · checked Oct 15, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://thinkingol.com/Alert2/glow.htmlhttps://thinkingol.com/Alert2/glow.htmlServer: nginxContent-Type: text/htmlContent-Encoding: gzipkeep-alivegziptext/htmlThu, 15 Oct 2026 01:22:30 GMTW/"6aba4007-173c8"Mon, 28 Sep 2026 10:23:03 GMTnginxmax-age=31536000chunkedAccept-EncodingValues 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.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=nginx
thinkingol.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
접속 가능
No threat flag
View source8/92 engine detections
View sourcePD-20261015-7EB594
Page captured
View sourcethinkingol.com
View sourcePD-20261015-7EB594 Recipient: abuse@tencent.com 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 (CN): Cybersecurity Law of China Criminal Law Article 285 Criminal Law Article 266 - Fraud Chinese law strictly prohibits cyber fraud and illegal access to computer systems. 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.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
thinkingol.com)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.