VirusTotal
3 / 91
“Website proverka.vavadadhr.store is ready. The content is to be added”
Security analysis of www.proverka.vavadadhr.store 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.
The domain www.proverka.vavadadhr.store was registered on March 02, 2024 through the REGRU-RU registrar. Its authoritative nameservers resolve to ns1.vavadadhr.store (5.61.53.167) and ns2.vavadadhr.store, indicating that the attacker controls the DNS zone. The site resolves to IP address 176.97.79.105, which is allocated to AS58061 Scalaxy B.V. in the Netherlands. No SSL certificate is presented, and the HTTP response currently indicates the site is taken offline, but historical evidence shows the page title "Website proverka.vavadadhr.store is ready.
The content is to be added," suggesting a placeholder landing page typical of phishing infrastructure awaiting payload deployment. The domain appears on one security blocklist and has been actively blocked by the PhishDestroy feed. VirusTotal analysis reports a single positive detection out of ninety‑five submitted security vendors, reinforcing the malicious classification despite the low detection count. Gridinsoft assigns a trust score of 0 out of 100, reflecting a lack of confidence in the site's legitimacy.
The available data points collectively confirm the domain’s use in a generic phishing campaign, though details such as the specific luring vector, targeted brands, or credential‑harvesting mechanisms remain unverified. Defenders should continue to block the domain at perimeter controls, monitor for any resurrection of the site, and add the IP address 176.97.79.105 to deny‑list rules. Because the domain is already offline, threat hunters should focus on correlating any recent traffic to the IP or nameserver hostnames with internal logs to identify potential compromise attempts. Ongoing surveillance of the registrar REGRU-RU and associated nameservers may reveal future malicious domains employing the same infrastructure.
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
status_splitScanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-2816.invalid', port=80): Max retries exceeded with url: / (Caused by Ne
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.
ns1.vavadadhr.store5.61.53.167ns2.vavadadhr.store5.61.54.124Location describes the IP network.
9 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.
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