Analysis of kintsu.events, observed on July 24, 2026, indicates a confirmed brand‑impersonation attempt targeting Google. The domain resolves to IP 142.250.185.164, which belongs to AS15169 Google LLC in the United States, suggesting the attacker leveraged legitimate Google infrastructure to increase credibility. The TLS certificate presented is issued by Google Trust Services under the WE1 label, further reinforcing the illusion of authenticity. HTTP probing returned a 404 status, and the page title reported by the scanner is simply “Google”, matching the declared brand target.
Infrastructure fingerprints show the domain is hosted behind Cloudflare, with nameservers brenna.ns.cloudflare.com and hassan.ns.cloudflare.com, and the site supports HTTP/3. Reputation data show the domain is listed on a single security blocklist and has been actively blocked by the PhishDestroy service. VirusTotal scans flagged the domain by two of ninety‑five security vendors, providing additional corroboration of malicious intent. The domain is currently taken offline, and no additional payload or phishing kit details have been disclosed.
Uncertainty remains regarding the exact content that was served before takedown, as no visual or form analysis is available. Defenders should continue to block kintsu.events at the DNS and proxy layers, add the domain to URL filtering policies, and monitor for newly registered domains that resolve to the same IP range or use similar Cloudflare name‑server patterns. Ongoing observation of the associated IP address and certificate issuance may reveal further abuse campaigns.
DOM Analysisanalyzed 2026年10月20日score 81/1002 brand signals
Submitted URLhttp://kintsu.events/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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-21 01:34:32 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-21 01:34:32 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.
使用技術 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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)
