Analysis indicates that the domain drive-google.digital was registered on 21 February 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is hosted on IP 144.124.251.224, which belongs to ASN 216071 (SERVERS TECH FZCO) located in the Netherlands. The domain resolves to four VDSINA name servers (ns1‑ns4.vdsina.com), and no TLS certificate is presented, leaving the site accessible only over HTTP. The page title returned by the HTTP response is “Проверка доступа”, which provides no additional context about the malicious payload. The site is classified as a Tech Support Scam that impersonates Google, and the underlying infrastructure matches the “Recovery Scam” phishing kit documented in prior threat‑intel reports. Reputation scoring from Gridinsoft assigns a trust score of 0 / 100, indicating a high confidence of malicious intent.
VirusTotal scans show that five of ninety‑three antivirus engines flagged the domain, reinforcing the suspicion despite the low detection count. The domain appears on three public blocklists and is actively blocked by PhishDestroy, MetaMask, and SEAL, confirming that multiple security vendors have taken protective action. The current operational status is offline, suggesting that the infrastructure has been taken down or is no longer serving content. Defenders should continue to monitor DNS resolutions for the listed VDSINA name servers, as they may be reused for future campaigns. Adding the IP address 144.124.251.224 and the domain drive-google.digital to local blocklists, firewall deny lists, and secure web gateway policies is recommended.
Incident response teams should also inspect any logs for connections to the VDSINA name servers or attempts to retrieve the “Проверка доступа” page, as these may indicate ongoing reconnaissance. Because the site lacks an SSL certificate, any attempted HTTPS connections will fail, but HTTP traffic may still be used to deliver malicious payloads.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='drive-google.digital', port=80): Max retries exceeded with url: / (Caused by NewConnection
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 4, 2026
DOM Analysisanalyzed Apr 23, 2026score 63/1001 brand signal
Submitted URLhttp://drive-google.digital/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:08:25 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-16 22:13:40 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 22:13:40 UTC → 2026-09-30 16:14:55 UTC · 2,538.02hmidpoint estimate ≈ 2026-08-08 19:14:17 UTC · precision very low · 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
drive-google.digital detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 9, 2026
Time to First Unavailability
2240 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
5 evidence signal groups linked1 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · drive-google.digital
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(IN)
