VirusTotal
4 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
4 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 25 July 2026, analysis confirms that distribute.center is an active generic phishing infrastructure. The domain resolves to Cloudflare nameservers jack.ns.cloudflare.com and princess.ns.cloudflare.com, indicating use of a reputable DNS provider to obscure hosting details. Registration information shows the domain was acquired through Dynadot Inc, a registrar frequently observed in abuse reports. VirusTotal scans show that 3 of 91 security vendors have flagged the domain, providing an early indication of malicious intent.
HTTP response currently returns a 403 status, suggesting that the site is intentionally restricting access, which is a common tactic to evade casual browsing while still serving malicious payloads to targeted requests. The domain appears on three external blocklists and is explicitly blocked by PhishDestroy, MetaMask, and SEAL, reinforcing its classification as a high‑risk phishing resource. Despite the 403 response, the domain remains active, meaning that threat actors can still deliver malicious content to victims who follow crafted URLs or receive phishing emails referencing the domain. Defenders should add distribute.center to outbound and inbound filtering rules, monitor DNS query logs for any resolution attempts, and ensure that web proxy and secure web gateway solutions enforce the blocklists that already list this domain.
Since the underlying hosting is on Cloudflare, any takedown request should be directed to Cloudflare Abuse Contact with reference to the observed vendor detections and blocklist entries. Continuous re‑inspection of the site’s content is advised, as the current page title and payload have not been publicly disclosed. Organizations should also consider threat‑intel sharing with peers to propagate the indicator and reduce exposure to potential credential‑harvesting campaigns that leverage this domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
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.
Edge-IP reputation is not attributed to this domain.
princess.ns.cloudflare.comLocation describes the IP network.
88aba6f0811e8964ab6a75ee94ac36843304e17c155095165348ec982be79172Saved 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 distribute.center · checked Jul 26, 2026
9 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.
Reported by 1 community member, first seen Apr 26, 2026
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