VirusTotal
4 / 91
“Explore pons”
On 2026-08-07 SOC analysts reviewed the newly observed domain ponz.family. The WHOIS record shows the domain was registered through NameSilo, LLC and its creation timestamp is 2026-07-16, indicating a recent launch. DNS resolution points to the IPv4 address 45.9.148.108; no additional A or CNAME records were observed. The domain is currently listed on two public blocklists, specifically PhishDestroy and ScamSniffer, and both services have flagged it as malicious. VirusTotal reports that the domain has been scanned by 91 antivirus and URL-reputation engines; none of the engines raised a detection at the time of analysis.
The absence of detections does not constitute a safety guarantee, as many scanners rely on signatures that may not yet cover this campaign. No TLS certificate data, HTTP response codes, or page-title information have been published, and automated crawlers have not returned a content fingerprint. Consequently, the specific brand or service being impersonated remains unknown, and the exact phishing vector cannot be confirmed. The limited evidence suggests the infrastructure is being used for a generic phishing operation, but the lack of payload samples leaves the precise tactics, techniques, and procedures (TTPs) unverified.
Defenders should treat ponz.family as a high-confidence indicator of compromise. Immediate mitigation steps include adding the domain and its resolving IP 45.9.148.108 to network deny lists, updating DNS filtering policies to block resolution, and ensuring that email gateways enforce URL-reputation checks that incorporate the PhishDestroy and ScamSniffer feeds. Continuous monitoring for any new hostnames, changes in SSL configuration, or appearance of the domain in sandboxed traffic is advised. If future analysis yields page content or credential-stealing forms, the findings should be correlated with existing phishing kits to refine detection rules.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
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.dnsowl.comns2.dnsowl.comns3.dnsowl.comLocation describes the IP network.
0318df74b5446944ab614029642fc5cfd0f88fbe0646720e28ae3596dc6be91fwww.ponz.familySaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of ponz.family · checked Aug 7, 2026
45.9.148.108. 14 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