ABUSE NOTICE · 24H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@swissnetwork.co.
The latest stored availability evidence still shows the domain reachable; 2 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
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.
On 2026-10-09, payments.transaction-processing.com was observed returning an HTTP 302 status code, indicating a redirect response. The domain was also noted to have a low PageSpeed performance score, which may reflect technical limitations or configuration issues.
Recorded Evidence
VirusTotal reported 15 detections out of 92 scanners for payments.transaction-processing.com on 2026-10-03. The PhishDestroy internal listing included the domain as of 2026-10-09. The observed server header was 'snooserv,' and the technologies identified were Reddit and Reddit Ads, both recorded on 2026-10-09. The page title was 'Blocked' during the HTTP check on 2026-10-09.
Interpretation
The collected evidence provides a technical profile of payments.transaction-processing.com from multiple sources, each offering distinct insights into its observed state. VirusTotal’s detection count and scanner coverage reflect external security intelligence, while the PhishDestroy listing represents an internal catalogue entry. The HTTP response and PageSpeed score highlight aspects of the domain’s infrastructure and user experience, without indicating the nature of its content or activity.
Recommended Actions
For payments.transaction-processing.com, it is advisable to preserve the VirusTotal detection record and the PhishDestroy internal listing for ongoing comparison and review. Retaining the HTTP response details and PageSpeed performance score will support technical assessments of the domain’s infrastructure. Future checks should reference these source records to monitor for any changes in external and internal observations.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:42:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:42:02 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.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Amazon S3 or Amazon Simple Storage Service is a service offered by Amazon Web Services (AWS) that provides object storage through a web service interface.
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
SOCRadar
ソフォス
VIPRE
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of payments.transaction-processing.com· checked Oct 9, 2026
32
Poor
Performance
FCP
4.46s
First Contentful Paint
LCP
6.26s
Largest Contentful Paint
CLS
1.02
Cumulative Layout Shift
TBT
281ms
Total Blocking Time
SI
6.87s
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.
Threat First Observed2026-10-09 03:22:37 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 31.56.209.94.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
11 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
