Stored evidence for spif394.com: VirusTotal recorded 11 detections among 90 scanners on 2026-09-06. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for spif394.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 11 detections among 90 scanners in the stored snapshot dated 2026-09-06. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-06 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish are recorded as named external blocklist observations for spif394.com in the snapshot dated 2026-09-05. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains spif394.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed spif394.com on 2026-09-05. The OpenPhish blocklist snapshot is dated 2026-09-05 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-06-27. A URLScan reference was stored on 2026-09-05 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For spif394.com, the registrar field records Dynadot Inc; this is kept as an exact source value. The source stores 156.238.121.206 as the observed address in this record. The registration date for spif394.com is recorded as 2026-06-27. The SSL issuer is recorded as Let's Encrypt / YR1 in the snapshot dated 2026-09-05. The stored ASN observation records 54801 and Zillion Network Inc. in this record. The observed server header is recorded as nginx in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The spif394.com record states that VirusTotal recorded 11 detections among 90 scanners on 2026-09-06. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-05. PhishDestroy remains a separate publisher catalogue entry in the stored record. For spif394.com, the registrar field records Dynadot Inc; this remains separate from the other source fields. The observed address field in this record contains 156.238.121.206. The supported conclusion is bounded to the exact stored observations for spif394.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to spif394.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain spif394.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to spif394.com. The stored record does not justify extending that rule to 156.238.121.206 or to other infrastructure records.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
RegistrationCreated Jun 27, 2026 (98d)—Expires Jun 27, 2027
HTTP Status502 Error
Time to First Unavailability5 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 5, 2026
DOM Analysisanalyzed Sep 5, 2026score 0/1001 brand signal
Submitted URLhttp://spif394.com/
Favicon Hash
Case ID
Page Title
shopify
Impersonates
Shopify
TLS Certificate
Hostname coverage not recorded·
Issued by Let's Encrypt· stored validity ends in 80 days
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownOrigin unreachableHttp 5xx20%2026-10-03 01:36:27 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-09 22:14:58 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-09 22:14:58 UTC → 2026-09-30 16:14:55 UTC · 498.00hmidpoint estimate ≈ 2026-09-20 07:14:56 UTC · precision low · basis bounded
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.
Technologies · 3 identified
V
Vue.js
JavaScript frameworks
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Google PageSpeed Insights — mobile performance audit of spif394.com· checked Sep 5, 2026
85
Needs Work
Performance
FCP
1.25s
First Contentful Paint
LCP
3.34s
Largest Contentful Paint
CLS
0.055
Cumulative Layout Shift
TBT
64ms
Total Blocking Time
SI
6.68s
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.
Domain Status Transition2026-09-10 22:46:47 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-05 15:03:13 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 156.238.121.206.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
16 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.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · spif394.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches1
Same favicon hash or the same page title as this host.
(US)
