The domain w.beefyhubs.monster was observed with a creation timestamp of 26 Oct 2025 and is registered through Dynadot LLC. DNS resolution is delegated to brenna.ns.cloudflare.com and hassan.ns.cloudflare.com, both Cloudflare name servers. A lookup resolves the hostname to 142.251.140.164, an address owned by Google LLC (AS15169) located in the United States. The HTTP response returns a page whose title is "Google", matching the declared brand target of Google and confirming the intent to impersonate that brand. No TLS certificate was presented during the connection, indicating an unencrypted service.
VirusTotal records show that 11 of 95 scanning engines flag the domain as malicious, and the domain appears on a single external blocklist, where it has been listed by PhishDestroy. The site is currently taken offline, and no further content has been captured. Evidence suggests a brand‑impersonation campaign that leverages a legitimate Google IP range to increase credibility.
Because the service lacks TLS, interception is trivial, but the use of a Google‑owned address may bypass some reputation filters. Defenders should block the domain at the network perimeter, monitor the associated IP for additional malicious activity, and consider adding the name servers to watchlists. Ongoing surveillance of DNS changes, rapid removal from resolve caches, and updating threat intelligence platforms to retain historical indicators are recommended until the threat is fully mitigated.
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='w.beefyhubs.monster', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)beefyhubs.monster · Created Oct 26, 2025 (352d)—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 15, 2025
DOM Analysisanalyzed Apr 11, 2026score 25/1002 brand signals
Submitted URLhttp://w.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:49 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-04-12 10:25:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-12 10:25:15 UTC → 2026-09-30 16:14:55 UTC · 4,109.83hmidpoint estimate ≈ 2026-07-07 01:20:05 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
w.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
2391 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.
3 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 · w.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)
