This report analyzes the domain wlfi.beefyhubs.monster, which was configured to impersonate the Google brand. The site's page title is "Google," indicating an attempt to deceive users into believing they are visiting a legitimate Google service. This impersonation poses a threat of credential theft or malware distribution, as users may enter sensitive information or download malicious files under the false assumption of a trusted Google environment.
Technical analysis reveals the domain was flagged by 7 out of 95 VirusTotal vendors, with detection from ChainPatrol, alphaMountain.ai, CRDF, CyRadar, and Lionic. It is listed on one blocklist. The domain was registered through Dynadot LLC on 2025-10-26, hosted on IP address 172.253.62.103 (US) associated with AS15169 Google LLC. No SSL certificate is present, and nameservers are brenna.ns.cloudflare.com and hassan.ns.cloudflare.com. GridinSoft trust score is 0 out of 100.
The domain is currently DOWN or OFFLINE, mitigating immediate user risk. However, given the impersonation of Google, the high number of vendor detections, and the zero trust score, the risk level is assessed as high. Users should avoid any interaction with this domain if it becomes active again.
Registration (base domain)beefyhubs.monster · Created Oct 26, 2025 (353d)—Expires Oct 26, 2026
Time to First Unavailability100 days
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 DetectedNov 14, 2025
DOM Analysisanalyzed Apr 11, 2026score 68/1001 brand signal
Submitted URLhttp://wlfi.beefyhubs.monster/
ICANN OVERSIGHTRegistration: beefyhubs.monster
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For the registrable domain beefyhubs.monster behind this subdomain, 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-13 01:11:57 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-04-21 22:27:10 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 22:27:10 UTC → 2026-09-30 16:14:55 UTC · 3,881.80hmidpoint estimate ≈ 2026-07-11 19:21:02 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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
wlfi.beefyhubs.monster 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.
Feb 23, 2026
Time to First Unavailability
2411 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.
4 evidence signal groups linked0 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 · wlfi.beefyhubs.monster
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.
(US)
