This domain, www.coinsecurity.digital, is actively flagged as a high-risk phishing site impersonating Google. Analysis indicates the domain was registered on March 3, 2026, through Global Domain Group LLC, and remains operational as of July 12, 2026. The site resolves to IP address 87.120.219.250 and presents a page title matching the targeted brand, further supporting the impersonation claim. Security vendors have detected this domain on two blocklists, and it appears in two threat intelligence pulses, reinforcing its classification as malicious infrastructure. Infrastructure analysis reveals the use of Google Web Server technology, HSTS, and HTTP/3, which may be employed to lend an appearance of legitimacy or to evade detection. The SSL certificate is issued by Let's Encrypt, a common choice for both legitimate and malicious sites due to its accessibility. While the presence of these technologies does not inherently confirm malicious intent, their combination with the domain's registration details and detection by security vendors raises significant concerns. The page content itself has not been fully analyzed, but the page title explicitly matches the targeted brand, aligning with typical brand impersonation tactics. Defenders should treat this domain as confirmed malicious infrastructure. The risk level is classified as high due to the domain's active status, its presence on multiple blocklists, and its detection by 13 out of 95 security vendors. Network-level blocking is recommended for this IP and domain to prevent potential credential theft or other fraudulent activities. Given the domain's recent creation and ongoing activity, continuous monitoring is advised to track any changes in hosting, SSL certificates, or associated infrastructure. If this domain is encountered in logs or user reports, it should be investigated as part of a broader phishing campaign targeting Google users.
Minimum notice count3 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
ICANN RAA §3.18
The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
技術詳細Provenance & timestamps
初確認2026年3月3日
DOM Analysisanalyzed 2026年7月10日score 78/1001 brand signal
Submitted URLhttps://www.coinsecurity.digital/
Favicon Hash
ケース ID
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.
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)
