VirusTotal
10 / 89
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 →
No stored capture is available for this domain.
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.
10 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no 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.
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.
account.placements.digital returned HTTP status 200 during a check on 2026-10-01, providing a clear record of response from the domain on that date. The domain was first observed on 2026-08-09, marking the earliest recorded activity in this evidence set.
An HTTP check on 2026-10-01 recorded status 200 for account.placements.digital. VirusTotal was checked on 2026-09-13 and reported 10 detections out of 89 scanners. The domain was first observed on 2026-08-09. A blocklist check on 2026-10-01 noted a PhishDestroy internal listing.
These records offer a snapshot of account.placements.digital across several dates and sources, each capturing a distinct aspect of its activity. The HTTP check and VirusTotal scan provide technical and detection data, while the PhishDestroy listing and first observation date add context for timeline and cataloging. Each source should be considered individually, as their measurements are not directly comparable.
Maintain the HTTP response, VirusTotal detection record, and PhishDestroy listing for account.placements.digital as separate reference points. Compare future checks against these records to monitor any changes. Keep all source records for ongoing review and analysis of the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: empty_body: raw=empty_body; http=200; via=http_proxy; server=cloudflare
For the registrable domain placements.digital 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.
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.
drake.ns.cloudflare.comLocation describes the IP network.
4d6942038435091e3a3ee771824d596474185e6a32e98939a3c2e4875c4bf83eplacements.digitalSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
7 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.
1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-07-15T10:27:09.679Z.
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