auth.sellerjobchile.com returned HTTP status 200 in an HTTP check dated 2026-10-01, a recorded response that does not by itself establish present availability. The same domain appears on the PhishFeed external blocklist, according to a blocklist check dated 2026-10-01.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 200. A blocklist check on 2026-10-01 counted one external listing, PhishFeed. VirusTotal recorded 18 detections across 91 scanners on 2026-09-29. The domain was first observed on 2026-09-25, when PageSpeed recorded a performance score of 94. An SSL scan on 2026-09-26 identified the issuer as Let's Encrypt / YR1.
Interpretation
The PhishFeed listing and the VirusTotal detection count are separate source observations, each with its own scope, and they should not be merged into a single verdict. The first-observed date and the later checks form a chronology, but the differing dates alone do not demonstrate a change in the domain's status. The HTTP 200 response describes only the recorded response, not all content served.
Recommended Actions
For auth.sellerjobchile.com, preserve the PhishFeed listing and the VirusTotal record as separate source records for later comparison. Compare the HTTP check record with the blocklist check record in separate sentences rather than combining them. Review the PageSpeed and SSL scan records alongside the other observations, and repeat the checks on a later date to build a comparable series.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 01:44:53 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 01:44:53 UTClast content: 2026-10-11 01:44:53 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
使用技術 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Google PageSpeed Insights — mobile performance audit of auth.sellerjobchile.com· checked Sep 25, 2026
94
Good
Performance
FCP
2.41s
First Contentful Paint
LCP
2.41s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.98s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-27 09:14:50 UTC
VirusTotal Detections Update2026-09-26 07:23:10 UTC
VirusTotal scanner detections updated from 17 to 18. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-25 20:25:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 216.198.79.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(US)
