play[.]puebax[.]com
Evidence Summary
Analysis of play.puebax.com, flagged on August 07, 2026 as an active generic phishing infrastructure, shows several concrete indicators of compromise. The domain is listed on one security blocklist and is actively blocked by the PhishDestroy feed, confirming that threat‑intel platforms have identified it as malicious. VirusTotal scans report that 11 out of 91 security vendors have flagged the domain, providing a modest but non‑trivial detection ratio that aligns with the elevated risk rating.
DNS resolution points to the IPv4 address 64.7.198.11, which can be used by defenders to correlate network traffic and enforce deny‑list rules. No additional contextual data such as registrar details, SSL certificate information, or HTTP response codes are available, leaving the broader hosting environment and potential payload delivery mechanisms uncertain. Given the observed blocklist inclusion, vendor detections, and confirmed IP address, security teams should treat any connections to play.puebax.com as hostile.
Recommended mitigations include adding the domain and its resolved IP to outbound filtering rules, monitoring DNS queries for the domain, and reviewing internal logs for any prior contact. Continuous re‑evaluation is advised, as further analysis may reveal additional infrastructure components or changes in detection confidence.
Data Coverage
Network Security Intelligence
Threat Response Pipeline
Blocklist coverage
10 monitored external feeds · stored snapshot Aug 11, 2026
10 monitored external feeds No match
Stored Capture
Domain Intelligence
Technical detailsDNS, TLS names and timestamps
ICANN OVERSIGHT
Registration: puebax.com
Accreditation and RAA context
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For the registrable domain puebax.com 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.
VirusTotal Analysis
Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive