VirusTotal
11 / 89
“com-authorization-v2.digital | 521: Web server is down”
Security analysis of com-authorization-v2.digital covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
This domain, com-authorization-v2.digital, is identified as a high-risk crypto wallet drainer phishing infrastructure designed to harvest wallet credentials and execute unauthorized transactions. Analysis indicates the domain mimics legitimate authorization portals, tricking users into entering sensitive wallet recovery phrases or private keys. The intent is to drain cryptocurrency assets from compromised wallets, a tactic increasingly observed in targeted phishing campaigns against decentralized finance (DeFi) users. Infrastructure analysis reveals multiple technical indicators confirming malicious intent. The domain was registered on June 05, 2026, through NICENIC INTERNATIONAL GROUP CO., LIMITED, a registrar frequently associated with phishing domains. It resolves to the IP address 172.67.202.29 and is flagged by 13 out of 95 security vendors on VirusTotal. Additionally, the domain appears on five security blocklists and is referenced in two AlienVault OTX threat intelligence pulses. The SSL certificate is issued by Google Trust Services, which, while legitimate, is commonly exploited in phishing campaigns to lend a false sense of security. Users who visited com-authorization-v2.digital or interacted with its content should assume their wallet credentials may be compromised. Immediate action is required: revoke any connected dApp permissions, transfer assets to a new wallet, and monitor transaction history for unauthorized activity. If credentials were entered, consider the original wallet permanently compromised. Users should also report the domain to their wallet provider and relevant security teams to aid in broader mitigation efforts. Continuous vigilance and verification of domain authenticity are critical to mitigating such threats.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://com-authorization-v2.digital/; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
melissa.ns.cloudflare.comwesley.ns.cloudflare.comLocation describes the IP network.
6a32fbd870eb332f2b077855bd42aa9e50ac8032bcc62d6d30f6f52ced1333b2Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Reported by 1 community member, first seen Jun 11, 2026
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive