vrf-chatbot.company is a phishing page detected by PhishDestroy on 2026-04-26. Risk: critical (100/100). Registrar: Nicnames. Status: Last known active. Hosting: Zemlyaniy Dmitro Leonidovich. PhishDestroy sent 1 abuse report. VirusTotal: 14/91 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 14. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@nicnames.com.
The latest stored availability evidence still shows the domain reachable; 5 months has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
PhishDestroy has flagged vrf-chatbot.company as a potential brand impersonation site. This means the site may be attempting to trick users into divulging sensitive information by pretending to be a legitimate and trusted organization. Such sites often mimic the look and feel of well-known brands to gain credibility.
This determination is based on several factors, including the fact that the domain was registered through Nicnames, Inc., and has a VirusTotal detection ratio of 10/95, indicating it's a newly created or less-known threat. The domain was created on April 22, 2026, which could suggest it's part of a recent phishing campaign. It resolves to IP address 185.236.79.9 and uses an SSL certificate from Let's Encrypt.
If you have visited vrf-chatbot.company and entered any personal information, such as usernames, passwords, or financial details, it is crucial to take immediate action. Change your passwords on any other accounts where you use the same credentials. Monitor your bank and credit card statements for any unauthorized transactions. Run a full scan of your computer with a reputable antivirus program. Report the incident to the relevant authorities and consider placing a fraud alert on your credit reports.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
No. PhishDestroy classifies vrf-chatbot.company as a phishing page (risk: critical, 100/100); it was first detected on 2026-04-26. VirusTotal: 14/91 engines flag it. Treat the site as unsafe.
Is vrf-chatbot.company safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on vrf-chatbot.company. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used vrf-chatbot.company?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.236.79.9
Network ASN
AS42159
Organization
Zemlyaniy Dmitro Leonidovich
Observed location
Dronten, NL
Server header
nginx
Nameservers 1
ns2.v10394.dh.net.ua
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-04-22 06:17:17
Valid until
2026-07-21 06:17:16
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-04-26 17:00:17 UTC
Collection source
PhishDestroy collector
Certificate fingerprintadd4204ddc2ed15f0d4973d3c0e6c9c4828da89d5987bf8951304391a7291028Certificate names · 1 SAN
v10394.dh.net.ua
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-22 10:36:29 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:36:29 UTClast content: 2026-10-11 10:35:39 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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · vrf-chatbot.company
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.
Content matches2
Same favicon hash or the same page title as this host.
7 evidence signal groups linked1 stored notification recordsLast known active
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
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including vrf-chatbot.company)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
