Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Stored evidence for post-info-swiss.com: VirusTotal recorded 20 detections among 89 scanners on 2026-09-19. 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 post-info-swiss.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 20 detections among 89 scanners in the stored snapshot dated 2026-09-19. 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-19 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 post-info-swiss.com in the snapshot dated 2026-09-19. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains post-info-swiss.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 post-info-swiss.com on 2026-09-19. The OpenPhish blocklist snapshot is dated 2026-09-19 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-17. 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 post-info-swiss.com, the registrar field records NameSilo, LLC; this is kept as an exact source value. The source stores 180.178.180.159 as the observed address in this record. The registration date for post-info-swiss.com is recorded as 2026-09-17. 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 post-info-swiss.com record states that VirusTotal recorded 20 detections among 89 scanners on 2026-09-19. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-19. PhishDestroy remains a separate publisher catalogue entry in the stored record. For post-info-swiss.com, the registrar field records NameSilo, LLC; this remains separate from the other source fields. The observed address field in this record contains 180.178.180.159. The supported conclusion is bounded to the exact stored observations for post-info-swiss.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to post-info-swiss.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain post-info-swiss.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 post-info-swiss.com. The stored record does not justify extending that rule to 180.178.180.159 or to other infrastructure records.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='post-info-swiss.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:29:39 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-19 10:00:19 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-19 10:00:19 UTC → 2026-09-30 16:14:55 UTC · 270.24hmidpoint estimate ≈ 2026-09-25 01:07:37 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.
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-19 22:00:28 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-19 06:44:57 UTC
Telemetry event observed.
Threat First Observed2026-09-19 06:44:44 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 180.178.180.159.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
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)
PhishDestroy Investigation
