VirusTotal
16 / 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.
16 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
View stored capture ↗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.
0 external matches
DetailsA 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.
sunset-profit.com returned HTTP status 200 in a check recorded on 2026-10-01, the most recent HTTP observation in this evidence set. The domain was first observed on 2026-09-16, and its registration date is listed as 2025-10-28.
PhishDestroy's internal listing records sunset-profit.com as listed, with that listing recorded in the evidence set. VirusTotal, checked on 2026-09-29, reported 16 detections across 91 scanners. OTX, checked on 2026-09-19, showed 4 pulses. The registrar is Dynadot Inc, and the SSL certificate issuer is Google Trust Services / WE1, scanned on 2026-09-17. PageSpeed, checked on 2026-09-16, recorded a performance score of 100.
The VirusTotal and OTX figures describe separate source observations made on their own dates, so they should be read as distinct records rather than combined into a single measure. The HTTP 200 response on 2026-10-01 describes only that recorded response, not all content or present availability. The PhishDestroy listing is a publisher-owned catalogue entry, and the PageSpeed score reflects a single dated measurement.
For sunset-profit.com, preserve the PhishDestroy listing record, the VirusTotal report, and the OTX pulses as separate source records for later comparison. Compare the HTTP response record with the PageSpeed record to see whether the recorded observations align. Re-check the VirusTotal and OTX records on new dates to compare against the existing entries. Retain the SSL scan record alongside the other source records for reference.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
Edge-IP reputation is not attributed to this domain.
faye.ns.cloudflare.comLocation describes the IP network.
779449ee256ebc17d44024f23612fcb960ba863a2123abfcdfb1784abec1d1a0Saved 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 sunset-profit.com · checked Sep 16, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
172.67.155.220.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unavailable→Reachable
live_content→Unknown
probe_inconclusive
Reachable→Unavailable
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
live_content→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
Unknown
12 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